bennyblade
asked on
The Microsoft Exchange Replication Service VSS writer (instance 1aa7f733-4b22-405b-a9ab-4204ab3c94a4) failed with error code FFFFFFFC when processing the backup completion event.
The Microsoft Exchange Replication Service VSS writer (instance 1aa7f733-4b22-405b-a9ab-42
The VSSWriter on Exchange 2007 seems to be failing. We have Backup Exec 11d installed and for some reason there seems to be two listed instances of VSSWriter
The VSSWriter on Exchange 2007 seems to be failing. We have Backup Exec 11d installed and for some reason there seems to be two listed instances of VSSWriter
ASKER
Yes, this is one of the first things I tried.
Did you stop "MSExchRepl"?
ASKER
did I stop it before I applied the pacth you mean? no i didnt. would this have made any difference?
I meant, did you try stopping the MSExchRepl service before starting the backup. Does that make the backup complete successfully?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Oh, by the way: Stopping the MSExchRepl service sure gets the backup going with no issues, but it's not really a solution.
It looks like the whole issue arises from the fact that Exchange keeps the catalog files locked (on the passive copy only) in order to provide real-time replication...
It looks like the whole issue arises from the fact that Exchange keeps the catalog files locked (on the passive copy only) in order to provide real-time replication...
I am also experiencing this issue, it only happens every few weeks. Its starts with the cannot access the object list which usually means the disk is full where the back up to disk img's are. As by design BUE 11d does not delete these, 12 does so you have to manually delete them through BUE 11d.
This error happens every 3 weeks or so for me, resolution is a server restart which imo is not an answer!! You can restart the information store to get it working again if the write is in a retryable error state. If its failed the only option is a restart.
Something needs to be done about this. Anyone got a solution?
Catherine
This error happens every 3 weeks or so for me, resolution is a server restart which imo is not an answer!! You can restart the information store to get it working again if the write is in a retryable error state. If its failed the only option is a restart.
Something needs to be done about this. Anyone got a solution?
Catherine
Happening to me too. Clearly a bug in Exchange. it happens with any backup tool I've seen people use (including the builtin Windows Server Backup for 2008).
You may have to stop "MSExchangeRepl to make this work.