On Tue, 4 Jun 2002 at 10:26am, GOODWYN,RON (HP-USA,ex1) wrote
> 1. Can the tape server be a system other then the AMANDA server or a system
> acting as both the client and the server. So in other words, lets say you
> have systems A, B, and C. System A is the client. System B, is the AMANDA
> server and system C is the tape server. Does the AMANDA architecture allow
> for this?
I don't believe that there's any easy way to do this. You could kludge it
by writing to disk, transferring the images to C, and then putting them on
tape by hand. You'll be forced to do the tape accounting by hand,
however.
> 2. Does there have to be a tape device on the AMANDA server to successfully
> complete an archive generation, using amdump? I know that the "reserve"
> keyword in the amanda.conf file can take on various settings. However, I
> read in another newsgroup posting that AMANDA will by default attempt to
> create incremental backups when writing to the holding disk. Is there a
> way to tell AMANDA to write to the holding disk without it being
> incremental?
There are two ways to do backups (both full and incremental) to disk.
1) Set reserve to something low, and do backups without a tape in the
drive (or without a tape drive). Reserve is how much holding disk space
is set aside for incrementals in "degraded" (i.e. no tape) mode, so a low
value leaves space for level 0s.
2) Use the file: driver in 2.4.3bN ("b is for beta"), which uses files on
disk as if they were tapes.
> 3. Is there a way to configure AMANDA to use udp instead of tcp or
> vice-versa?
No. Amanda uses udp for communication (setting up ports, getting
estimates, etc), and tcp for streaming the actual backup data. You can
restrict the portranges used at configure time, however. See ./configure
--help, docs/PORT.USAGE in the 2.4.3b3 distro, and the list archives for
more gory details on this.
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
