dump/restore

[Brian Beattie]

In article <8373 at alice.UUCP> debra at alice.UUCP () writes:
>In article <44433 at beno.seismo.CSS.GOV> rick at seismo.CSS.GOV (Rick Adams) writes:
>>...
>>A BACKUP program should be able to restore the disk to the state it
>>was at the time of the backup. It should also offer incremental backups.
>
>Right, and since there is no way to reset the create-time on a Unix system
>(except by setting the date and resetting it but that's awful and can never
or writting the inode by writting the raw device as dump/restor does.
>be used in a multiuser environment) there are NO backup programs that can
you should never dump an active filesystem.
>restore the disk to the state it was at the time of the backup since this
>is simply not possible in Unix.
>The only way to restore the disk is if you make a complete image, using
>volcopy or dskcpy or whatever it is called (depending on the Unix version)
or dump/restor if ATT has not castrated you system.
>but those programs cannot offer incremental backups.
dump/restor will do incremental backups just fine.  It is true that
an _incremental_ _restor_ will not set the create time back but that too
could be worked if necessary.
>
>Paul.
>
>-- 
>------------------------------------------------------
>|debra at research.att.com   | uunet!research!debra     |
>------------------------------------------------------

l
i
n
e

c
o
u
n
t

f
o
d
d
e
r
-- 
    _ANYONE_     | Brian Beattie          (703)471-7552
can sell software| 11525 Hickory Cluster, Reston, VA. 22090 
that has already | beattie at visenix.UU.NET
been written     | ...uunet!visenix!beattie