cbj4074 Posted August 27, 2012 Report Share Posted August 27, 2012 Hello, As of late, my logs have filled-up with the following error message (44,900+ instances for one backup job): Trouble writing: "1-Backup Set 1" (2355679232), error -106 ( data overwrite attempt) Trouble writing media: "1-Backup Set 1" error -106 ( data overwrite attempt) Additional error information for Disk Backup Set member "1-Backup Set 1", Can't write to file M:\Backup Sets\Retrospect\Backup Set 1\1-Backup Set 1\AA001709.rdb, error -1023 ( already exists) The script progress (on the Activity Monitor's "Executing" tab) states that it is on the "Closing..." step. The "Completed" time is at 19:18:03, even though the task has been running for three days. Clicking the "Stop" button has no effect; the button becomes greyed-out, but Retrospect never moves past the "Closing..." step. I can't quit the application, either. I try, and Retrospect warns me that one execution is running, and when I try to quit anyway, Retrospect hangs indefinitely with "Exiting....." in the status area at bottom-left of the interface. (All UI components are disabled.) Killing the Retrospect UI process does kill Retrospect without affecing the the OS or other applications. Any thoughts as to what might be happening here? Thanks for any help! Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted August 27, 2012 Report Share Posted August 27, 2012 I quote rhwalker. Please provide: (1) complete version number of Retrospect (2) complete version number of Retrospect Driver Update (3) complete version number of the OS (4) complete description of hardware being used. (5) complete description of the steps you are doing (6) complete description of the problem I think you have covered part 6 quite well, but not the others. Quote Link to comment Share on other sites More sharing options...
cbj4074 Posted August 28, 2012 Author Report Share Posted August 28, 2012 Sorry, Lennart. (1) 7.7.620 x64 (2) I didn't see Driver Updates for 7.7, so none, I suppose. (3) Windows 7 SP1 x64 (7601.17835.amd64fre.win7sp1_gdr.120503-2030) (4) Seagate Barracuda 3TB (ST3000DM001) drive, connected via wall-powered Sans Digital external 4-bay enclosure in USB 3.0 mode to proper USB 3.0 port on back of desktop tower. (I can provide more details on this hardware if necessary.) (5) Configured four LAN backup clients to be backed-up to single Backup Set (started empty) that is stored on the above hard disk. Nothing else is stored on this disk, and Avast A/V solution has been cofigured to ignore the disk during realtime monitoring and scheduled scans. I created a new backup task by going to Automate -> Manage Scripts -> New. Chose "Backup" task, gave it a name. Chose four LAN client boot volumes as sources (these are all Macs with Mac OS Extended Journaled filesystems [HFS+, I believe]). Also added server's boot volume to sources. Set schedule to run once per day. Scheduled backups ran for a week or so. Despite the other issues I've encounted ( http://forums.retros...thers-are-fine/ and http://forums.retros...eboot-required/ ), the full contents of each client was eventually backed-up. Then, all of a sudden, these error messages began appearing in my logs. The only thing I noticed that seems worthy of mention is that disk defragmentation had not been disabled when this began to occur. After noticing that Windows' built-in disk defragmentation was running on a schedule, I disabled it, but the same errors persist. I tried to rebuild the existing catalog file, which took a mere 52 seconds (seems quick for a 1TB backup set), and the job was reported successful. Yet, the errors persisted during backup. I tried to rebuild the catalog from scratch, overwriting the existing catalog, but that failed with: + Executing Rebuild at 8/27/2012 2:35 PM (Execution unit 1) To Backup Set Backup Set 1... Generated MD5 digest for file "C:\Recycle.Bin\S-1-5-21-67599994-2904207001-1248085395-1000\R1ETLLF.gz" does not match stored MD5 digest. Trouble reading: "1-Backup Set 1" (80613676), error -102 ( trouble communicating) Trouble reading: "1-Backup Set 1" (80613679), error -102 ( trouble communicating) Trouble positioning: "1-Backup Set 1" (80613679), error -102 ( trouble communicating) Trouble reading: "1-Backup Set 1" (80613680), error -102 ( trouble communicating) Trouble reading: "1-Backup Set 1" (80613681), error -102 ( trouble communicating) TPCVol::GetInfo: UGetVolumeInformation failed, M:\, osErr 55, error -1102 Additional error information for Disk Backup Set member "1-Backup Set 1", Can't read to file M:\Backup Sets\Retrospect\Backup Set 1\1-Backup Set 1\AA000528.rdb, error -1102 ( drive missing/unavailable) Trouble reading: "1-Backup Set 1" (80613682), error -116 ( volume doesn't exist) 8/27/2012 3:25:33 PM: Execution incomplete Completed: 2505085 files, 312.8 GB Performance: 6477.9 MB/minute Duration: 00:50:13 (00:00:46 idle/loading/preparing) I found this to be quite strange, and not a particularly good sign. This hard disk is brand new. I ran Windows' built-in disk error-checking tool, with both boxes checked, and it reported that no problems were found (this was in GUI mode, so not much detail provided). So, I attempted the same a second time, and this time, the errors were: + Executing Rebuild at 8/27/2012 11:01 PM (Execution unit 1) To Backup Set Backup Set 1... Generated MD5 digest for file "C:\Recycle.Bin\S-1-5-21-67599994-2904207001-1248085395-1000\R1ETLLF.gz" does not match stored MD5 digest. The Disk Backup Set data file "AA000931.rdb" reported missing by user The Disk Backup Set data file "AA001093.rdb" reported missing by user 8/28/2012 2:01:08 AM: 3 execution errors Completed: 4148959 files, 958.6 GB Performance: 5599.1 MB/minute Duration: 02:57:54 (00:02:36 idle/loading/preparing) I'm not sure what the missing backup set data file messages are about. I didn't tell Retrospect that either of those archives was missing. Anyway, I attempted to run the backup script again, and the behavior persists (-1023 and -106 errors for seemingly every file that is backed-up). I elected to Verify the Backup Set one more time, and this time, the errors are different: + Executing Verify at 8/28/2012 10:27 AM (Execution unit 1) To Backup Set Backup Set 1... Generated MD5 digest for file "C:\Recycle.Bin\S-1-5-21-67599994-2904207001-1248085395-1000\R1ETLLF.gz" does not match stored MD5 digest. Backup Set format inconsistency (5 at 669372253) 1 files were not verified 8/28/2012 1:21:05 PM: 3 execution errors Remaining: 15143 files, zero KB Completed: 4133816 files, 959.4 GB Performance: 5862.1 MB/minute Duration: 02:50:39 (00:03:03 idle/loading/preparing) Finally, I re-ran the backup script and the -1023 and -106 errors persist. Please let me know if I can provide additional detail in any regard. Thanks! Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted October 23, 2012 Report Share Posted October 23, 2012 Seems to me like a USB problem. Try another USB cable. 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.