* Jean-Francois Malouin <[email protected]> [20100429 
14:58]:
> Hi,
> 
> First go with amanda-3.1.0beta2 on a Debian/Lenny 64bit box.
> Configured with:
> 
> export CFLAGS='-m64'
> 
> ./configure                                 \
> --with-testing=test                         \
> --prefix=/opt/amanda-3.1.0beta2             \
> --mandir=/opt/amanda-3.1.0beta2/man         \
> --with-tmpdir=/var/tmp/amanda-3.1.0beta2    \
> --with-amperldir=/opt/amanda-3.1.0beta2/perl \
> --with-config=test                          \
> --with-user=amanda                          \
> --with-group=disk                           \
> --with-bsdtcp-security                      \
> --with-amandahosts                          \
> --with-tape-device=tape:/dev/nst1           \
> --with-tape-server=watch                    \
> --with-index-server=watch
> 
> My first test was with a simple vtape changer and I can apparantly
> back up the client but how do I go around the fact that the switch
> `--with-testing' doesn't do what it's supposed to do: amrecover tries
> to connect to port 10080/tcp rather than the one I configured it with
> (amanda-test 22224/tcp). The problem it that the server is already an
> amanda server running 2.6.1p2 and is in production so when I start
> amrecover it connect to the amanda port as defined in inetd.conf:
> 
> ~# /opt/amanda-3.1.0beta2/sbin/amrecover -C test -s watch -t swatch
> AMRECOVER Version 3.1.0beta2. Contacting server on watch ...
> 220 watch AMANDA index server (2.6.1p2) ready.
> Setting restore date to today (2010-04-29)
> 200 Working date set to 2010-04-29.
> 501 Could not read config file for test!

Ah! Next time I should read the release notes with both eyes open!
I think the answer is:

* Amanda server configuration file changes (amanda.conf)
  o new configuration keyword
    + client_port -- in dumptype, to specify which port to connect on
                     the client.

* Amanda client configuration file changes (amanda-client.conf)
  o new configuration keyword
    + client_port -- use by amrecover, specify which port to connect on
                     the server.

Just added the bits in, then:

~# /opt/amanda-3.1.0beta2/sbin/amrecover -C test
AMRECOVER Version 3.1.0beta2. Contacting server on watch ...
220 watch AMANDA index server (3.1.0beta2) ready.

jf

> 
> Short of installing 3.1.0beta2 on a host without prior amanda
> installation is there a way to test and experiment using another
> tcp port for communication?
> 
> One more things: notice the 'part X/UNKNOWN' in the amfetchdump
> output below. Normal?
> 
> ~# su amanda -c \
> "/opt/amanda-3.1.0beta2/sbin/amfetchdump -p -d chg-disk:/vtapes \
> test gustav /raid/hrrt/SCS_SCANS 20100428 "| tar -xpGf -
> 2 volume(s) needed for restoration
> The following volumes are needed: vtape-1 vtape-2
> Press enter when ready
> 
> amfetchdump: 1: restoring split dumpfile: date 20100428171243 host
> gustav disk /raid/hrrt/SCS_SCANS part 1/UNKNOWN lev 0 comp N program
> APPLICATION
> ...
> amfetchdump: 12: restoring split dumpfile: date 20100428171243 host
> gustav disk /raid/hrrt/SCS_SCANS part 12/UNKNOWN lev 0 comp N program
> APPLICATION
> amfetchdump: 1: restoring split dumpfile: date 20100428171243 host
> gustav disk /raid/hrrt/SCS_SCANS part 13/UNKNOWN lev 0 comp N program
> APPLICATION
> amfetchdump: 2: restoring split dumpfile: date 20100428171243 host
> gustav disk /raid/hrrt/SCS_SCANS part 14/UNKNOWN lev 0 comp N program
> APPLICATION
> amfetchdump: 3: restoring split dumpfile: date 20100428171243 host
> gustav disk /raid/hrrt/SCS_SCANS part 15/UNKNOWN lev 0 comp N program
> APPLICATION
> 
> regards and thanks to the amanda developers!
> jf
> -- 
> <° >< Jean-François Malouin          McConnell Brain Imaging Centre        
> Systems/Network Administrator       Montréal Neurological Institute
> 3801 Rue University, Suite WB219          Montréal, Québec, H3A 2B4
> Phone: 514-398-8924                               Fax: 514-398-8948

Reply via email to