I've used tar, the admin backup, BackupEdge, BRU, and Lone-tar. The problem with tar and most admin backups are they DO NOT VERIFY the data after the backup. You won't know if the backup is valid until you try to restore it. I found that out the hard way.
BackupEdge, BRU, and Lone-tar are the best, IMHO, backup packages available for Unix. The last time I used BRU, I had to modify scripts while the other two were menu driven. That may have changed since. Of the three, I like Lone-tar a little better. It not only had menus but scripts that could be modified, too. You could things both ways. Also, and this was the big one, Lone-tar has "Air-Bag" for SCO.
Air-bag allows the user to create a series of bootable disks that contained a copy of the OS as the user had on the hard drive. If the hard drive is trashed, the user can put in a new hard drive, boot from the floppies, and restore the OS and data. Some dealer used this to create SCO boxes en-masse.
I think that BackupEdge also has something similar now. I'm not sure if BRU is even available now. We still use BRU on our old DG box so you know it was a solid performer.
All three verify the data afterwards. They compare the data on the backup device to the data hard drive after the backup. Again, Lone-tar was the easiest to set up. I could tell Lone-tar to skip temp files, spoolers, etc. that would change between the backup and the verify. BackupEdge was harder to do this on, and BRU only allowed different levels of verification. Again, things may have changed since the version I used. James P. Cottingham
When a man sits with a pretty girl for an hour, it seems like a minute. But let him sit on a hot stove for a minute and it's longer than any hour. That's relativity.
[tab][tab]Albert Einstein explaining his Theory of Relativity to a group of journalists.