blawson Posted May 2, 2003 Report Share Posted May 2, 2003 We've been using Retrospect 6.0.206 on our Windows 2000 server to back up a number of Mac OS X and Win2K servers for some time now, but for the past few weeks we've been unable to properly complete a backup. The backup 'locks' during the "closing" phase of one of the later clients in the backup script. Not always the same client, btw. Retrospect still responds to menu choices and such, but the only way to perform another backup is to click "Stop" and then use Task Manager to kill retrospect.exe. This seems to result in a completed backup (as far as the retrospect Client application is concerned) that doesn't have an updated catalog. The catalogs are about 400 MB in size, in case this is relevant. Anyone know how to correct this? I'm thinking of forgetting and deleting the next catalog file and building a new one from scratch in case it is a corruption problem. Thanks, Ben Link to comment Share on other sites More sharing options...
blawson Posted May 12, 2003 Author Report Share Posted May 12, 2003 Well. I "forgot" and deleted the catalog file and created a new one. Still the same problem. Link to comment Share on other sites More sharing options...
AmyJ Posted May 13, 2003 Report Share Posted May 13, 2003 What are you backing up to? While in Retrospect, go to Configure > Devices > Environment and list Vendor, Product and Version for your backup drive. Link to comment Share on other sites More sharing options...
blawson Posted May 13, 2003 Author Report Share Posted May 13, 2003 We're backing up to a SCSI AIT2 tape library. 2:3 SONY SDX-500C version 010B Sony AIT DC (1.38) 2:6 SPECTRA 215 version 1010 Spectra Logic Library (1.06) Link to comment Share on other sites More sharing options...
AmyJ Posted May 16, 2003 Report Share Posted May 16, 2003 In many cases, these types of problems are related to device communication issues. As a test, if possible, try backing up the same sources to a disk backup set (which would be saved to a hard drive) to see if the problem goes away. If so, the following troubleshooting list will help you isolate the problem with the backup hardware. If the problem occurs while writing to a disk backup set, or only when backing up clients, there could be a problem with the backup computer or the networking hardware. Once the problem has been further isolated, troubleshooting will be a little easier. SCSI Troubleshooting: 1) A dirty tape drive or bad tape. Clean the drive using a cleaning cartridge. Try another tape. If other tapes work then you just have a tape with a spot that's bad enough to stop your backup. 2) 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. 3) 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. 4) You are missing a terminator 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. 5) 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. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.