2 Chapter 30. Upgrade Issues
3 Prev Part VI. Historical files Next
5 -------------------------------------------------------------------------------
7 Chapter 30. Upgrade Issues
18 Refer to http://www.amanda.org/docs/upgrade.html for the current version of
20 Amanda 2.4.0 has introduced a major incompatibility in the Amanda protocol.
21 This means that pre-2.4.0 clients won't interoperate with a 2.4.0 server, nor
22 will 2.4.0 clients interoperate with pre-2.4.0 servers. You have to upgrade
23 them all at the same time.
24 To ease the upgrade process Amanda has, from release 2.4.0 on, a configure flag
25 (--with-testing) that will cause Amanda to use alternate service names (Amanda-
26 test) instead of the standard ones. This allows you to keep using your old
27 version of Amanda while you test the new one.
28 Depending upon the version of Amanda you are upgrading from, Amanda may use a
29 different database library to store the backup information, and the new Amanda
30 may not be able to read the old Amanda database files. In this case, you will
31 want to do something like the following:
32 Before the upgrade (using the old version of amadmin):
34 # cd /var/AMANDA/CONFIG
35 # amadmin CONFIG export > zzz
40 and after the upgrade (using the new version of amadmin):
42 # cd /var/AMANDA/CONFIG
43 # amadmin CONFIG import < zzz
46 and a month :-) after you are happy with the new version:
48 # cd /var/AMANDA/CONFIG
52 After 2.4.0, the structure of the directory holding the index files was changed
53 to have three levels instead of being flat. This greatly reduces the number of
54 files in a given directory, which was a problem for some systems.
56 [indexdir]/hostname/filesystem/YYYYMMDD_L.gz
57 where hostname and filesystem are "sanitized" versions of the names from
58 disklist, i.e. '/' characters are converted to '_' and so on. This new naming
59 convention matches the one used for the text formatted database.
60 A script is available to convert the flat directory structure to the new
62 http://www.amanda.org/2.4-conv/msg00428.html
63 -------------------------------------------------------------------------------
66 Chapter 29. Response to CPIO Security Home Chapter 31. What once was new