dustmachine Posted March 4, 2002 Report Share Posted March 4, 2002 It would seem that when Retrospect Express encounters an error on my drive that the backup stops. What's the best way to continue and/or ignore the error? (Errors such as "can't read file -- volume corrupt?", and "file too large") While I appreciate Retrospect informing me of the error, I have now restarted a few times, with new backup sets, many times. I'm glad CDs are cheap. -brad Link to comment Share on other sites More sharing options...
Guest Posted March 25, 2002 Report Share Posted March 25, 2002 If you get an error in the backup, it's usually not necessary to restart the backup altogether. In most cases, Retrospect will log the error and continue on with the backup. If you're getting an error that your volume is corrupt, then you need to investigate why this is happening. A "file too large" error may be about a single file that is too large for Retrospect to back up, but in this case Retrospect should log the error and continue the backup. Instead of just restarting the backup again, look and and try to diagnose the errors that Retrospect is reporting. In most cases, these errors are a result of an outsode factor that needs to be addressed before a backup can be completed. Link to comment Share on other sites More sharing options...
ericstrauss Posted January 31, 2003 Report Share Posted January 31, 2003 Is there any way to Make Retrospect Desktop log the errors but not post them to the screen? Link to comment Share on other sites More sharing options...
AmyJ Posted January 31, 2003 Report Share Posted January 31, 2003 Not in an Immediate backup. If you use Automated Backups, you can have Retrospect quit after a scheduled execution. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.