How To:Migrate from older amanda versions: Difference between revisions
Line 27: | Line 27: | ||
# tape type | # tape type | ||
# labelstr | # labelstr | ||
# infofile "/var/lib/amanda/DailySet1/curinfo" | |||
# logdir "/var/lib/amanda/DailySet1" | |||
# indexdir "/var/lib/amanda/DailySet1/index" | |||
# ... | # ... | ||
Revision as of 10:49, 26 October 2007
Overview
Sometimes you have to upgrade your backupserver.
This article describes, how to migrate from an old amanda version (amanda-server-2.4.4p2-3) to the current version (amanda-server-2.5.1p3).
Backup jobs
The default backup job is e.g. DailySet1.
Amanda store the configuration data for this backup job in /etc/amanda/DailySet1: e.g. /etc/amanda/DailySet1/amanda.conf
The Amanda database data for this backup job is stored in /var/lib/amanda/DailySet1.
The file index for backup data is stored in /var/lib/amanda/DailySet1/curinfo/HOST/DISK.
Startpoint
After 3 years of using amanda 2.4 there was time for updating the whole server.
On a new server with Fedora Core 6 I installed amanda 2.5 with the old DLT-tapedrive.
I configured the new server and tested the backup with a small backupjob.
In /etc/amanda/DailySet1/amanda.conf there is to change your basic configuration like
- runtapes
- tapedev
- tpchanger
- tape type
- labelstr
- infofile "/var/lib/amanda/DailySet1/curinfo"
- logdir "/var/lib/amanda/DailySet1"
- indexdir "/var/lib/amanda/DailySet1/index"
- ...
Tranfering data
Amana2.5 store its process data in/etc/amanda/DailySet1:
- /etc/amanda/DailySet1/index
- /etc/amanda/DailySet1/curinfo
Therefore I transfer the data from the old server: //old-server/var/lib/amanda/DailySet1/index to //new-server/etc/amanda/DailySet1/index
tapelist and curinfo vice versa.
Back to How Tos