> 1. We don't want to install a compiler on the CC server ...
>... Will Amanda build ok (with vxfs support) if I copy the
>/usr/lib/fs/vxfs dir from the CC server to Amanda server?
That will work, or you can just set the VXDUMP and VXRESTORE environment
variables to the correct path (on the client) before running ./configure
(make sure you "make distclean" first).
> 2. Which files/directories needs to be on the client as a
>minimum to function properly? Remember that I don't want to build on the
>client directly nor want to use an NFS share.
It will be difficult to give you a list of files. My suggestion would
be to use --prefix to install the client built version someplace all by
itself (e.g. --prefix=/opt/amanda-CC) and then rdist that to the client.
> 3. To successfully back up a CC server, the VOBs needs to be
>locked. This is normally done with a script. How can I force the client to
>run a script before (and after to unlock the VOBs) backup is executed?
Amanda doesn't yet have callouts for doing this kind of thing directly
(it's in the works), so the usual trick, as Will stated, is to configure
Amanda on the client to call a special version of GNU tar and set it to
run GNU tar for that client via the dumptype. That does **not** mean it
actually runs GNU tar, just that it calls a script it thinks is GNU tar.
The script can do anything it wants, which in your case would be locking
the VOBs, calling vxdump, then unlocking them.
I have some examples of how to set up a general wrapper at:
ftp://gandalf.cc.purdue.edu/pub/amanda/gtar-wrapper.*
You'll have to fill in the locking/vxdump/unlocking pieces, but hopefully
the hooks provided will make that easy.
>--Peres--
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
