When you use tar, the destination filesystem won't get a chance
to see or
muck with any of the attributes of the backed-up files. Probably the only
likely problem is with file-size limits.
FWIW, tar can back up changes only, by keeping a list of files it has
backed up. See option --listed-incremental in "info tar", and the section
on Backups. I find info to be inscrutable, so "info tar", U, cursor down
to Backups, Enter.
If you compress the resulting files, you have more risk that a single error
can make all of a backup (or at least any following incrementals) useless.
I wonder if there is a tool to add redundancy, like .par files on usenet?
(Note that I have only read about this stuff; I have no actual experience.)
____________________________________________________________________
TonyN.:' <mailto:tonynelson@georgeanelson.com>
' <
http://www.georgeanelson.com/>
Hi, I know this thread is basically dead, but I was thinking of simply
using cp to perform a backup:
cp -dpRux source/ dest/
my question is how would I wrap this into a gzip archive (again to
preserve file attributes which SMB cannot handle.) Additionally, would
the whole archive have to be recreated each time or would it be able to
insert the appropriate changes.
If you guys think it will have to recreate the entire archive each time,
I guess I will just use tar then.
Thanks,
Julian