Jump to content

Rebuilding Catalogue from Tapes


Recommended Posts

Hi,

 

 

 

At home I have a 17“ iMac (1Ghz / 1Gb) running 10.2.6 and Retrospect Server 5.0.238 with Driver version 3.6.106. This machine uses a FireWire VXA-1 tape drive.

 

 

 

The whole thing acts as a Backup server for itself and other machines on the home LAN.

 

 

 

Recently a catalogue set was damaged and I‘m attempting to rebuild it using the seven VXA tapes that it used.

 

 

 

The process started properly with the status window showing files being added to the catalogue and the catalogue file itself growing in size.

 

 

 

However the first tape has reached some 27Gb restored and I was expecting the usual message about “are there more tapes in this set or is that the end“. However the drive has run for several hours now with the two spinning sprockets being displayed on the screen (so I know it hasn‘t frozen). Once every few hours the tape drive makes a sound like a high speed rewind and I expect the dialogue box to appear or the tape to eject but nothing happens.

 

 

 

Should I revert to an earlier version of the Driver? The tape drive itself has never given me any problems.

 

 

 

Your assistance will be greatly appreciated.

Link to comment
Share on other sites

Hi,

VXA is pretty bullteproof media so it may be as simple as the machine needing a reboot. Be sure to power cycle the tape drive and plug it in to the computer before you power the copmuter up again.

 

Normally that back and forth "shoe-shining" action means the device is unable to read the tape for some reason. Most likely it is only a problem with that one particular tape. I would stop the rebuild and save your progress. Then start the rebuild again from tape #2.

 

Nate

 

Link to comment
Share on other sites

  • 4 weeks later...
  • 2 weeks later...

I have the same problem -- rebuilding a catalog takes FAR too long after the estimated GB has gone by. I have cleaned my drive.

 

I have given up on rebuilding catalogs at the moment which is a same. It used to work. I am currently on 5.1 but I am not sure when I started having the problem... it could have been in 5.0238

 

-Suzanne

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...