Comprehensive data protection for all workloads
sebastian.mair
Novice
Posts: 8
Liked: never
Joined: Apr 11, 2013 12:24 pm
Contact:

Backup SQL Always ON 2016 Basic Availiblity Group

Post by sebastian.mair » Feb 10, 2017 8:10 am

hello, i have a 2 SQL Server 2016 Standard with Basic Availiblity Group. i have Databases on both hosts, but have only 2 which are on high availiblity state. so i want to backup both nodes, but the backup on the secondary replica fails, because this is a limitation of BAG. but in fact i have normal databases on the secondary node, so my question is, is it possible to exclude the database from backup on the second node? i can only exclude the complete database from veeam over the registry tweak, but i want to backup the HA Database which is active on the primary node.


any ideas?

kind regards,

sebastian

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

Re: Backup SQL Always ON 2016 Basic Availiblity Group

Post by foggy » Feb 10, 2017 10:54 am

Hi Sebastian, indeed, Basic Availability Group doesn't allow backup of databases from secondary node (there's no read access on secondary replica). We already have a requirement to detect and exclude such databases from VSS processing and will address this in one of the future updates. Thanks.

leigh.brewster
Lurker
Posts: 2
Liked: never
Joined: Nov 28, 2016 1:37 am
Full Name: Leigh Brewster
Contact:

[MERGED] SQL 2016 Backup Failes

Post by leigh.brewster » May 16, 2017 1:20 am

Hi, I have a SQL2016 AlwaysOn setup with a primary and a secondary replica running on Server 2012R2

When trying to backup the secondary replica SQL server I get the following error:

Code: Select all

16/05/2017 11:05:17 AM :: Unable to release guest. Error: Failed to call RPC function 'Vss.Unfreeze': Error code: 0x80004005. Failed to invoke func [Unfreeze]: Unspecified error. Unfreeze error: [Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}]. Instance ID: [{83df507e-cc79-44fb-979c-0ac04025ad51}]. Writer's state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x800423f4].].  
Unable to release guest. Error: Failed to call RPC function 'Vss.Unfreeze': Error code: 0x80004005. Failed to invoke func [Unfreeze]: Unspecified error. Unfreeze error: [Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}]. Instance ID: [{83df507e-cc79-44fb-979c-0ac04025ad51}]. Writer's state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x800423f4].].
Error: Failed to prepare VM for processing: Failed to call RPC function 'Vss.Unfreeze': Error code: 0x80004005. Failed to invoke func [Unfreeze]: Unspecified error. Unfreeze error: [Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}]. Instance ID: [{83df507e-cc79-44fb-979c-0ac04025ad51}]. Writer's state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x8
Any help would be great

Thanks

Leigh

Dima P.
Product Manager
Posts: 10633
Liked: 874 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:

Re: SQL 2016 Backup Failes

Post by Dima P. » May 16, 2017 4:37 am

Hi Leigh,

Please reach our support team and let them investigate the application logs. Additionally, here is the thread with a similar error, take a look at suggested workaround. Thank you.

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

Re: SQL 2016 Backup Failes

Post by foggy » May 16, 2017 10:39 am

Any chance this is a Standard Edition of SQL Server 2016?

leigh.brewster
Lurker
Posts: 2
Liked: never
Joined: Nov 28, 2016 1:37 am
Full Name: Leigh Brewster
Contact:

Re: SQL 2016 Backup Failes

Post by leigh.brewster » May 16, 2017 10:46 pm

Yes STD SQL2016 why?

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

Re: SQL 2016 Backup Failes

Post by foggy » May 17, 2017 4:53 pm

Then it is a known MS limitation, please see above.

nmdange
Expert
Posts: 475
Liked: 116 times
Joined: Aug 20, 2015 9:30 pm
Contact:

Re: Backup SQL Always ON 2016 Basic Availiblity Group

Post by nmdange » May 22, 2017 3:15 pm

According to the original post Veeam should have an update at some point to detect these databases and exclude them to stop the error from happening. Is there any ETA on when this fix might be made available? This is still an issue on 9.5 update 2.

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

Re: Backup SQL Always ON 2016 Basic Availiblity Group

Post by foggy » May 22, 2017 3:16 pm

This is planned for v10.

james-w
Lurker
Posts: 1
Liked: never
Joined: Sep 06, 2017 6:18 am
Contact:

Re: Backup SQL Always ON 2016 Basic Availiblity Group

Post by james-w » Sep 06, 2017 6:19 am

Hi,

Is this still planned for v10?

Thanks.

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

Re: Backup SQL Always ON 2016 Basic Availiblity Group

Post by foggy » Sep 06, 2017 1:37 pm

Yes.

nmdange
Expert
Posts: 475
Liked: 116 times
Joined: Aug 20, 2015 9:30 pm
Contact:

Re: Backup SQL Always ON 2016 Basic Availiblity Group

Post by nmdange » Feb 27, 2018 7:06 pm

Any ETA on when this might be fixed? I've noticed that the backup job our SQ 2016 Std AlwaysOn members are in is not merging/removing old restore points because the backup job always fails.

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

Re: Backup SQL Always ON 2016 Basic Availiblity Group

Post by foggy » Mar 01, 2018 12:10 pm

It is planned for the next Veeam B&R update, but I cannot provide any ETA at the moment.

sdv
Lurker
Posts: 2
Liked: never
Joined: Jan 09, 2018 8:12 am
Full Name: Stefan de Vries
Contact:

Re: Backup SQL Always ON 2016 Basic Availiblity Group

Post by sdv » May 24, 2018 12:37 pm

Just a ping to keep this in track.
Hoping for release of 9.5v4 instead of v10.

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

Re: Backup SQL Always ON 2016 Basic Availiblity Group

