2 Chapter 1. AMANDA 2.4.x - System-Specific Installation Notes
3 Prev Part I. Installation Next
5 -------------------------------------------------------------------------------
7 Chapter 1. AMANDA 2.4.x - System-Specific Installation Notes
17 XML-conversion;Updates
37 Sinix_5.43_(Reliant_Unix)
62 Refer to http://www.amanda.org/docs/systemnotes.html for the current version of
64 Please read the notes that correspond to the architectures you are installing
65 for. If you find additional gotchas, or anything incorrect in these notes,
66 please send your updates to mailto://amanda-hackers@amanda.org after checking
67 that they are not known/fixed problems in the AMANDA patches page: http://
68 www.amanda.org/patches/.
72 You may have compilation errors on statfs.c if you're running, on a Solaris 2.6
73 host, a gcc that was not build on a Solaris 2.6 host. This happens because gcc
74 stores fixed copies of some Solaris header files on an internal directory. You
75 must rebuild gcc if you get this kind of trouble. Note, however, that gcc
76 2.7.2.3 does not support Solaris 2.6, you should upgrade to 2.8.0 or higher, or
81 According to Julian Stevens <julian.stevens@baedsl.co.uk>, the format of inetd
82 on Trusted Solaris 1.2 is a bit different. Just before the user name, you
83 should insert the word `untrusted':
85 amanda dgram udp wait untrusted amuser /usr/local/libexec/amandad amandad
88 The patch-system script is *NOT* aware of this detail; you must fix it
93 A bug in GNUtar 1.12 causes it to miscalculate (in fact, to misreport) the size
94 of filesystems. A patch for GNUtar is available in the patches directory.
98 The Ultrix dump program contains an explicit check that it is being run by
99 root. This defeats the usual practice of a non-root "operator" userid for
100 dumps. For this reason, the rundump program (a setuid-root wrapper for dump) is
101 enabled by default. If you find rundump is not necessary for you, just run
103 configure --without-rundump
105 The Ultrix restore program will fail if it is not connected to a tty. Since the
106 restore program is invoked in the clients in order to create index files, and
107 it the client is not connected to a tty, index creation will fail. Using GNUTAR
108 instead of DUMP is an option. Thanks to Edwin Wiles
109 <ewiles@mclean.sterling.com> for the investigation. Another alternative
110 proposed by Martyn Johnson <Martyn.Johnson@cl.cam.ac.uk> is to use a modified
111 restore program: use a binary program editor and replace `/dev/tty' with `/dev/
112 nul', for instance, and link /dev/nul to /dev/null. Note that the chosen file
113 name must be exactly 8 bytes long, otherwise you'll break the restore program.
114 A nice one-liner perl script by Martyn Johnson will do the trick (make sure you
115 preserve a copy of the original restore program, it will be rewritten by
116 running this script!):
118 perl -pi -e 'BEGIN { $/ = "/dev/tty" } s-$/-/dev/nul-' restore
121 The Ultrix C compiler seems to be too broken to compile AMANDA. You are likely
126 You may run into an internal /bin/sh limit when running the configure script.
127 The error message is:
129 ./configure: sh internal 2K buffer overflow
132 Using /bin/posix/sh usually works around the problem. Another solution is to
133 install GNU bash and use it instead of /bin/sh.
134 If `configure' complains about not finding `lex', you'll have to get `flex'
135 installed. Look for its URL in Amanda_Installation_Notes.
136 If you use logical volumes, you may refer to mountpoints or full device
137 pathnames instead of device names in the disk list file.
138 According to Stan Brown <stanb@awod.com>, amverify won't work with HP/UX's
139 stock mt. The work-around is to install GNU cpio, that contains an
140 implementation of mt, and edit amverify so that MT points to GNU mt and MTOPT
141 is `-f', or reconfigure and rebuild amanda from scratch, making sure it finds
142 GNU mt before the stock mt in the PATH.
143 If you have vxfs filesystems to back up, AMANDA will pick vxdump automatically.
144 GNU tar 1.12 will incorrectly report the size of backups. There's a patch in
145 the patches directory that fixes this problem.
146 The use of `amhpfixdevs' is deprecated, since you can list mount-points or full
147 device names in the disklist. The script may be removed in future releases of
149 Sometimes you may get the error message `Link severed' from an HP/UX client.
150 This is just a cute name the developers of HP/UX found for `Network error'.
151 Reported by Michael Brehl <mbr@condor.de>
155 Linux hosts intended to back up efs partitions with dump should install the
156 dump package, as it is not installed by default on most Linux distributions. It
157 is possible to find compiled versions of dump on most Linux sites and CD-ROMs.
158 Note, however, that DUMP for Linux has been quite unreliable, sometimes being
159 unable to perform backups, producing weird error messages such as `master/slave
160 protocol botched', and sometimes creating unrestorable dump images, especially
161 of active filesystems. The first problem can sometimes be fixed by cleaning up
162 outdated entries in /etc/dumpdates, but your best bet is probably GNU tar.
163 Make sure the user that runs configure has permission to run the dump program,
164 otherwise configure may misdetect an ability of dump to accept a -E (for
166 GNUtar 1.11.8, distributed with some Linux versions, will cause index failures
167 (Index returned -1). Upgrading to GNUtar 1.12 fixes this problem. This is not a
168 Linux-specific problem, but it is quite common in this platform.
169 AMANDA now supports the ftape driver version 3.04d. It adjusts the blocksize
170 automatically to 32k and supports QIC volume tables. More details con be found
171 in the file ZFTAPE in this directory.
172 Some releases of dump for Linux, such as the one distributed with Debian 2.0,
173 have modified dump so that it stores dumpdates in /var/lib. If this is your
174 case, you should create a link to it in /etc. Suggested by David Wolfskill
179 According to Michael Galloway <mgx@spruce.lsd.ornl.gov>, the stock DUX4 dump is
180 broken. There is a patch available at ftp://ftp.service.digital.com/public/
181 dunix/v4.0b/duv40bas00005-19970926.README
182 When both dump and vdump are available, AMANDA will use vdump for backing up
183 advfs filesystems only, and dump will be used for the rest. If you'd rather
184 back up all filesystems with vdump, #undef DUMP in config/config.h after
186 Unfortunately, the output of `dump -E' incorrectly matches a line of output
187 from SAMBA, which gets AMANDA's estimate process confused. client-src/
188 sendsize.c will refuse to compile if both HAVE_DUMP_ESTIMATE and SAMBA_CLIENT
189 are defined in config/config.h. AMANDA will work correctly if you undefine
190 HAVE_DUMP_ESTIMATE in config/config.h; if you prefer to have incorrect
191 estimates for SAMBA backups, follow the instructions in client-src/sendsize.c
192 on removing the compile-time error.
193 According to Oren Laadan <orenl@cs.huji.ac.il>, DEC compiler version "DEC C
194 V5.2-033 on Digital UNIX V4.0 (Rev. 564)" (obtained with "cc -V") does not
195 build AMANDA properly, in particular, taper.c. Using gcc is OK.
197 Sinix 5.43 (Reliant Unix)
199 The use of `amsinixfixdevs' is deprecated, since you can list mount-points or
200 full device names in the disklist. The script may be removed in future releases
202 Sinix port originally by Michael Schmitz <mschmitz@iname.com>.
206 When setting the tape device name in either amanda.conf or one of the changer
207 configuration files, make sure you specify the "variable" device name, which
208 has a 'v' on the end. If not, IRIX will write 4KByte blocks instead of the
209 32KByte blocks AMANDA tells it to. This apparantly works OK unless you take the
210 tape to a non-IRIX system, where amrestore will complain about a short (4096)
212 If you do end up in this situation, the dd command to use to pipe into your
213 system restore program is:
215 dd if=/dev/whatever bs=4k skip=8 | ...
218 Jean-Francois Malouin <Jean-Francois.Malouin@bic.mni.mcgill.ca> reports that,
219 if you are going to use an IRIX host as the tape server, you *must* patch your
220 system with *all* kernel and scsi rollup patches, otherwise you may end up with
221 useless tapes, due to tape rewinding after short periods of inactivity. See
222 http://www-viz.tamu.edu/~sgi-faq/ for more details.
223 Some unpatched version of xfsdump are reported as not printing estimates. This
224 causes estimates to take much longer than they had to, because backups are
225 always performed twice. According to Mike Acar <mike@kentinfoworks.com>, patch
226 2333 for IRIX 5.3 and 6.1 will fix this problem.
230 Seems like SGI make program is a bit broken, in a way that causes it to rebuild
231 some files if doesn't have to if you happen to run make again. Using GNU make
233 If you have xfs filesystems to back up, AMANDA will pick xfsdump automatically.
237 Luc Lalonde <Luc.Lalonde@polymtl.ca> contributed the following notes:
238 If you use a jukebox, you must set the ownership of the robot-changer device to
239 the AMANDA operator:group in /etc/ioperms. Here's my configuration:
241 /etc/ioperms: /dev/scsi/sc8d6l0 0600 amanda backup
243 Otherwise the ownership:group is changed to "root:sys" after each reboot. When
244 you do upgrades, check the file /var/sysgen/master.d/scsi to see if it has
245 changed. Otherwise your jukebox could be rendered unuseable. In particular,
246 check if it has been replaced by a new version and renamed to "./scsi.O/.".
247 If you use the AMANDA package provided by freeware.sgi.com, you are not
248 affected by the first question since at compile time the AMANDA operator is
253 Jens Krause <jens@transcom.de> has reported some problems with GNUtar 1.12 on
254 SCO Release 5. Although the `sparse' files patch was applied, GNU tar would
255 consistently crash. GNUtar had to be built linked with malloc-libraries, and
256 the `--sparse' switches had to be removed from client-src/sendbackup-gnutar.c
257 and client-src/sendsize.c.
261 chg-scsi was not updated to support the new camlib.h-dependent chio.h, so chg-
262 scsi will be automatically disabled if camlib.h is found. You may use chg-chio
267 Sep. 28th, 2004: Jason Miller <jwm@interlinc.net> reported problems with
268 setting up the AMANDA-client on FreeBSD 4.9. He wrote:
269 Due to the need for read permissions for AMANDA-client the default user and
270 group for this on FreeBSD 4.9 is "operator:operator" which I found a write up
271 on that as well. Just a note the port wanted to install it with these user
272 permissions by default and I initially changed them to match my Redhat 9.0
273 install. So just doing a
274 make distclean uninstall install AMANDA_SERVER=servername
275 fixed that for me. Then I just followed the below instructions and everything
277 Refer to this link for more details: http://www.freebsd.org/cgi/query-
282 Nicolas Ecarnot <nicolas.ecarnot@accim.com> discovered that for FreeBSD 5.1
283 (maybe earlier, and surely further), you have to set the net.inet.udp.maxdgram
284 TCP/IP variable to 65535. The default is 9216, and this is a problem when
285 trying to backup a large number of clients as indicated by errors in during
286 amcheck or the estimate phase.
287 You can just run the command:
288 sysctl net.inet.udp.maxdgram=63535
289 but this won't last until the next reboot.
290 To make it permanent, just add this line:
292 net.inet.udp.maxdgram=65535
295 in the file /etc/sysctl.conf.
299 sendsize is reported to coredump on AIX 4.3.3, this is a linking problem, try
300 configuring AMANDA with the option "--disable-shared".
304 Although AMANDA won't run standalone on MS-Windows hosts, it is possible to use
305 it to back up their disks, by using SAMBA. Please read Backup_PC_hosts_using
306 Samba for more information.
307 SAMBA may be unable to back up some files due to file locking restrictions.
308 Particularly, paging and registry files usually present problems. Backing up
309 page files is pointless, but registry files are quite important to back up. It
310 is possible to create regular files that contain registry information by using
311 the Regback utility, from the Windows NT Resource Kit. Unfortunately, it is not
312 part of the Windows NT standard distribution, you have to purchase it
313 separately. Thanks to Ernie Oporto <ernie_oporto@mentorg.com> for the tip.
317 For notes on how to setup AMANDA under Apple's OS X, please refer to http://
318 web.brandeis.edu/pages/view/Bio/AmandaMacOSXCompileNotes, written by Steven
319 Karel<karel@brandeis.edu>. Thanks to Jose L.Hales-Garcia <jose@stat.ucla.edu>
321 -------------------------------------------------------------------------------
324 Part I. Installation Home Chapter 2. AMANDA Installation Notes