specifying gnutar, trouble with OSF1 file system

2002-06-23 Thread John Koenig
Using AMANDA version 2.4.2p2 on OSF/Tru64 v5.1 On the client side, amanda is sending an inappropriate parameter to the /sbin/dump = sendsize: running "/sbin/dump 0Esf 1048576 - /net/home1" running /usr/local/amanda-2.4.2p2/libexe

Re: specifying gnutar, trouble with OSF1 file system

2002-02-06 Thread John R. Jackson
>Question: Have all these patches been rolled into post-2.4.2p2 builds? Yup. >Oh... and the no-record option does perform the backup however with >this dumptype specified the "backup command" (e.g. dump, vdump, etc) >will not update its state file (e.g. /etc/dumpdates) Right. John R. Jackson

Re: specifying gnutar, trouble with OSF1 file system

2002-02-05 Thread Ashley
What dumptype specs are you using for your disklists? define dumptype root-tar { global program "GNUTAR" comment "root partitions dumped with tar" compress none index yes record yes exclude list ".amanda_excludes" strategy nofull priority low maxdumps 3 }

Re: specifying gnutar, trouble with OSF1 file system

2002-02-04 Thread John Koenig
A lot of my issues with the client and dump were resolved by using the "advfs.diff" patch located here: Question: Have all these patches been rolled into post-2.4.2p2 builds? "All the sudden" amanda and vdump and everything is just working like a charm on

specifying gnutar, trouble with OSF1 file system

2002-02-04 Thread John Koenig
Using AMANDA version 2.4.2p2 on OSF/Tru64 v5.1 On the client side, amanda is sending an inappropriate parameter to the /sbin/dump = sendsize: running "/sbin/dump 0Esf 1048576 - /net/home1" running /usr/local/amanda-2.4.2p2/libexe