2 .\" Title: amanda-compatibility
3 .\" Author: Dustin J. Mitchell <dustin@zmanda.com>
4 .\" Generator: DocBook XSL Stylesheets v1.76.1 <http://docbook.sf.net/>
6 .\" Manual: Miscellanea
7 .\" Source: Amanda 3.3.2
10 .TH "AMANDA\-COMPATIBILIT" "7" "07/25/2012" "Amanda 3\&.3\&.2" "Miscellanea"
11 .\" -----------------------------------------------------------------
12 .\" * Define some portability stuff
13 .\" -----------------------------------------------------------------
14 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
15 .\" http://bugs.debian.org/507673
16 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
17 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
20 .\" -----------------------------------------------------------------
21 .\" * set default formatting
22 .\" -----------------------------------------------------------------
23 .\" disable hyphenation
25 .\" disable justification (adjust text to left margin only)
27 .\" -----------------------------------------------------------------
28 .\" * MAIN CONTENT STARTS HERE *
29 .\" -----------------------------------------------------------------
31 amanda-compatibility \- Compatibility between Amanda versions
32 .SH "NETWORK COMPATIBILITY"
34 Amanda has used several on\-the\-wire protocols to communicate between the server and backup clients, and not all of them have been compatible\&.
36 Versions of Amanda prior to about 2\&.3 used a different protocol which is not compatible\&. 2\&.3 is very old so this is not of general interest\&.
38 The Amanda 2\&.4 series all use the same protocol\&. This protocol has support for extensibility\&. Generally upgrading clients or servers along the 2\&.4 branch does not cause difficulty\&.
40 Amanda 2\&.5\&.0 uses the same protocol as 2\&.4\&. One can use a 2\&.5\&.0 server with 2\&.4 clients and a 2\&.4 server with 2\&.5\&.0 clients\&.
42 Kerberos4 authentication in 2\&.5 is compatible with 2\&.4\&. In 2\&.5, kerberos4 encryption is broken, at least for the server\&.
44 Amanda 2\&.5\&.1 introduced a new recover protocol\&. Backup communication works with any combination of versions, but 2\&.5\&.1\*(Aqs amrecover cannot communicate with an older server\&. Use oldamrecover on 2\&.5\&.1 and higher clients when communicating with an older server\&.
46 Amanda 2\&.6\&.0 and later are completely compatible with 2\&.5\&.1\&.
48 To restore a dump created with the tapesplit_size option using amrecover, you need at least a 2\&.5 server and late\-2\&.4 client\&. (Extracting that backup using only shell, mt and dd is also possible\&.)
51 The recommended course for Amanda upgrades is to upgrade the server first, and test backups and restores before upgrading clients\&. Consult the changes described below for the relevant span of versions to determine what adjustments, if any, are required\&. Also see the NEWS file shipped with each Amanda release for more detailed information\&.
54 The following configuration configration keywords are deprecated\&. This is currently a warning, but will become an error soon\&.
64 \fBamrecover\-do\-fsf\fR
65 \- amrecover always seeks to files when recovering
76 \fBamrecover\-check\-label\fR
77 \- amrecover always checks the volume label when recovering
89 \fBtape\-splitsize\fR,
90 \fBsplit\-diskbuffer\fR, and
91 \fBfallback\-splitsize\fR
94 and tapetype parameters
96 \fBpart\-cache\-type\fR,
97 \fBpart\-cache\-dir\fR, and
98 \fBpart\-cache\-max\-size\fR\&. See
100 for more information on these new parameters, noting particularly that all but the first are tapetype parameters, not dumptype parameters\&.
102 To convert most cases to the new parameters, set
105 \fBtape\-splitsize\fR
107 \fBpart\-cache\-dir\fR
109 \fBsplit\-diskbuffer\fR, if present\&. If
110 \fBsplit\-diskbuffer\fR
112 \fBpart\-cache\-type\fR
114 \fBdisk\fR, otherwise
115 \fBmemory\fR\&. Finally, if using memory caching, set
116 \fBpart\-cache\-max\-size\fR
117 to the previous value of
118 \fBfallback\-splitsize\fR\&. Be sure to remove all of the old keywords from your configuration\&.
123 Although it is a significant rewrite, there are no incompatible changes in this release\&.
125 Old\-style changer scripts are deprecated in this release\&. While they remain available, they may be removed in a future release\&. Consider upgrading to one of the new changer scripts\&. Users of
127 are particularly encouraged to consider the much more intelligent
128 \fIchg\-robot\fR\&. See
129 \fBamanda-changers\fR(7)
130 for more information\&.
132 The following configuration configration keywords are deprecated\&. This is currently a warning, but will become an error in a future version\&.
147 .SS "Amanda 2\&.6\&.1"
149 There are no incompatible changes in this release, but consider switching to some of the new applications instead of the old GNUTAR and DUMP programs\&.
151 The following configuration configration keywords are deprecated\&. This is currently a warning, but will become an error soon\&.
163 device\-output\-buffer\-size
190 \- this is no longer optional, and all files are padded
193 .SS "Amanda 2\&.6\&.0"
198 are removed and replaced with
199 \fBamcheckdump\fR(8)\&. Both
205 Some Amanda files are now installed in new
207 subdirectories: libraries are now installed in
209 and internal programs are now installed in
210 $libexecdir/amanda\&.
212 The amandates file, previously at
213 /etc/amandates, is now at
214 $localstatedir/amanda/amandates\&. You may want to move your existing
216 when you upgrade Amanda\&.
218 GLib is now required to build and run Amanda\&.
225 : http://wiki.zmanda.com/
228 \fBDustin J\&. Mitchell\fR <\&dustin@zmanda\&.com\&>
230 Zmanda, Inc\&. (http://www\&.zmanda\&.com)