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=<fileref> 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 <path>/vob_standard.sh lock ("lock" as
argument) and after backup is finished, <path>/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
