Date: Thu, 1 Apr 2004 23:00:16 +0200 From: Christoph Sold <cs@cheasy.de> To: sellis@telus.net Cc: freebsd-isp@freebsd.org Subject: Re: tape backup from remote Message-ID: <200404012300.27578.cs@cheasy.de> In-Reply-To: <20040401064322.GA62696@telus.net> References: <20040329183323.GC51870@telus.net> <86wu51oukz.fsf@PECTOPAH.shenton.org> <20040401064322.GA62696@telus.net>
next in thread | previous in thread | raw e-mail | index | archive | help
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 01 April 2004 08:43, Sean Ellis wrote: > On Wed, Mar 31, 2004 at 11:22:04AM -0500, Chris Shenton wrote: > > Christoph Sold <cs@cheasy.de> writes: > > > Amanda dumps (or tars -- your choice) to a holding disk on the > > > backup server. After enough data has been collected to stream to > > > tape, the tape is started. Keeps the tape streaming. > > > > I've also used Amanda and like it for this reason. The only > > problem, > > I'm looking at the Amanda suggestions. > > Just to get the ball rolling I decided to make local copies of the > more important files with rsync. Until the tape is installed and up. > > I copied a directory tree last night using -avz as switches, no > daemon running; the files lost their ownership in the copying. I've > been searching and doing some experimenting. Running rsync as a > daemon on the backup server with uid =3D root in the rsyncd.conf seems > to preserve the ownership. Is there a better way of achieving this? > Most of the users and groups on the source machine don't exist on the > destination machine. Both tar as well as dump keep uid and gid _numerically_. Restoring to=20 the original machine as root yields the expected results. If you use=20 newer features of the file system such as ACLs, keep in mind tar is not=20 up to the job -- use star from the ports instead. During restores, the restore job _must_ be run with root privileges --=20 otherwise restore maybe cannot write to a just restored directory.=20 rsync has its uses as project synchronization mechanism, but won't do=20 good when the user/group lists differ between machines. It was not=20 designed as backup mechanism, see? Regardless which backup application you use, it is possible to tunnel=20 the backup through ssh onto any remote machine. No need to cannibalize=20 rsync for remote backups. See=20 http://lists.freebsd.org/pipermail/freebsd-isp/2003-July/000793.html=20 and following, further googling turns up more results. HTH =2D -Christoph Sold =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAbILmjGVuYEZ1RPYRAhxOAJ0eo85gEcsQT2C46odVa5bIvvRlHgCgm+BB =46B9L2OxFa0DHq7kk55rt6wo=3D =3DeUnR =2D----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200404012300.27578.cs>