Symptoms
VSS: The writer failed due to an error that might not occur if another snapshot is created (Microsoft Exchange Writer)(Specific GetWriterStatus)(Snapshot continued)
1. The error is reported while running a backup for a VSS-Aware backup set protecting Exchange2007 or Exchange2010. If on the backup target computer the command: vssadmin list writers is run in a command prompt window, Microsoft Exchange Writer may be in a "failed" state.
2. The error is reported during a vss restore for a VSS-Aware backup set protecting Exchange.
Cause
1. The "Circular logging" option is enabled on backup target Exchange.
2. The "rename component" option is used along with the "alternate restore", still the target restore server is the original server that was backed up.
Workaround
1. Disable the option "Circular logging" for all mailbox databases intended to be backed up as it causes the truncation log failure for VSS based Exchange backups; the mailbox databases may need to be dismounted and re-mounted in order to thave the change effective. A restart or Microsoft Exchange Information Store service is required in order to revert the state of Microsoft Exchange Writer from "failed" to "stable" ( for a successful VSS backup this writer should be in a stable state).
2. During a "vss" restore the DS-Client/Exchange writer verifies if the names provided in the "rename component" pane actually exist, if they are not in place the error is reported and the restore aborted. Also during such restore ( "vss" ) the database GUID is verified, when restoring to the same server that was backed up in order to prevent overwriting the original database ( if that is not intended ) perform a "file restore" to a different folder or to a Recovery Database ( for example when in need to merge some inadvertently deleted mailbox content to the original mailbox database ).