It's been years since I've used dump/restore, and I can't say I've used
it on Linux, but as far as I know its still got its BSD roots.
"i", "x" and "r" should be mutually exclusive options.
"i" is for an interactive restore, where you can pick and choose files
and directories.
"x" is to extract either everything or a named path. I rarely used this
option.
"r" is to restore the whole filesystem. A checkpoint file is maintained
(restoresymtable I believe) that allows for restoring a full dump, then
incrementals, and properly removing files that no longer existed at the
time of the incremental. This is what you want to use if you are
restoring the whole filesystem, especially if you need to restore a set
of incrementals.
restore always extracted to current directory.
It looks like Linux also supports a -N option, which will not actually
write to any files on the filesystem.
Scott Ehrlich wrote:
Now that I'm back at work, I reviewed the restore man page and some
other web pages on restore, and want to verify:
I'm in a scratch/temp directory, and type:
restore rf (maybe with i, too) /dev/tape
the result will restore the dump to the current scratch/temp location so
nothing in the active filesystem is overwritten?
If true, I'll test it asap.
Please advise.
Thanks.
Scott
_______________________________________________
bblisa mailing list
[email protected]
http://www.bblisa.org/mailman/listinfo/bblisa
_______________________________________________
bblisa mailing list
[email protected]
http://www.bblisa.org/mailman/listinfo/bblisa
