Re: Amanda configuration, vxfs and ClearCase
> 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]
RE: Amanda configuration, vxfs and ClearCase
Ok, maybe I'm slow but I need some deeper explanation to this. I believed
that Amanda picked up the right dump program to use depending on what kind
of fs present on the actual partition/device i.e vxdump on vxfs and ufsdump
on ufs (Solaris). If compiled with --with-gnutar= option, how can
Amanda still work with vxdump/ufsdump? How will the disklist amanda.conf
(define dumptype global part) file look like for such configuration? The CC
script to call before backup is /vob_standard.sh lock ("lock" as
argument) and after backup is finished, /vob_standard.sh unlock (this
could be two different scripts like lock.sh an unlock.sh if easier)
--Peres--
-Opprinnelig melding-
Fra: Will Partain [mailto:[EMAIL PROTECTED]]
Sendt: 5. februar 2001 13:23
Til: [EMAIL PROTECTED]
Emne: Re: Amanda configuration, vxfs and ClearCase
"Stiansen, Per Sverre" <[EMAIL PROTECTED]> writes:
> 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?
You build amanda --with-gnutar=/usr/local/sbin/gnutar-for-amanda
(your choice of name, of course), then write a script that,
on the outside, behaves like GNU tar, but on the inside does
ClearCase magic when required. I can send a Deeply Ugly
one, if necessary.
Will
Re: Amanda configuration, vxfs and ClearCase
"Stiansen, Per Sverre" <[EMAIL PROTECTED]> writes: > 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? You build amanda --with-gnutar=/usr/local/sbin/gnutar-for-amanda (your choice of name, of course), then write a script that, on the outside, behaves like GNU tar, but on the inside does ClearCase magic when required. I can send a Deeply Ugly one, if necessary. Will
