vtrasikis Posted March 23, 2010 Report Share Posted March 23, 2010 For some reason Retrospect has started giving: + Executing Immediate Backup at 3/23/2010 11:50 AM To Backup Set asus-note... - 3/23/2010 11:50:54 AM: Copying DRIVE_C (C:) Scanning incomplete, error -1103 (write protected) There has been NO hardware changes. I have run numberous chkdsks with no errors and even ran defrag a few times and still get this error. What is write protected????? My other partitions (D and E) run with no trouble. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted March 23, 2010 Report Share Posted March 23, 2010 Windows is reporting something about the C: disk can not be scanned. What Retrospect version? What OS Version? Quote Link to comment Share on other sites More sharing options...
vtrasikis Posted March 23, 2010 Author Report Share Posted March 23, 2010 version 7.6. win-xp pro. Now how do you find out what that can be that it can not scan??? Quote Link to comment Share on other sites More sharing options...
Mayoff Posted March 23, 2010 Report Share Posted March 23, 2010 Any errors in the Windows event log during the failure? Quote Link to comment Share on other sites More sharing options...
vtrasikis Posted March 23, 2010 Author Report Share Posted March 23, 2010 The only failure is that Retrospect was incomplete... Quote Link to comment Share on other sites More sharing options...
vtrasikis Posted March 26, 2010 Author Report Share Posted March 26, 2010 any idea what could be causing this??? Quote Link to comment Share on other sites More sharing options...
Mayoff Posted March 26, 2010 Report Share Posted March 26, 2010 If you can scan all other disks, then it could be a corrupt file on the disk. Maybe scan specific subfolders to narrow down the bad item. Quote Link to comment Share on other sites More sharing options...
vtrasikis Posted March 26, 2010 Author Report Share Posted March 26, 2010 So you are saying to keep running retrospect for each individual folder on the C drive?? talk about a very long process. I have run chkdsk and there are NO errors... Isn't there an easier way to find out what is causing the error???? Quote Link to comment Share on other sites More sharing options...
Mayoff Posted March 26, 2010 Report Share Posted March 26, 2010 You would scan the folders at the root of the C: disk to try and narrow things down. Something is hiding on the hard disk and causing a critical failure. Quote Link to comment Share on other sites More sharing options...
vtrasikis Posted March 26, 2010 Author Report Share Posted March 26, 2010 So you are suggesting that I should create a script to just try and backup a particular folder and see if it works and keep trying till it fails... starting just at the root folders.. Quote Link to comment Share on other sites More sharing options...
rhwalker Posted March 26, 2010 Report Share Posted March 26, 2010 No, define Retrospect "subvolumes" (see the user manual index) and do a binary search on the volume - start at the root level, figure out what part of the filesystem tree has the problem by backing up subvolumes at that level, go down a level, repeat. Russ Quote Link to comment Share on other sites More sharing options...
L1Travis Posted March 27, 2010 Report Share Posted March 27, 2010 (edited) I have the same problem. My OS is VISTA and I am using Retrospect v7.7. The problem is intermittent and occurs in random subvolumes so it cannot be caused by an error in a file being backed up. Later post - I recatalogued and the backup ran without error the first try. We'll see if it continues to work. Edited March 27, 2010 by Guest Quote Link to comment Share on other sites More sharing options...
vtrasikis Posted March 31, 2010 Author Report Share Posted March 31, 2010 I did that. Funny thing is that I ran a regular backup and it worked! Why is that??? I have had a few more instances of it and when I run one with the subvolumes and then then regular back will run normally. What is going on with Retrospect???? Quote Link to comment Share on other sites More sharing options...
vtrasikis Posted May 27, 2010 Author Report Share Posted May 27, 2010 Does anyone one have any answers for this???? Isn't there a way to run a trace so as to find out what file is causing this problem????????? Quote Link to comment Share on other sites More sharing options...
vtrasikis Posted June 27, 2010 Author Report Share Posted June 27, 2010 Is there any way that you can set Retrospect to state what file(s) is causing this problem???? Quote Link to comment Share on other sites More sharing options...
vtrasikis Posted August 5, 2010 Author Report Share Posted August 5, 2010 Guess there is no one that can answer this question..... Quote Link to comment Share on other sites More sharing options...
vtrasikis Posted August 24, 2010 Author Report Share Posted August 24, 2010 I have been waiting and waiting for any sort of help as to what is causing the 1103 errors. I have NOT been able to back up my drive in a long time because of it. How can anyone recommend this product if no one seems to be able to explain what is causing the error and how to fix it???? :angry2: :angry2: :angry2: Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.