This is a nasty error, and an even nastier "fix". I had this error on one of my DPM servers, and no matter what I tried to do on the DPM side, it kept coming back with this error. I tried Consistency checks, Full Backups, Incremental, and none of them worked. I did go as far as stopping protection for the Storage Group that was failing, recreated the replica, and that seemed to work, but after it happened several times, this is not something I wanted to do regularly.
Apparently, this is a known issue with Exchange 2007, and there is little that can be done until a patch is released for this problem (not fixed as of Exchange 2007, SP1, Update Rollup 3).
KB217320 describes the issue, and offers this "resolution"
Run VSS backup again on the storage group on which backup was stopped. If the successive VSS backups fail with a backup-in-progress error, stop and restart the following services from the Services snap-in. This will clear the backup-in-progress state for the storage groups that are affected by this failure:
- Microsoft® Exchange Information Store service.
- Microsoft Exchange Replication Service.
If you are using cluster continuous replication (CCR), stop the backup process that is running, restart the passive node of the cluster, and then try the backup again.
In my case, I am protecting a CCR cluster, which, according to Microsoft, requires me to restart the node that I am protecting every time I get this VSS error! I did let the error go once, just to see if it would fix itself, and after 3 days, it did. **NOTE: I had PLENTY of space on the Exchange server for Logs, or I would not have attempted this.**
So, happy restarting... until MS can give us a patch!
Posts
6 comments:
Thanks Heaps. We use TSM copy Services and we were getting this same Retryable Errors after 3 weeks of successful VSS replica Backups. We have switched back to performing Legacy Backups using TSM TDP on the active server.
Glad I could help! I am still working with Microsoft on this issue, so once I get a resolution, I'll post it... grab the RSS feed, so you won't miss it! :)
Did Update Rollup 4 fix the issue with DPM? We are using TSM copy Services with TDP Exchange and are also working with Microsoft on this. As far as I can tell the issue was not fixed with Update Rollup 4 (at least not for TSM backup).
I'm experiencing the same error but with just one Virtual Machine. The other virtual machines on that host are backing up fine.
A reboot of the host seems to get everything back in sync but that is not a viable solution. I have tried just about every sequence of service restarts possible. Talk about frustrating.
Thanks,
John
For what its worth, we are also on Exchange 2007 CCR (rollup 3). On DPM I have the feature release and the 949779 release/featurepack/whatever. Every express full backup of our storage groups completes with no issues. Every recovery point sync fails with the retryable VSS error.If I recreate the recoverypoint it tells me its inconsistent. If I then run the consistency check, its reporting that all is well. This still sucks, but beats rebooting the passive node for each backup. Not sure if its the 949... fix that is making this slightly less painful or if there is something different in our environment.
I am also getting this error repeatedly on just one VM on one host. This VM has SQL 2005 installed.
Post a Comment