Cbarnhorst Posted July 14, 2003 Report Share Posted July 14, 2003 I recently had a problem with a filename that was "invalid", probably by being too long. I overcame the scanning error in Backup through the Secret Handshake function of turning off the error trapping. However, the same did not work for Restore and I could not restore the backup set due to the scanning error. The file was created by Executive Software's Undelete and when the Volume Shadowcopy Service added its pathname the total folder name probably exceeded 255 characters and became invalid. Is there a solution? I finally had to abandon the backup set (I still have it saved) and rebuild the hard drive. Needless to say, I did not include Undelete. Link to comment Share on other sites More sharing options...
Mayoff Posted July 14, 2003 Report Share Posted July 14, 2003 Quote: . I overcame the scanning error in Backup through the Secret Handshake function of turning off the error trapping. Is this something you did in Retrospect? I am a little confused, what have you changed? Link to comment Share on other sites More sharing options...
Cbarnhorst Posted July 14, 2003 Author Report Share Posted July 14, 2003 I did the Ctrl+Alt+P P to bring up the special preferences screen and turned off a function that causes Retrospect to stop on severe errors. That works for backing up but it turns out that it has no impact on the scan for restoring. The effect is that you can still back up in spite of the scanning error (folder name invalid), but you still can't restore (so what good is it?). I have since replaced the hard drive (upgrade to ATA133) and left the faulty backup file in a directory of one of my external drives. I don't use it and the function I changed is now restored to its default. My point was that Volume Shadowcopy Services adds enough to a path name that a problem can happen with Retrospect. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.