upgrade to v9 and Exchange 2013 DAG backup warning

Availability for the Always-On Enterprise

Re: upgrade to v9 and Exchange 2013 DAG backup warning

Veeam Logoby Markus.K1985 » Thu Apr 07, 2016 8:25 am

We have the same issue at the moment and also opened a Case.

Any result so far?
Markus.K1985
Service Provider
 
Posts: 46
Liked: 12 times
Joined: Mon Dec 08, 2014 2:30 pm
Full Name: Markus Kraus

Re: upgrade to v9 and Exchange 2013 DAG backup warning

Veeam Logoby pshute » Thu Aug 18, 2016 12:58 am

We have had this problem for weeks now. Is there a definitive fix we can do?
pshute
Expert
 
Posts: 118
Liked: 8 times
Joined: Mon Nov 23, 2015 10:56 pm
Full Name: Peter Shute

Re: upgrade to v9 and Exchange 2013 DAG backup warning

Veeam Logoby foggy » Thu Aug 18, 2016 11:34 am

I've checked the last case mentioned above and it was closed due to no response from the customer. Please contact support directly, they will be able to verify your issue and advise in case there's a solution available.
foggy
Veeam Software
 
Posts: 15272
Liked: 1131 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: upgrade to v9 and Exchange 2013 DAG backup warning

Veeam Logoby pshute » Thu Aug 18, 2016 11:56 pm 1 person likes this post

Thanks, we got a good backup without the error last night, so I'm hoping we've fixed it permanently. I ran "vssadmin list writers" on the mail server after posting that, as suggested above, and could see Microsoft Exchange Writer reporting a failed state. We removed a couple of databases we had previously dismounted because of errors, and then restarted services as suggested above (veeam-backup-replication-f2/upgrade-to-v9-and-exchange-2013-dag-backup-warning-t32764-15.html#p181174), and then Microsoft Exchange Writer was no longer reporting a failed state. Then the evening backup was ok.

I'm not sure which of those actions fixed it. It might be that I forgot to restart the services after dismounting the databases, and that removing the databases wasn't necessary.
pshute
Expert
 
Posts: 118
Liked: 8 times
Joined: Mon Nov 23, 2015 10:56 pm
Full Name: Peter Shute

Re: upgrade to v9 and Exchange 2013 DAG backup warning

Veeam Logoby jwz88 » Tue Aug 30, 2016 1:16 pm

Hi,

We also have this issue since the start of v9.
I have tried everything, also opened a support case which has been closed a long time ago as I gave up.

But its really bothering me a lot, especially since other people are having the same problem.

Exchange 2013 CU11 DAG, but the issue also persisted at CU7.
Sometimes the backup runs OK without warning, but that's like 5% of the time. The rest it gives this warning:

30-8-2016 01:52:31 :: 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: [{8f4c280e-5be6-455d-be15-176709528c84}]. Writer's state: [VSS_WS_FAILED_AT_BACKUP_COMPLETE]. Error code: [0x800423f3].

Its on the same patch levels as our other DAG members, which do not display any errors.
All members are running Active and Passive databases.
I have reseeded all the passive databases already, but also no success.

At this point I have no clue what to do anymore...
When running a manual shadow copy all seems fine....
jwz88
Influencer
 
Posts: 12
Liked: never
Joined: Fri Sep 05, 2014 6:24 am

Re: upgrade to v9 and Exchange 2013 DAG backup warning

Veeam Logoby Andreas Neufert » Tue Aug 30, 2016 10:22 pm

Thanks for the feedback. I updated myblog post with tips and tricks.
http://andyandthevms.com/exchange-dag-v ... plication/

At jwz88 can you please check the tips in this thread and on my blog post.
At least did you increased Failover CLuster heartbeat to max values and mount or delete unmounted databases?
Andreas Neufert
Veeam Software
 
Posts: 2288
Liked: 382 times
Joined: Wed May 04, 2011 8:36 am
Location: Germany
Full Name: @AndyandtheVMs Veeam PM

Re: upgrade to v9 and Exchange 2013 DAG backup warning

Veeam Logoby jwz88 » Wed Aug 31, 2016 8:35 am

Hi Andreas,

Yes, I have changed the heartbeat to the recommended settings in the Veeam KB article.
We don't have a failover occurring at backup time, we never had but changed this setting anyway when I contacted support a while ago.

We do have some dismounted databases, but those are passive databases from other servers. The other servers are running the exact same config but experience no issues.

At backup time, the CPU load at backup time is approx. 7 %, about the same as the other exchange servers.
Backup is being run on NBD mode, latencies about 2 ms.

The exchange logs are being truncated though. I even enabled circular logging for a weekend to disable it afterwards, this did not change anything either.

The weird thing is, sometimes the backup does go OK (very, very rarely) without any changes.
If anyone has any pointers that'd be great...
jwz88
Influencer
 
Posts: 12
Liked: never
Joined: Fri Sep 05, 2014 6:24 am

Re: upgrade to v9 and Exchange 2013 DAG backup warning

Veeam Logoby rogerdu » Tue Nov 29, 2016 6:51 pm

I get this error now as well... Exchange Replication jobs failing, but here's the twist... NetApp integration is failing and I cannot create a storage snapshot. case 01989645 opened with Support as it is showing as a VSS error (with the same error code 800423f3) because it gets a VSS timeout when using the "regular" snapshot mechanism... GRRR all was working for a whole 2 days!!
rogerdu
Expert
 
Posts: 111
Liked: 7 times
Joined: Tue Aug 20, 2013 1:16 pm
Full Name: Roger Dufour

Re: upgrade to v9 and Exchange 2013 DAG backup warning

Veeam Logoby rogerdu » Tue Nov 29, 2016 8:34 pm

Ignore the troll in the corner... it seems my client was running a backup at the same time I was... while his VSS session was in use, I could not create a new one... once his job finished, everything I had put in place fell back to the blissful green state we all like to see. Case closed...
rogerdu
Expert
 
Posts: 111
Liked: 7 times
Joined: Tue Aug 20, 2013 1:16 pm
Full Name: Roger Dufour

Re: upgrade to v9 and Exchange 2013 DAG backup warning

Veeam Logoby Andreas Neufert » Tue Nov 29, 2016 8:39 pm

Good to hear and thanks for the update. Be careful with the log truncation. If the customer uses the other software on a regular base and this software uses Logfile processing you can place our job to "Copy only".

... and hey, we learned a new root cause for this error message.
Andreas Neufert
Veeam Software
 
Posts: 2288
Liked: 382 times
Joined: Wed May 04, 2011 8:36 am
Location: Germany
Full Name: @AndyandtheVMs Veeam PM

Re: upgrade to v9 and Exchange 2013 DAG backup warning

Veeam Logoby rogerdu » Tue Nov 29, 2016 8:40 pm

for the replication jobs, I am already using the copy only functionality. The daily backups does the truncate logs function.
rogerdu
Expert
 
Posts: 111
Liked: 7 times
Joined: Tue Aug 20, 2013 1:16 pm
Full Name: Roger Dufour

Previous

Return to Veeam Backup & Replication



Who is online

Users browsing this forum: antipolis, Google Feedfetcher, jslic, Yahoo [Bot] and 5 guests