Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About darkod

  • Rank
    Occasional Forum Poster
  1. 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?
  2. OK, so we are talking about the Exchange server machine, not the Retrospect machine. So you need to make sure .NET 4 is installed. Got it. I am not sure I will have the chance to test it, but it is good to know anyway.
  3. Isn't that installed when you click "Exchange 2007/2010 Support" in the main install menu of Retrospect 8? Or you need to install the support and after that .NET 4 manually?
  4. No way I will try to mess with 8.0 yet, not after yesterday. If we are talking only about file backup, I think it should work. The thing with client 8.0 was that it was not configuring Exchange as a Volume. But the partitions on the same Exchange server were reported as Volumes, browsable, etc. I didn't actually try to run a backup on them since I don't need them, but since they looked "normal" like any other working Volume, I guess it should work. I am only sort of testing the program after using it in 2004-2007 when it was Dantz if I remember correctly, so I don't have too many clients to test. And after the Exchange scare I downgraded both the client on that machine and the server to 7.7 and I'm not touching it now. In the next few days if I have time I might set up server 8.0 to a test machine, and try to backup another test machine with client 8.0 to see how it goes for file backup. And after I will try server 7.7 with client 8.0 like you say. If time allows me. But no more blind confidence in Retrospect, which is really sad since I loved it when it was Dantz.
  5. OK, I got this sorted out. It seems 8.0 has bugs with Exchange but to go back to 7.7 client you will have to completely remove the Retrospect Client, including deleting the folders C:\ProgramData\Retrospect Client and C:\Program Files (x86)\Retrospect, and then restart the Exchange server. After that install the 7.7 client as normal and the databases and mailboxes should be visible in Volumes.
  6. OK, I got this solved, sort of. If client 8.0 is giving you problems with Exchange and you want to go back to 7.7, here what you will have to do: 1. Open Services and stop the Retrospect Client (I did this manually just in case). 2. Open Add/Remove Programs (or Programs in Server 2008) in Control Panel and remove the Retrospect Client. 3. Delete the C:\ProgramData\Retrospect Client and C:\Program Files (x86)\Retrospect folders (Note: ProgramData is hidden, you will have to make hidden folders show). 4. Restart the Exchange Server (this is important, it didn't work without this step). 5. Install the 7.7 client. Your databases and mailboxes should now be visible.
  7. The thing is that I had Exch2007 working with 7.7, followed all steps, got MAPI, etc. But after installing the 8.0 and the 8.0 client on the Exchange machine, now even downgrading to 7.7 doesn't see neither the databases or mailboxes. The only thing I haven't tried so far is restarting the Exchange server in between downgrading the client because I didn't have the opportunity for a restart. So, Exch2007 is running client 7.7 right now, the backup server is running 7.7 and still nothing. All of this after trying 8.0. It worked fine before that.
  8. Thanks for the update. In your discussions with Retrospect you wouldn't know how it might affect Exchange 2007 and why I can't see anything now, would you? The problem is I'm just testing 8.0 before buying so I don't think I can get support. But without a clear solution I don't plan to spend company money on something that might not work as desired. Because as stated above, in my case even 7.7 doesn't see Exchange now, which got me really surprised.
  9. Don't be too fast with trying 8.0, I think it messed up my Exchange 2007. I also rushed to check it out. After I added the client (Exchange 2007 server on Win2003 R2 x64), in Volumes when clicking on Exchange Server it asked me the standard question about using the add-on license. After accepting, it never reads the databases (they never show) or the mailboxes. Further more, since then, this is the second day that I couldn't see the databases or mailboxes even from 7.7.620 any more. All that I have tried, failed. The mailserver is working fine, but no Retrospect version can see the databases or mailboxes any more.
  10. I have the following in the retroclient.log, if it means anything to anyone: ------- 1353409450: ConnStartListen: starting thread ConnStartListen for 1353409540: Connection established by 1353409560: connTcpConnection: invalid code found: 164 1353409560: connTcpConnection: invalid code found: 153 1353409560: ConnReadData: Connection with closed 1353409565: Connection established by 1353409571: ConnReadData: Connection with closed 1353409582: Connection established by 1353409584: ConnReadData: Connection with closed 1353409588: Connection established by 1353409863: ConnReadData: Connection with was reset 1353409899: PipeRead: ReadFile failed with error 109 ------- So far my search on google and in the Retrospect KB hasn't produced anything.
  11. I can not say 100% it is fault of Retrospect 8.0 but it does look like that to me 99%. After testing Retrospect 8.0 now the Exchange 2007 mailboxes and databases can not be seen as volumes by both Retrospect 8.0 and 7.7.620 any more. The 8.0 never did manage to add them correctly to Volumes (yes, I had the additional patch needed installed). But after that now even 7.7.620 can not add them to Volumes even though it worked fine before trying 8.0. Did it leave some files on the Exchange server that need to be removed? I tried with both 8.0 and 7.7 clients removing the C:\ProgramData\Retspect Client folder after deinstalling the client from Add/Remove Programs. If it matters, the Exchange is running on Server 2003 R2 x64. Now I can not even back up my server with any version of Retrospect or client. What the hell did it do??? I would really appreciate some advice.
  12. Something similar happened to me. I have Exchange 2007 SP3 which has been backed up by Retrospect 7.7.620 fow a few months now. I tried the new Retrospect 8 and in the Volumes section after clicking on the Exchange server client and confirming to use the Exchange Add-on license, no mailboxes show and no DB neither. Further more, after that I am unable to successfully register the Exchange as volume even if I try with Retrospect 7.7.620 (which worked fine so far). Did the intention to "register" it on Retrospect 8 mess up something on the server side so that even 7.7.620 doesn't read it now? If yes, that would be very, very dissapointing from a software that you consider to be your backup protection. Can someone please shed some light on these cases, because my server is sitting unprotected now, regardless of everything I have tried. Is there something hidden on it now?
  13. Here is what I tried with success but I do not consider it a real solution. Failing everything else, what worked is: 1. Create a new temporary mailbox and user. 2. Using the PowerShell of Exchange 2007 and the export-mailbox command, export all data from the mailbox giving the 557 error to the temp mailbox. 3. I tried a backup of the temp mailbox and worked straight away, no 557 error. The idea is later to disconnect the original mailbox from the original user (using the disable-mailbox command for example) and connect the temp mailbox to this original user (using the connect-mailbox command). That way the user will continue to work with the mailbox where the whole data was exported and which doesn't give the 557 error. It's not pretty, but it should work. Make sure you don't forget to assign the original email address to the new mailbox after disabling the original one. When you create the temp mailbox it will need to have some temp email address because the original email address will still be assigned to the original mailbox so you can't attach it to the temp mailbox too.
  14. I also have the -557 error on three mailboxes on Exchange 2007. Retrospect is 7.7.620 running on Windows Server 2008 R2 x64 and the windows client on the exchange server is 7.7.114. Reading other ports/threads, I have tried: 1. Removing the client on the exchange server using Add/Remove Programs, deleting all Retrospect folders left over, restart the exchange server, reinstall the client. After that I deleted the "old" client in Retrospect and added it again. Still the same error -557 on the same mailboxes. 2. Completely formatted the backup server installing 2008 R2 x64 again and Retrospect again. Stil lthe same. Unfortunately, and seeing other threads it seems to me that you can't get real help here. Maybe from someone who had the same situation and managed to resolve it. I haven't been able to solve this with any instructions I have found so far. As for Retrospect staff helping, I guess they are waiting for you to purchase additional support. I mean, why would you expect a software that costs 3,000-4,000 dollars or euros to work out of the box without paying more more money for support for something that should have just worked. I used it years ago when it was EMC and I have to say it worked perfectly and the support was great. Right now I don't think I would recommend to anyone spending the loads of cash.
  15. I am aware of that, and my suspicion is also that it fails once it starts to demand large bandwith. But of coure, that is so difficult to prove. And why i suspect the switch as a primary suspect. i think it simply doesn't pass the packets fast enough from one port to the other. On one server i am about to install the latest Broadcom Management software in the next few days, I guess that will install the latest drivers too. I will use the possibility to see if that changes anything. I will double check drivers. The other thing is that these are production servers and I can't simply take them offline to check cables etc, unless I really have something pointing that way. Not just fishing around.