Jump to content

Error with Retrospect after Patching

Recommended Posts

I recently patched my copy of Retrospect 4.0 to fix the "Calendar/clock out of sync" error. Version is now listed as 4.0i. After running the patch I now get an error whenver a backup is run. The error is "Catalog out of sync with StorageSet "Backup ©. Use Tools>Repair>Update Existing". I tried running this repair, It said it was successfull, but the next time the backup runs I get the same error. I have three backup sets, hence the "C" in the storageset name, and this problem happened with both sets A and C. With backup set B I get the error "Can't add that much data to StorageSet. Limited to 1000.0 G total". This error happens randomly with different drives in the backup but I know none of them have near 1000 G of info.




Any possible fixes for this problem? I don't want to have to recreate the storageset considering I have 34 AIT tapes for all three sets. It would most likely take days to recreate one storageset.







Link to comment
Share on other sites

The patch that you are referring to only changed the expiration date of the product. There were no changes to device drivers or to the resolution of Backup Sets (Storage Sets).




Because this is happening on three different sets, it sounds like you are experiencing a coincidental hardware failure. You should go through standard SCSI troubleshooting to help isolate where the problem is coming from. Your catalogs are becoming corrupted when accessed by your device.




Another device on your SCSI bus is interfering with the tape drive's communication. Make sure your SCSI ID numbers are set correctly. Turn off your computer and the devices. Disconnect all SCSI devices except for the tape drive.




You have a bad cable. Replace the SCSI cable that connects the tape drive to the computer after removing other devices and cables from the SCSI chain.




You are missing a terminator (SCSI) or have a bad terminator. The last device and ONLY the last device in your SCSI chain needs to be terminated. Try replacing the terminator if you already have one on the chain.




Update the driver software for your SCSI card(s) at their manufacturers' websites.




The computer may be having a problem. Install Retrospect on another computer and try the tape drive there as the lone device on the SCSI chain.




The drive may be defective. If you have implemented all of the preceding steps and get failures on multiple tapes after changing cables terminators and computers then the drive (being the only factor that has not changed) is the culprit--send it back to your vendor for repairs.




The steps above are essentially the outline of our device troubleshooting here at Dantz. Hands on testing of device issues is really still the best method and even getting device logging information is usually only to confirm empirical testing. Note that concluding something is a bad device is the LAST thing we assume after all other components and variables have been ruled out. "SCSI voodoo" as they call the nebulous symptoms that can plague a SCSI bus can often lead one to false assumptions of the cause of problems. It's important that once a variable is tested that it be tested more than once for consistency's sake to rule out dumb luck. For example SCSI voodoo accounts for why a tape drive may work fine for many months without proper termination but then suddenly fail in some way later. Although customers will often cite that nothing has changed with their SCSI bus configuration in months and that it was all working before this is really indicative of the inconsistency of SCSI voodoo. The quickest and most conclusive test for most devices is to test it on more than one computer as the only device on the bus and with a different SCSI cable. If the problems can be reproduced on multiple computers it's more than likely a hardware problem with the device itself. Of course there a myriad of other specific issues having to do with a device's own hardware settings like with internal jumper cables dip switches or internal termination that has to be sorted out with the device's manual and/or vendor or manufacturer of the drive, but the kernel of SCSI troubleshooting above is a good general guideline.











Link to comment
Share on other sites


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

  • Create New...