Hi,

I've recently been doing more-than-my-usual backups after making some
changes in the Sun cluster here.  As I like to do, I want to test
the backups by attempting a restore of one of the directories on one of
the disks that has just been backed up.

The backups seem to be running normally but, as I'm trying to restore a
directory just under 100 megs from one such backup, it runs
strangely slowly.  After starting the restore (using 'amrecover'), I
check that files and directories are indeed being created.  Good.  I
think, "hmmm, a 100 megs, should take well less than an hour".  Yet
after running quite awhile, I decided to leave it to finish while at
lunch.  Returning an hour or so later, I returned to find the program
still running.  The read light on the tape drive continued to flash yet
the size of data on the client disk was apparently not changing.  Thinking
something must be wrong, I aborted 'amrecover' and restarted things.
Afterall, I was playing around with the /etc/services file during
the restore.

This following time, not having erased the files and directories that were
restored the first time to the client disk, I can't see that anything
is being restored.  'df's of the partition and 'du's of the
directory show no change in size though, as with the first time, the tape
drive read light is slowly flashing away.  The only proof that anything has
happened at all was the appearance of a finite number of:

restore: <filename>: File exists

which appeared awhile after beginning the extraction though no
activity has been seen since.

Is there anyway to monitor amrecover's activity?  I checked the
man page for a verbose flag but apparently this doesn't exist.  I
could stop things again and try the restore with 'amrestore'
directly using the verbose mode with 'ufsrestore' but only part of
this test is to ensure that I can really restore things.  The
other is to prove I can use 'amrecover' to do so.  If I can't
get amrecover to work, I might as well turn indexing off.

-- 
Paul Yeatman    (858) 534-9896      [EMAIL PROTECTED]
        ==================================
        ==Proudly brought to you by Mutt==
        ==================================

Reply via email to