Wolfgang Weisselberg wrote:
> Trying to kill the keyboard, [EMAIL PROTECTED] produced:
> > I did give some time, as its a cron job and the tape has only been
> > removed a few times. my backup script is as follows:
>
> > ftmt -f /dev/nqft0 reten
> > ftmt -f /dev/nqft0 erase
> > ftmt -f /dev/nqft0 rewind
> > tar czvf /dev/nqft0 /
> > ftmt -f /dev/nqft0 rewind
>
> > perhaps there isn't enough time between the ftmt commands and the tar
> > command?
>
> I think so.
>
> Now, first you compress the tar archive. That is *bad*.
> If you get just a single bit error (it should not happen,
> but it will once you need the backup!) ... you will loose
> every file and directory after the bit error.
Use bzip2 instead of gzip - it operates with blocks and if you loose a
single bit, you only loose one bzip2-block, which is around 900k of
compressed data.
I also like to have a checksum over my backup and bzip2 fits well for
that, too. There is one thing even worse than a lost backup: a backup
with badly wrong restored data which you are not even aware of.
Greetings
Christian
