1AMANDA-COMPATIBILIT(7)            Miscellanea           AMANDA-COMPATIBILIT(7)
2
3
4

NAME

6       amanda-compatibility - Compatibility between Amanda versions
7

NETWORK COMPATIBILITY

9       Amanda has used several on-the-wire protocols to communicate between
10       the server and backup clients, and not all of them have been
11       compatible.
12
13       Versions of Amanda prior to about 2.3 used a different protocol which
14       is not compatible. 2.3 is very old so this is not of general interest.
15
16       The Amanda 2.4 series all use the same protocol. This protocol has
17       support for extensibility. Generally upgrading clients or servers along
18       the 2.4 branch does not cause difficulty.
19
20       Amanda 2.5.0 uses the same protocol as 2.4. One can use a 2.5.0 server
21       with 2.4 clients and a 2.4 server with 2.5.0 clients.
22
23       Kerberos4 authentication in 2.5 is compatible with 2.4. In 2.5,
24       kerberos4 encryption is broken, at least for the server.
25
26       Amanda 2.5.1 introduced a new recover protocol. Backup communication
27       works with any combination of versions, but 2.5.1's amrecover cannot
28       communicate with an older server. Use oldamrecover on 2.5.1 and higher
29       clients when communicating with an older server.
30
31       Amanda 2.6.0 and later are completely compatible with 2.5.1.
32
33       To restore a dump created with the tapesplit_size option using
34       amrecover, you need at least a 2.5 server and late-2.4 client.
35       (Extracting that backup using only shell, mt and dd is also possible.)
36

UPGRADES

38       The recommended course for Amanda upgrades is to upgrade the server
39       first, and test backups and restores before upgrading clients. Consult
40       the changes described below for the relevant span of versions to
41       determine what adjustments, if any, are required. Also see the NEWS
42       file shipped with each Amanda release for more detailed information.
43
44   Amanda 3.2
45       The following configuration configration keywords are deprecated. This
46       is currently a warning, but will become an error soon.
47
48       ·   amrecover-do-fsf - amrecover always seeks to files when recovering
49
50       ·   amrecover-check-label - amrecover always checks the volume label
51           when recovering
52
53       ·   Dumptype parameters tape-splitsize, split-diskbuffer, and
54           fallback-splitsize - see allow-split and tapetype parameters
55           part-size, part-cache-type, part-cache-dir, and
56           part-cache-max-size. See amanda.conf(5) for more information on
57           these new parameters, noting particularly that all but the first
58           are tapetype parameters, not dumptype parameters.
59
60           To convert most cases to the new parameters, set part-size to the
61           old value of tape-splitsize and part-cache-dir to the old value of
62           split-diskbuffer, if present. If split-diskbuffer was set, then set
63           part-cache-type to disk, otherwise memory. Finally, if using memory
64           caching, set part-cache-max-size to the previous value of
65           fallback-splitsize. Be sure to remove all of the old keywords from
66           your configuration.
67
68
69   Amanda 3.1
70       Although it is a significant rewrite, there are no incompatible changes
71       in this release.
72
73       Old-style changer scripts are deprecated in this release. While they
74       remain available, they may be removed in a future release. Consider
75       upgrading to one of the new changer scripts. Users of chg-zd-mtx are
76       particularly encouraged to consider the much more intelligent
77       chg-robot. See amanda-changers(7) for more information.
78
79       The following configuration configration keywords are deprecated. This
80       is currently a warning, but will become an error in a future version.
81
82       ·   label_new_tapes - use autolabel
83
84
85   Amanda 2.6.1
86       There are no incompatible changes in this release, but consider
87       switching to some of the new applications instead of the old GNUTAR and
88       DUMP programs.
89
90       The following configuration configration keywords are deprecated. This
91       is currently a warning, but will become an error soon.
92
93       ·   tapebufs - use device-output-buffer-size instead
94
95       ·   rawtapedev - use tapedev instead
96
97       ·   file-pad - this is no longer optional, and all files are padded
98
99
100   Amanda 2.6.0
101       amverify and amverifyrun are removed and replaced with amcheckdump(8).
102       Both amdd and ammt are removed.
103
104       Some Amanda files are now installed in new amanda/ subdirectories:
105       libraries are now installed in $libdir/amanda and internal programs are
106       now installed in $libexecdir/amanda.
107
108       The amandates file, previously at /etc/amandates, is now at
109       $localstatedir/amanda/amandates. You may want to move your existing
110       /etc/amandates when you upgrade Amanda.
111
112       GLib is now required to build and run Amanda.
113

SEE ALSO

115       amanda(8), amanda.conf(5)
116
117       The Amanda Wiki: : http://wiki.zmanda.com/
118

AUTHOR

120       Dustin J. Mitchell <dustin@zmanda.com>
121           Zmanda, Inc. (http://www.zmanda.com)
122
123
124
125Amanda 3.3.3                      01/10/2013            AMANDA-COMPATIBILIT(7)
Impressum