jriggin Posted February 25, 2008 Report Share Posted February 25, 2008 Exchange server - Windows 2003 - Retrospect Client version 7.5.116 Retrospect is running on Windows 2003, version 7.5.387, hotfix version 7.5.13.100 We've never had an issue backing up the Exchange server before. This weekend there was a network communication error, followed by the exchange backup failing. When I try to back it up manually today I receive the following error: Trouble reading files, error -3681 (Backup is already active I've restarted the Retrospect server on the client, and restarted the Retrospect application itself, with no luck. Short of rebooting both servers, what can I do to resolve this and why is it happening? Link to comment Share on other sites More sharing options...
Mayoff Posted February 25, 2008 Report Share Posted February 25, 2008 This error is being reported by Exchange. Your exchange server thinks the backup is still running. I would suggest restarting the exchange server. Link to comment Share on other sites More sharing options...
fgs Posted June 9, 2008 Report Share Posted June 9, 2008 jriggin, did this solve your problem? I am experiencing the same error messages. Link to comment Share on other sites More sharing options...
fgs Posted June 10, 2008 Report Share Posted June 10, 2008 I was able to reboot my Exchange server last night after receiving this error lately and now my backups are running normal again. Link to comment Share on other sites More sharing options...
fgs Posted June 24, 2008 Report Share Posted June 24, 2008 I've received this error a couple more times since the last time I posted about it. Restarting the Exchange server works, but I get it again a few days later. It seems to be happening after my Storage Group backup runs out of space and can't groom anything out, so I have to stop the script. It really gets annoying for a bunch of people (including myself) when I have to restart the email server one night a week. I've tried just restarting the Retrospect Client service on Exchange, but that didn't allow it to work. I've also tried closing Retrospect and re-opening it (even though it appears to be a client side error)... still no go. FYI... my Storage Group is 81GB. I have the backup set size set to 550GB. Groom to remove backups older than 3. With this setup I would think that it would never be able to reach the 550GB with 3 backups @ 81GB a piece. Any help would be greatly appreciated. Thanks. Link to comment Share on other sites More sharing options...
Mayoff Posted June 24, 2008 Report Share Posted June 24, 2008 Are you using compression for your backups. That should increase the amount of data copied to the backup itself. Link to comment Share on other sites More sharing options...
fgs Posted June 24, 2008 Report Share Posted June 24, 2008 No. We do brick layer and Storage Group backups of Exchange and neither one uses data compression. How would compression increase the size of the data copied to the backup? Link to comment Share on other sites More sharing options...
Mayoff Posted June 25, 2008 Report Share Posted June 25, 2008 Exchange data may compress up to 80 or 90%, saving a lot of disk space. Try turning on compression within Retrospect assuming you are writing to a disk device. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.