VSS Writers status doesnt reset after a backup.
Created: 20 Jun 2007 • Updated: 09 Nov 2011 | 3 comments
This issue has been solved. See solution.
We are having problems with our Exchange Server backup. The following VSS Writers display State  Waiting for completion after each backup:
Writer name: 'System Writer'
Writer name: 'Microsoft Exchange Writer'
Writer name: 'IIS Metabase Writer'
Writer name: 'FRS Writer'
Writer name: 'NTDS'
Writer name: 'WMI Writer'
All other Writers are State  Stable.
The full backup of that server is successful.
If i run another backup, the 'Microsoft Exchange Writer' state change to Retryable Error and the backup fails.
I've read lots of forums and tried every possible fix/workaround and we still have the same problem. To be able to backup the server, we have to reboot it each day. If i try to backup the server without resetting the VSS Writers state, the Exchange Server freeze and the backup fails. We can't receive/send emails anymore until the next reboot.
We are using:
- Windows Server 2003 Standard Service Pack 2
- Microsoft Exchange 2003 Service Pack 2
- BackupExec 11D with the latest patch
To backup the Exchange Server, we use a policy that backup the following to tape:
- Dell Utility Partition
- First Storage Group
- Shadow Copy Components
- System State
For the Exchange Agent, we have to following options checked:
- Enable the restore of individual mail messages...
- Perform consistency check...
- Continue with backup if consistency check fails
- Enable single instance backup for message attachments
Some thing i noticed during the backup is in the Event Log of the Exchange Server. Every 10sec or so, i have to following events "ESEUTIL (5032) The database engine stopped.", instantly followed by "ESEUTIL (1024) The database engine 6.05.7638.0002 started."
There is no errors in the Application and System event logs.
We only have this problem since we upgraded to Backup 11D, everything was OK with version 10. The installation of Backup 11D is a fresh install and i recreated the backup jobs. The jobs imported from the database backup of BE10 was a standalone job and now we created a policy instead. I've tried to recreate the same standalone job but the VSS Writers keeps hanging in Waiting for Completion state.
BackupExec is backing up 4 other servers without any problems.
Message Edited by Claude Bilodeau on 06-20-200708:20 AM