AlexisLayton Posted April 15, 2003 Report Share Posted April 15, 2003 Apologies if this topic has come up before -- I tried searching for it. I run 4.3 Desktop on an older Mac stuck at MacOS 9.1. I have a QPS Que!Fire 12x10x32 CD-R/RW drive. I always verify when I backup. Sometimes when I run the backups, the writing phase seems to work just fine but during verification Retrospect experiences a slowdown followed by a drive error when verify files at the end of the CD-R. The verification and backup aborts at this point. Which brings me to my problem: Apparently Retrospect does not mark the as-yet-unverified files as "not backed up". When I run backup again, the files are assumed to be ok, when in fact at least one of them is not! This seems to me to be a serious problem in backup set reliability. If I cannot rely on the backup set at this point the whole thing is useless. Q1. Is there a way to force RDB to re-backup files as if the previous backup run never happened? Q2. Is there a way to continue verifing the files on the next CD-R after the one on which the error occurred? Q3. Is there a way to standalone verify on less than the entire backup set? (I.e. the last two CD-Rs, or after a certain date, etc.?) I really want RDB to consider un-verified files as NOT BACKED UP. Is 5.0 different in any way on this matter? Link to comment Share on other sites More sharing options...
Mayoff Posted April 15, 2003 Report Share Posted April 15, 2003 If you get an error during backup on a file, Rerospect should automatically attempt to backup that file again during the next backup. Quote: Q1. Is there a way to force RDB to re-backup files as if the previous backup run never happened? If you get an error during backup on a file, Rerospect should automatically attempt to backup that file again during the next backup. Data and Resource offset errors are examples You can go to Matching under options and turn off all matching. This will force 100% of the data to get backed up again. Quote: Q2. Is there a way to continue verifing the files on the next CD-R after the one on which the error occurred? If you get a fatal error that stops the backup, then you can not go back and do a byte by byte compare on the remaining files. You can use Tools>Repair to check to see if the files appear to be restorable. Quote: 3. Is there a way to standalone verify on less than the entire backup set? (I.e. the last two CD-Rs, or after a certain date, etc.?) Tools>verify but it does not campare the files to the original on the hard disk. Link to comment Share on other sites More sharing options...
AlexisLayton Posted April 16, 2003 Author Report Share Posted April 16, 2003 Quote: If you get an error during backup on a file, Rerospect should automatically attempt to backup that file again during the next backup. This is clearly not happening. The error is detected during verification while the window says there are hundreds of files and over a hundred megabytes left to compare. Yet the next backup, if I start it immediately, says only three files need to be backed up. This is why I am so concerned. Link to comment Share on other sites More sharing options...
Mayoff Posted April 16, 2003 Report Share Posted April 16, 2003 If that is the case, then either disable matching or perform a Recycle Backup to make sure all files are copied successfully without error. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.