U15503 Posted March 16, 2003 Report Share Posted March 16, 2003 I am including an extract from the Retrospect Backup log which indicates that, after a successful incremental backup, errors -102 and -205 were generated during the compare process. Following this error situation, I ran a backup set verify, which completed without any errors. For your information Retrospect is running on a Dell Inspiron 5000, Adaptec FireWire PC bus card and an extrernal Sony I.link CD-RW drive. The operating system is Windows 2000 Professional, service pack 3. I have serveral questions. First, is this a valid backup or not? Does the fact that the backup set verify compelted successfully indicate the backup data is valid? Secondly, since this error -102 and -205 seems to occur with some regularity, is there anyway to reinitiate a backup set compare after the failure occurs since one does not know if the remaining date to be compared was in fact written correctly? Thirdly, if there isn't any way in Retrospect to reinitiate the backup compare after this type of failure, is there anyway of convincing Retropsect that the session just created is invalid so that the incremental backup can be redone? The problem here is that it appears that the Retropsect catalogue considers the incremental backup to have been successful even though the compare process did not complete successfully. I would think there should be some way of invalidating that session in the catalogue or on the CD-RW's so one could redo it. + Retrospect version 6.0.206 Launched at 3/15/2003 4:32 PM + Retrospect Driver Update, version 3.6.104 + Executing Immediate Backup at 3/15/2003 4:32 PM To Backup Set Backup Set A... - 3/15/2003 4:32:27 PM: Copying Drive E (E:) 3/15/2003 4:46:22 PM: Snapshot stored, 247 KB 3/15/2003 4:46:24 PM: Comparing Drive E (E:) Trouble reading: "Backup Set A" (281), error -102 (trouble communicating) Trouble reading: "Backup Set A" (0), error -205 (lost access to storage medium) 3/15/2003 4:50:12 PM: Execution incomplete Remaining: 16 files, 85.9 MB Completed: 70 files, 250.6 MB, with 17% compression Performance: 40.2 MB/minute (27.0 copy, 117.4 compare) Duration: 00:17:45 (00:03:10 idle/loading/preparing) Quit at 3/15/2003 5:01 PM + Retrospect version 6.0.206 Launched at 3/15/2003 5:03 PM + Retrospect Driver Update, version 3.6.104 Quit at 3/15/2003 5:07 PM + Retrospect version 6.0.206 Launched at 3/15/2003 5:11 PM + Retrospect Driver Update, version 3.6.104 + Executing Verify at 3/15/2003 5:12 PM To Backup Set Backup Set A... 3/15/2003 6:25:27 PM: Execution completed successfully Completed: 1737 files, 7.3 GB Performance: 124.4 MB/minute Duration: 01:13:18 (00:13:20 idle/loading/preparing) Link to comment Share on other sites More sharing options...
AmyJ Posted March 18, 2003 Report Share Posted March 18, 2003 While in Retrospect, go to Configure > Devices > Environment and list Vendor, Product and Version for your drive. Link to comment Share on other sites More sharing options...
U15503 Posted March 26, 2003 Author Report Share Posted March 26, 2003 Sorry to take so long in providing this information. It is: Vendor: SONY Product: CD-RW CRX160E Version: 1.0e Driver: SONY CR-RW (1.54) Link to comment Share on other sites More sharing options...
AmyJ Posted March 26, 2003 Report Share Posted March 26, 2003 Try *temporarily* uninstalling any other CD-writing utilities, in case extraneous drivers are conflicting with Retrospect. Also uninstall any drivers Windows may have loaded. Was ASPI installed correctly? Run ASPICHK (in the Retrospect Program Files folder) to make sure ASPI is "green." If not, try a reinstall (ASPIINST.exe). If you still have problems, consult the Retrospect User's Guide or Adaptec's website. Is this Windows NT or 2000? If so, enable NT SCSI Passthrough to bypass ASPI: From the Retrospect Directory hit Ctrl-Alt-P-P. Under "Execution," check "Enable NT SCSI Passthrough." Click OK. Quit and relaunch. If you still don't have any luck, I'd recommend the following hardware troubleshooting steps. Try a different disc in your drive. If you're trying discs of the same brand, try at least one of a different brand. Try straightening out the internal ribbon cabling. Try switching master and slave settings. Try new internal cabling. Try updating the firmware on the device if possible (see the drive manufacturer's website). Are the drivers for the IDE controller current? Try updating them with an approved update from your PC vendor. Finally, try bringing this drive to another PC and trying the backup. If it works here, you could be having a problem with either the ATAPI bus on the original machine or with the PC itself. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.