curioffl Posted February 6, 2014 Report Share Posted February 6, 2014 Retrospect 8, Exchange 2007. Since migrating to Retrospect 8, when I make a backup of "Exchange Mailboxes", I get this error on the same 5 (of 40 or so) mailboxes (an they appear not to back up very much of their content): - 2/4/2014 11:39:40 PM: Copying Ron E James on Rainbow Trouble reading files, error -1010 ( API request bad) 2/4/2014 11:45:26 PM: Execution incomplete Remaining: 21677 files, 697.4 MB Completed: 98 files, 3,394 KB Performance: 16.5 MB/minute Duration: 00:05:45 (00:05:33 idle/loading/preparing) I had no such problem on Retrospect 7.6 (or, at least it did not email me nightly to alert me of it). What do I do? Ron E. James D.O. 1 Quote Link to comment Share on other sites More sharing options...
Mayoff Posted February 7, 2014 Report Share Posted February 7, 2014 If it happens with specific mailboxes only, then the mailbox may contain data Retrospect has trouble reading. You can try to back up subvolumes from the mailbox to see if it fails when you copy a specific folder. Quote Link to comment Share on other sites More sharing options...
darkod Posted June 25, 2014 Report Share Posted June 25, 2014 I have the same thing hapenning on 5 out of 109 mailboxes on Exch2007. If I'm not mistaken, originally it started when version 7.7 crashed during a backup of these mailboxes. Not sure if it left some flag or corruption of some kind, but ever since it reported these mailboxes as -557 transaction already complete. Even though it says there is data remaining to copy, it never even starts copying and leaves these mailboxes unrptoected. Moving to the latest version 9 the message has changed to 1010 API request bad, but only on the same mailboxes. I have tried numerous things, including removing the client, deleting all Retrospect Client folders, rebooting the Exch server and reinstalling the client. No luck. There were not many suggestions to try either. I love this program but this part of the Exchange agent is making me very nervous. It seems during a crash/stop of a backup it can "mark" a mailbox and makes it impossible to back it up again. It always reports it as already done which is not true. I would love some solution if it exists. If not, it seems the only thing left to try is disconnecting the mailbox from the user, exporting it to a PST, making a new mailbox for that user and import the data back. But that's also a risky operation and these mailboxes are important. Also it will be lengthy operation on big mailboxes (the export/import will take 4-5 hours each). Anyone has any solution for these -1010 errors, earlier -557? Quote Link to comment Share on other sites More sharing options...
tonypresnow Posted May 21, 2015 Report Share Posted May 21, 2015 I'm having the same problem with one of my mailboxes too. Anyone figure out this issue? I'm running exchange 2010 sp3 and retrospect 10. The problem started after upgrading to exchange 2010, and retrospect 10. 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.