Thanks. Lots of ideas there.
J.P: I would be interested to know what is so awful about cpio to tape. The
answers may be amusing and alarming


--
http://www.careprovider.com

"Jean-Pierre Radley" <jpr@jpr.com> wrote in message
news:20040412005136.GA11497@jpradley.jpr.com...
> G3WIP typed (on Sun, Apr 11, 2004 at 08:48:58PM +0100):
> | Two SCO machines . Backup server os 5.06 Main server 5.07.
> |
> | In cron I have
> | copy -rom /nfs-mounted-server/directory /here/safe (you know what I
mean)
> |
> | I am attempting to copy a directory or two so we have a complete working
> | server backup in case the main server goes down. I do not mind it being
a
> | few hours out of date. The staff know the backup will in effect be read
> | only.
> |
> | This may not be the best way to copy or have duplicate files to another
> | server, as I want all permissions and ownerships copied as well. copy
> | command in cron just makes everything owned by root and sys.
> |
> | Better cron backup ideas? Of course the main server does a cpio to
tape of
> | the entire system. I want the staff to be able to click another system
> | should the main server go down and their engineer is on hols (ie me).
>
> Use rdist instead of copy.
>
> And cpio to tape is a *terrible* backup strategy.
> Use BackupEDGE or LoneTar.
>
> --
> JP