On Fri, 15 Feb 2002, Dave Edick wrote:
>I'm in the process of setting up an Amanda backup server to back up a
>collection of new servers. The Linux and Solaris servers aren't posing
>any problems so far. But I also have to back up a SNAP 4100 appliance. In
>my old pre-amanda backup scheme, I was backing it up as an NFS volume, but
>evidentally Amanda doesn't do NFS volumes (please correct me if I wrong on
>this). So I set it up to back up using Samba. I installed the latest
>Samba and ran a manual smbtar, which worked. But when I run the nightly
>Amanda backup, it wigs out. It shows that it's backing up about 3.5Mb,
>but there is really about 3GB on the SNAP server. I included the output
>from amdump below. I run full backups every night.
>
>Any ideas what I'm doing wrong?
In my opinion, adding the complexity of samba is wholly unnecessary
unless you are actually backing up a Windows system. I have one linux
machine here which has exhibited some very bizarre glibc issues and so I
am unable to get an amanda client working on it. This machine at this
time is a temporary situation and will get replaced in the next couple
of months. In order to facilitate backing it up in the meantime I have
it NFS exporting itself to my amanda backup server. The amanda backup
server then automounts those partitions from the client. In the
disklist I just have:
backuphost /path/to/nfs/mount tar-NOTdump
It's very straightforward. Amanda will backup any mounted partition,
including NFS ones, so long as you are using GNUtar.
--
Brandon D. Valentine <[EMAIL PROTECTED]>
Computer Geek, Center for Structural Biology
"This isn't rocket science -- but it _is_ computer science."
- Terry Lambert on [EMAIL PROTECTED]
