> On 15 Feb 2002 at 6:02am, [EMAIL PROTECTED] wrote
>
> > It did produce the following error however. I am not a Windows person
> > so I don't know, but I presume from the file name that this is something
> > to do with the Windows swap space and it is normal. If so, should I
> > expect to see it every day, or is there a way to prevent it?
> >
> > FAILED AND STRANGE DUMP DETAILS:
> >
> > /-- gorn.ameri //zena/C lev 0 STRANGE
> > sendbackup: start [gorn.americom.com://zena/C level 0]
> > sendbackup: info BACKUP=/usr/bin/smbclient
> > sendbackup: info RECOVER_CMD=/usr/bin/smbclient -f... -
> > sendbackup: info end
> > | Added interface ip=192.168.2.1 bcast=192.168.2.255 nmask=255.255.255.0
> > ? ERRDOS - ERRbadshare opening remote file \WINDOWS\WIN386.SWP (\WINDOWS\)
> > | tar: dumped 12935 tar files
> > | Total bytes written: 639080448
> > sendbackup: size 624102
> > sendbackup: end
> > \--------
>
> You're exactly right -- that's the swap file, and you can't open it. You
> could exclude it in your dumptype, or just ignore the error.
I would like to exclude it, but the sample amanda.conf file (from which
I derived the one I am using) says I can't, under the comments for
dumptypes:
# dumptypes
...
# exclude - specify files and directories to be excluded from the
# dump. Useful with gnutar only; silently ignored by dump and samba.
Is this information outdated. That is, does it actually work with
samba? I tried:
define dumptype americom-samba {
americom-standard
program "GNUTAR"
exclude "/WINDOWS/WIN386.SWP"
}
but it did not work. Do I use backslashes, or is there anything else I
need to do?
Thanks,
Dick