Post by foggy » Jul 30, 2018 4:47 pm

Hi Stefan, yes, high chances it will be included in U4.

nixoidas
Service Provider
Posts: 15
Liked: never
Joined: May 24, 2017 12:29 pm
Full Name: Mantas
Contact:

[MERGED] AlwaysOn SQL backup

Post by nixoidas » Sep 03, 2018 6:53 am

Hi,

We have 2 nodes SQL cluster. SQL licence Standard. There is one AlwaysOn db. When veeam backups these 2 nodes, backup fails on that VM which is not active. Error is something like sqlwriter is at failed state. If we exclud AlwaysOn db from the second node, backups is success. Is there a way for veeam to check on which node the AlwaysOn db is during backup and not to try to backup this db on other node that does not have this db during backup time? Otherwise, veeam is not very smart with Standard SQL edition and there is no way to backup AlwaysOn on Standard... I am aware of the SQL limitations for Standard but there are commands which Veeam could run to check where the alwayson db resides and backup this db only on the the active node and not on both of them.

nixoidas
Service Provider
Posts: 15
Liked: never
Joined: May 24, 2017 12:29 pm
Full Name: Mantas
Contact:

Re: AlwaysOn SQL backup

Post by nixoidas » Sep 03, 2018 1:00 pm

Any IDEAS?

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

Re: AlwaysOn SQL backup

Post by foggy » Sep 03, 2018 1:32 pm

Veeam B&R does actually check the node state and use this information during logs processing. The error you see is not Veeam B&R but rather SQL specific, please see above for details. Thanks.

nmdange
Expert
Posts: 475
Liked: 116 times
Joined: Aug 20, 2015 9:30 pm
Contact:

Re: AlwaysOn SQL backup

Post by nmdange » Sep 03, 2018 1:50 pm

This is a known issue with Veeam and Basic Availability Groups that is supposed to be fixed in Update 4

https://forums.veeam.com/post241299.html

sdv
Lurker
Posts: 2
Liked: never
Joined: Jan 09, 2018 8:12 am
Full Name: Stefan de Vries
Contact:

Re: Backup SQL Always ON 2016 Basic Availiblity Group

Post by sdv » Dec 05, 2018 10:14 am

foggy wrote:
Jul 30, 2018 4:47 pm
Hi Stefan, yes, high chances it will be included in U4.
Hi Foggy, thanks for replying with an ETA.

Can we still expect this to be included in U4 ?

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

Re: Backup SQL Always ON 2016 Basic Availiblity Group

Post by foggy » Dec 05, 2018 2:55 pm

Yes, it is there.

mkaaden
Influencer
Posts: 21
Liked: 1 time
Joined: Dec 11, 2017 12:35 pm
Contact:

Re: Backup SQL Always ON 2016 Basic Availiblity Group

Post by mkaaden » Jan 28, 2019 11:50 am

Hi,

I've implemented Update4 in a new installation.
I still get truncation error's on secondairy databases
Is there a setting to filter out secondairy databases in Basic Availability Groups ?

Regards

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

Re: Backup SQL Always ON 2016 Basic Availiblity Group

Post by foggy » Jan 28, 2019 6:23 pm

Well, truncation is a different scenario and we were able to reproduce this internally. Though secondary database is correctly detected and excluded from backup (while the entire job failed in previous version), further logs truncation does indeed produce a warning. Will be fixed in future, thanks for the heads up!

mkaaden
Influencer
Posts: 21
Liked: 1 time
Joined: Dec 11, 2017 12:35 pm
Contact:

Re: Backup SQL Always ON 2016 Basic Availiblity Group

Post by mkaaden » Jan 28, 2019 9:08 pm

In this case one database sneaked over to the second node.
But you are assuming that these always run active-standby ?
What if they are running active-active ?
Then there should be some other mechanism to determine the primairy node of the database and include that with the backup.
I'll guess you do the same with Exchange DAG ?

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

Re: Backup SQL Always ON 2016 Basic Availiblity Group

Post by foggy » Jan 29, 2019 11:43 am

We're talking about Basic AG, where the secondary replica is always inactive, since there's no read access on it.

nmdange
Expert
Posts: 475
Liked: 116 times
Joined: Aug 20, 2015 9:30 pm
Contact:

Re: Backup SQL Always ON 2016 Basic Availiblity Group

Post by nmdange » Jan 29, 2019 2:51 pm

If you have multiple databases each in their own Basic AG, the active node may be different per database, so if the exclusion is at the server level and not the database level, it won't work properly.

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

Re: Backup SQL Always ON 2016 Basic Availiblity Group

Post by foggy » Jan 29, 2019 8:18 pm

Exclusions are database level, so will work correctly in the described use case.

mkaaden
Influencer
Posts: 21
Liked: 1 time
Joined: Dec 11, 2017 12:35 pm
Contact:

Re: Backup SQL Always ON 2016 Basic Availiblity Group

Post by mkaaden » Feb 06, 2019 10:39 am

Will there be a hotfix for the Log truncation issue on the Secondary node ?

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

Re: Backup SQL Always ON 2016 Basic Availiblity Group

Post by foggy » Feb 06, 2019 3:25 pm

Hotfix no, it will be included in one of the future releases.

nmdange
Expert
Posts: 475
Liked: 116 times
Joined: Aug 20, 2015 9:30 pm
Contact:

Re: Backup SQL Always ON 2016 Basic Availiblity Group

Post by nmdange » Feb 06, 2019 4:41 pm

I'm a bit disappointed it took 2 years from when this issue was first posted for Veeam to get some kind of fix in, and it's still not complete. Seems like that should have been enough time for Veeam to fully test this functionality and see that there are still errors with log truncation.

Post Reply

Who is online

Users browsing this forum: vishalgupta and 30 guests