Date: Thu, 11 May 2006 16:04:10 -0400 (EDT) From: Jerry McAllister <jerrymc@clunix.cl.msu.edu> To: don@lizardhill.com (Don O'Neil) Cc: freebsd-questions@freebsd.org Subject: Re: Copying a file system w/ tar - symbolic links not copied right. Message-ID: <200605112004.k4BK4AAr021804@clunix.cl.msu.edu> In-Reply-To: <049201c67525$dc159700$0300020a@mickey>
next in thread | previous in thread | raw e-mail | index | archive | help
> > I've tried both the BSD and GNU tars, I get the same results on both. It's > very strange. > > When I add the B option, no different.... I used: > > tar cf - /array01/* | ( cd /mnt/disk01 && tar xfvBp - ) > > Maybe this is something specific to 4.11? > > Here's what happens: > > Source file: > > lrwxrwxrwx 1 root wheel 21 Feb 19 03:05 apache.log -> > /var/shc/apache/logs/ > > Destination file created on the tar backup: > > ---------- 1 root wheel 0 May 11 11:02 apache.log > > Some have suggested using dump/restore. The problem with dump/restore is > that I can't do it across the network and the file systems need to match. > The whole point is to move these files/directories from one server to > another to a volume with a LOT more space on a RAID array. I used to do it over the net regularly with dump/restore. Just take advantage of the pipe ability. Since the other system has so much room, just pipe the dump file over there and unroll it with restore on the other machine as you please or just leave it in a dump file if you don't want. ////jerry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200605112004.k4BK4AAr021804>