Availability for the Always-On Enterprise
Post Reply
gdavid16
Influencer
Posts: 22
Liked: never
Joined: Aug 27, 2015 2:05 pm
Full Name: George D.
Contact:

log truncation backups

Post by gdavid16 » Jun 13, 2018 10:44 pm

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?

Dima P.
Veeam Software
Posts: 8756
Liked: 647 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:

Re: log truncation backups

Post by Dima P. » Jun 14, 2018 2:34 pm

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.

vdellachiesa
Novice
Posts: 8
Liked: 2 times
Joined: Jun 11, 2014 11:39 pm
Contact:

Re: log truncation backups

Post by vdellachiesa » Jun 14, 2018 4:55 pm

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].

Dima P.
Veeam Software
Posts: 8756
Liked: 647 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:

Re: log truncation backups

Post by Dima P. » Jun 15, 2018 4:35 pm

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.

zimmy6996
Lurker
Posts: 2
Liked: never
Joined: Aug 15, 2018 11:53 am
Full Name: Chris Zimmerman
Contact:

Re: log truncation backups

Post by zimmy6996 » Aug 15, 2018 11:56 am

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]. 

zimmy6996
Lurker
Posts: 2
Liked: never
Joined: Aug 15, 2018 11:53 am
Full Name: Chris Zimmerman
Contact:

Re: log truncation backups

Post by zimmy6996 » Aug 16, 2018 12:07 pm

Failed again last night, same error ...

foggy
Veeam Software
Posts: 16932
Liked: 1377 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: log truncation backups

Post by foggy » Aug 16, 2018 1:49 pm

Hi Chris, please review this post for some hints. Thanks.

Post Reply

Who is online

Users browsing this forum: Google [Bot], yowmemperor and 60 guests