1AMANDA-COMPATIBILIT(7) Miscellanea AMANDA-COMPATIBILIT(7)
2
6 amanda-compatibility - Compatibility between Amanda versions
7
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 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 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 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 Kerberos4 authentication in 2.5 is compatible with 2.4. In 2.5,
24 kerberos4 encryption is broken, at least for the server.
25 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 Amanda 2.6.0 and later are completely compatible with 2.5.1.
32 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
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 Amanda 3.1
45 Although it is a significant rewrite, there are no incompatible changes
46 in this release.
47 Old-style changer scripts are deprecated in this release. While they
49 remain available, they may be removed in a future release. Consider
50 upgrading to one of the new changer scripts. Users of chg-zd-mtx are
51 particularly encouraged to consider the much more intelligent
52 chg-robot. See amanda-changers(7) for more information.
53 The following configuration configration keywords are deprecated. This
55 is currently a warning, but will become an error soon.
56 · label_new_tapes - use autolabel
58 Amanda 2.6.1
61 There are no incompatible changes in this release, but consider
62 switching to some of the new applications instead of the old GNUTAR and
63 DUMP programs.
64 The following configuration configration keywords are deprecated. This
66 is currently a warning, but will become an error soon.
67 · tapebufs - use device-output-buffer-size instead
69 · rawtapedev - use tapedev instead
71 · file-pad - this is no longer optional, and all files are padded
73 Amanda 2.6.0
76 amverify and amverifyrun are removed and replaced with amcheckdump(8).
77 Both amdd and ammt are removed.
78 Some Amanda files are now installed in new amanda/ subdirectories:
80 libraries are now installed in $libdir/amanda and internal programs are
81 now installed in $libexecdir/amanda.
82 The amandates file, previously at /etc/amandates, is now at
84 $localstatedir/amanda/amandates. You may want to move your existing
85 /etc/amandates when you upgrade Amanda.
86 GLib is now required to build and run Amanda.
88
90 amanda(8), amanda.conf(5)
91 The Amanda Wiki: : http://wiki.zmanda.com/
93
95 Dustin J. Mitchell <dustin@zmanda.com>
96 Zmanda, Inc. (http://www.zmanda.com)
97Amanda 3.1.3 10/04/2010 AMANDA-COMPATIBILIT(7)