Date: Thu, 30 Nov 2006 11:12:42 -0500 From: Jerry McAllister <jerrymc@msu.edu> To: Christian Walther <cptsalek@gmail.com> Cc: Rachel Florentine <rachel_florentine@yahoo.com>, Marcelo Maraboli <marcelo.maraboli@usm.cl>, freebsd-questions@freebsd.org Subject: Re: Data Recovery Message-ID: <20061130161242.GC4725@gizmo.acns.msu.edu> In-Reply-To: <14989d6e0611300647q3974e751hd84ac4e67c80cb0c@mail.gmail.com> References: <20061130112939.12787.qmail@web57808.mail.re3.yahoo.com> <456EE9E2.7070606@usm.cl> <14989d6e0611300647q3974e751hd84ac4e67c80cb0c@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 30, 2006 at 03:47:53PM +0100, Christian Walther wrote: > I don't think that rsync can cope with hardlinks. > Best way to do a "backup" like this is: > > tar -clf - / | ( cd /ad2 ; tar -xf - ) > > The "-l" flag will stay on the specified filesystem. If you forget > this option tar (and any other command, even cp and rsync with their > respective option) will copy /ad2 into itself, e.g. /ad2/ad2, which > might lead to a kind of recursion. No. Tar isn't good enough. Use dump/restore. It is made for that. ////jerry > > BTW: No, there isn't any tool that might recover from a desaster like > the one you specified. Either the files you describe as being "fried" > have either been overwritten with some other content, or changed in > any other way. You need a backup to recover from this. ;) > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061130161242.GC4725>