Page 1 of 1

log truncation backups

Posted: Jun 13, 2018 10:44 pm
by gdavid16
exchange and sql don't like log truncation happening at the same time on multiple VMs in the same cluster.
really dont want to create a separate job for each exchange server or sql server.
is there a way to create a job with all exchange servers and tell it to process 1 VM at a time?

Re: log truncation backups

Posted: Jun 14, 2018 2:34 pm
by Dima P.
Hello George.

Are you talking about Exchange DAG? The only valid approach is to use job chaining and to process DAG nodes in separate backup jobs. Take a look at How to: Back up Exchange Database Availability Groups (DAGs) with Veeam Backup & Replication blog post for more details.

Re: log truncation backups

Posted: Jun 14, 2018 4:55 pm
by vdellachiesa
Veeam Support - Case # 03051477
upgraded to U3
rebooted servers to clear writer retry able error
still getting warning

Dima,

we have an exchange 2016 dag with 8 members. 4 of the members in site A hold activate databases and 4 of the members in site B hold the passive databases. Most jobs warn with the below error message, it isn't always the same server.

Code: Select all

VSS: Backup job failed. Cannot notify writers about the 'BACKUP FINISH' event. A VSS critical writer has failed. Writer name: [Microsoft Exchange Writer]. Class ID: [{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}]. Instance ID: [{d9ab8eb1-1e46-4db1-b84f-e70093814a80}]. Writer's state: [VSS_WS_FAILED_AT_BACKUP_COMPLETE]. Error code: [0x800423f3].

Re: log truncation backups

Posted: Jun 15, 2018 4:35 pm
by Dima P.
vdellachiesa,

Is that a chained backup jobs setup (like explained in the blog post) or you keep all DAG nodes in one backup job? Thanks.

Re: log truncation backups

Posted: Aug 15, 2018 11:56 am
by zimmy6996
Hey all ... I am in a Exchange 2013 environment, with 2 servers in a DAG. And I am havin the exact same issue as this. 50% of the time, I get this same error on one of the two servers. It generally leans towards one of the two, but again, it happens much of the time.

Logs are clearing, as can be seen when logging in to the file system.

Code: Select all

8/15/2018 3:37:41 AM :: VSS: Backup job failed.
Cannot notify writers about the 'BACKUP FINISH' event.
A VSS critical writer has failed. Writer name: [Microsoft Exchange Writer]. Class ID: [{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}]. Instance ID: [{fa03eef9-7e54-4ca4-9418-b0016a6457a1}]. Writer's state: [VSS_WS_FAILED_AT_BACKUP_COMPLETE]. Error code: [0x800423f3]. 

Re: log truncation backups

Posted: Aug 16, 2018 12:07 pm
by zimmy6996
Failed again last night, same error ...

Re: log truncation backups

Posted: Aug 16, 2018 1:49 pm
by foggy
Hi Chris, please review this post for some hints. Thanks.