Winston Sorfleet <[email protected]> writes:
> Greetings all. I was wondering if other eyes can spot something obvious I'm
> missing, with respect
> to how amanda invokes GNUTAR on client machines (the amdump logfile doesn't
> show anything
> unusual). It may be in the guts of /usr/lib/amanda/application/amgtar or
> runtar but short of looking
> at code I am not familiar with, I can't tell.
>
> I have amanda running on a server, with client machine forum.romanus.ca, and
> it's started giving
> me "STRANGE dump details":
gnutar uses --one-file-system option, so it will not save what is
mounted from a different filesystem.
You must have a DEL for each of your filesystems:
/
/bin
/etc
/...
Olivier
>
> /-- forum.romanus.ca / lev 1 STRANGE
> sendbackup: start [forum.romanus.ca:/ level 1]
> sendbackup: info BACKUP=/bin/tar
> sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -xpGf - ...
> sendbackup: info COMPRESS_SUFFIX=.gz
> sendbackup: info end
> ? /bin/tar: ./bin: directory is on a different filesystem; not dumped
> ? /bin/tar: ./dev: directory is on a different filesystem; not dumped
> ? /bin/tar: ./etc: directory is on a different filesystem; not dumped
> ? /bin/tar: ./lib: directory is on a different filesystem; not dumped
> ? /bin/tar: ./opt: directory is on a different filesystem; not dumped
> ? /bin/tar: ./proc: directory is on a different filesystem; not dumped
> ? /bin/tar: ./run: directory is on a different filesystem; not dumped
> ? /bin/tar: ./sbin: directory is on a different filesystem; not dumped
> ? /bin/tar: ./sys: directory is on a different filesystem; not dumped
> ? /bin/tar: ./usr: directory is on a different filesystem; not dumped
> ? /bin/tar: ./mnt/nvme0n1: directory is on a different filesystem; not
> dumped
> ? /bin/tar: ./mnt/vhosts: directory is on a different filesystem; not dumped
> ? /bin/tar: ./var/spool/fax/incoming: directory is on a different
> filesystem; not dumped
>
> Now recently, I moved these directories off a standard hard disk, to an nvme,
> using btrfs.
> Because, reasons (trying to do this with a live machine, not from bare-bones
> install) I did these as
> bind mounts, e.g. in /etc/fstab
>
> /dev/nvme0n1 /mnt/nvme0n1 btrfs defaults 0 2
> /mnt/nvme0n1/bin /bin none bind
> /mnt/nvme0n1/etc /etc none bind
> /mnt/nvme0n1/lib /lib none bind
> /mnt/nvme0n1/opt /opt none bind
> /mnt/nvme0n1/sbin /sbin none bind
> /mnt/nvme0n1/usr /usr none bind
>
> Now if I'd being doing some sort of one-file-system exclusion, I could
> understand why tar (as
> demanded by amanda) would drop them, but as far as I can tell, I'm not:
>
> The disklist (/home being an nfs mount from the server machine, it gets
> backed up with the
> server-as-amanda-client).
>
> forum.romanus.ca / {
> comp-root-tar
> # auth "bsdtcp"
> exclude append "./home"
> }
>
> (Note that the server's amdump log file does show the intentional exclude):
>
> driver: send-cmd time 263.809 to dumper2: SHM-DUMP 02-00003 44577 NULL 1
> forum.romanus.ca ffffffff9efefbfffffffffffffff3fffbf71f / N
> ODEVICE 1 2019:5:22:6:47:2 GNUTAR "" "" "" "" "" "" "" 1 "" "" bsdtcp AMANDA
> /amanda_shm_control-16837-0 20 |" <auth>bsdtcp</auth>\
> n <compress>FAST</compress>\n <record>YES</record>\n <index>YES</index>\n
> <datapath>AMANDA</datapath>\n <exclude>\n <file>./home</file>\n
> </exclude>\n"""
>
> And the dumptype definition:
>
> define dumptype root-tar {
> global
> program "GNUTAR"
> comment "root partitions dumped with tar"
> compress none
> index
> priority low
> }
>
> define dumptype comp-root-tar {
> root-tar
> comment "Root partitions with compression dumped with tar"
> compress client fast
> }
