frecover halt

[Juuso Siniketo]

Hi,

I took a full backup via SAM of k360 system with 3x4gb disk set (mirrored) running 10.20.
Everything went ok - no errors etc.

Last week I tried to restore this backup partially from the tape so that only /opt
/etc and /var would be restored. Everything went ok until frecover made it to the last file to be restored and stopped right there.

I waited about for a + hour and finally hit ctrl-c to exit the restoring process.
Frecover flashed to the screen something like "/opt/HP-AIN could not be restored due to sync ..something..". I checked sam log file and found nothing interesting.

Does anyone know what exactly happened there with frecover? Bad tape? Somekind of mysterious delay due to a partial restore from full backup?

-juuso

[CHRIS_ANORUO]

It could be that the file you were restoring was not properly backed up or while restoring , the overwrite was having problem because it cann't restore on an active/busy file.

[James R. Ferguson]

Hi:

Chris makes a good point. 'fbackup' is designed to work while files are inuse. It attempts to insure a good copy of a file is placed on tape by comparing the timestamp of the file at the end of the copy to the timestamp of the file seen at the beginning of the copy. If these do not match, fbackup marks the file as "bad" and retries the copy. The retry (maxretries) default is five (5).

It would be intesting for you to do a "dummy" recovery from the tape with which you had problems. Try the following:

# frecover -Nmv -f /dev/rmt/0m -x -i /etc -i /opt -i /var > /tmp/frecover.log 2>&1

This will NOT (-N) recover any files but will read the tape as if it was actually doing the recovery. Any errors will be reported along with the files "recoverd" in the /tmp/frecover.log file.

...JRF...