How To:Migrate from older amanda versions: Difference between revisions

From wiki.zmanda.com
Jump to navigation Jump to search
Line 33: Line 33:


== Tranfering data ==
== Tranfering data ==
Amana2.5 store its process data in/etc/amanda/DailySet1:
In the parameter       
Amanda 2.5 store its process data in/etc/amanda/DailySet1:
# /etc/amanda/DailySet1/index
# /etc/amanda/DailySet1/index
# /etc/amanda/DailySet1/curinfo
# /etc/amanda/DailySet1/curinfo

Revision as of 10:51, 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

  1. runtapes
  2. tapedev
  3. tpchanger
  4. tape type
  5. labelstr
  6. infofile "/var/lib/amanda/DailySet1/curinfo"
  7. logdir "/var/lib/amanda/DailySet1"
  8. indexdir "/var/lib/amanda/DailySet1/index"
  9. ...

Tranfering data

In the parameter Amanda 2.5 store its process data in/etc/amanda/DailySet1:

  1. /etc/amanda/DailySet1/index
  2. /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