🚀 go-pugleaf

In article <Pine.OSF.3.95.961022024048.12764A-100000@student.uq.edu.au>,
Doug Simon <s325296@student.uq.edu.au> wrote:
| I am installing a backup system to handle the backup of a four machine
| network. To enable backup machine to have access to the remote
| filesystems, I am running the whole thing over NFS. To ensure that the
| backed up files haveees the same ownership atrributes as the original, I
| am also using the ugidd daemon which maps remote uids to local uids.

As my youngest daughter once said, "yuckie-poo!"

I highly suggest setting up a non-priviledged account on the backup
master, which allows an rsh or something similar, and letting the
backup be done to the tape drive on the backup master, from a
program running on the machine being backed up.

Ex:
  find /home -xdev -depth -print | cpio -o -Hcrc |
  rsh backup.your.org -l backupid dd obs=50k of=/dev/tape

Things you can change:
- buffer size
- use non-rewinding tape for multiple machines
- have the backup machine send a message to start the process
- use tar or dump or rdump for backup
- compress before sending
- encrypt before sending

I set up a nice table drive backup scheme for a client a few years
ago, and I have something like this running in my office.
Unfortunately it's undocumented and contains some code I can't share
in the compress programs, but the simple form is, well, simple.

The performance of NFS is not up to a TCP stream, and more
importantly, as you found the hard way, you get into login matching
issues.

If you have lots of disk on a server, you can backup filesystems
using the 'ftpbackup' program and ftp the backup image to the
server, then write to tape. I do that on some small machines.

The real question isn't how to do backup with NFS, but how to do
backup at all. There are lots of options.
--
Bill Davidsen (davidsen@tmr.com)
  What do you mean I shouldn't do thing like that at my age?
  At my age if you don't do things like that you might die of natural causes!