gasser Posted July 27, 2009 Report Share Posted July 27, 2009 Twice I rebuilt my catalog and both times I got this error: Normal backup using Daily Backup at 7/15/2009 6:33 AM To Media Set Daily B... 7/15/2009 6:33:18 AM: Copying DAS 250 Additional error information for Disk Media Set member "1-Daily B", Can't write to file /Volumes/Backups/Retrospect/Daily B/1-Daily B/AA001201.rdb, error -1023 ( already exists) SMTP: opening addr 38.113.1.153 > !Trouble writing: "1-Daily B" (2499960832), error -106 ( data overwrite attempt) 7/15/2009 6:57:41 AM: Verifying DAS 250 !Trouble writing media: "1-Daily B" error -106 ( data overwrite attempt) SMTP: opening addr 38.113.1.153 The file AA001201.rdb is the most recently-created file my backup set, 148 MB (all others are 600 MB). I tried setting the logging level to 6, but all it shows is this, ad infinitum: Normal backup using Daily Backup at 7/27/2009 5:24 PM To Media Set Daily B... 7/27/2009 5:24:40 PM: Copying DAS 250 devSwapHeaderCheck(1): will swap, curver 0x303, M -694, Y 0 runRequestNewItem:thd 0xb1899000: will show media request SMTP: opening addr 38.113.1.153 devSwapHeaderCheck(1): will swap, curver 0x303, M -694, Y 0 devSwapHeaderCheck(1): will swap, curver 0x303, M -694, Y 0 devSwapHeaderCheck(1): will swap, curver 0x303, M -694, Y 0 devSwapHeaderCheck(1): will swap, curver 0x303, M -694, Y 0 devSwapHeaderCheck(1): will swap, curver 0x303, M -694, Y 0 Quote Link to comment Share on other sites More sharing options...
Mayoff Posted July 28, 2009 Report Share Posted July 28, 2009 That file could be corrupt or sitting on a bad disk sector. If you are sure this is the problem file, try to move it out of the folder and do another catalog rebuild. I would also run a disk check. Quote Link to comment Share on other sites More sharing options...
gasser Posted July 31, 2009 Author Report Share Posted July 31, 2009 (edited) Finally, after 2 months of agony, deleting the corrupt file on the end of my backup set and rebuilding solved the problem. It would be instructive perhaps to summarize the potpourri of problems that conspired to make this such an ordeal, in case you can see to improve the program's behavior when these problems occur, particularly in the error messages. 1. Retrospect bug where it wanted additional media even though the disk was not full, because it was remembering the space on the disk when the media set was created, rather than the current space. Not fixed simply by rebuilding catalog. Had to delete media set, erase data, and start over. 2. MacOS's mounting a network disk, sometimes with a -1 suffix, sometimes not, depending on what I had done in the Finder before Retrospect ran. Retrospect may not be able to find the member. 3. Some kind of access control problem with Iomega NAS drive, turning on security when Retrospect required it to be off (even though the security that was set should have allowed access anyway). 4. Corrupted file on the end of a backup set, not detected at catalog rebuild time but causing backup to fail with "data overwrite attempt message". 5. All four of above giving me the "Needs media" message rather than a message explaining what the problem actually was. Edited July 31, 2009 by Guest 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.