Hi!
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.
Second, you do no need to erase the tape, IIRC. Just starting
to write from the beginning (instead of appending) should do
the job.
> but judgung from the way the error reads, i think one of tar's child
> processes is getting in the way.
That is the compressing, too.
Just let the tape wait for a (long?) time.
> i was thinking, maybe it is backing up
> /dev/nqft0 or something in proc and that is getting in the way.
Well, you need to check that only the filesystems you want are
actually backupped. You don't need /tmp nor /proc (apart from
the mountpoint/directory itself). Nor do you want the data from
the /dev/* special files, just the special files themselves.
Probably tar is not the right backup method here, you might
want to look into dump/restore or afio or some backup package.
> mnt/hda3/home/colin/devel/muse1.9f3/
> mnt/hda3/home/colin/devel/muse1.9f3/working.tar.gz
Let me guess, colin the bot?
-Wolfgang
