Hello,
It is not happened all the time. But sometime I notice that some of the databases in the DAG were successfully register in the backup log but its database transaction logs were not truncated. When I logged on the server, I can see this VSS error on Exchange writer: Status 12 (VSS_WS_FAILED_AT_BACKUP_COMPLETE). I try to recycle the exchange information store, but it cannot reset the status of the writer. The only way to resolve this issue is to restart the exchange server.
This happened randomly on different database as well as node in the DAG. It is a pain to restart the server every week. Full or incremental back up log does logged as successful backup and no error.
I am not sure where or what else to check. Any advice are greatly appreciated.
Thanks,
Bob
In addition, all database (active and passive) copies are mounted and all content index are healthy. and the Exchange CU is 5. Like I mention this happened randomly and after a restart of Exchange server the Exchange writer status code reset to 1 and the logs will be truncated successfully until the VSS Exchange writer change its status code to 12 again.