Availability for the Always-On Enterprise
Post Reply
mikegmi
Novice
Posts: 8
Liked: 1 time
Joined: Nov 05, 2012 8:01 pm
Full Name: Mike Bordignon
Contact:

Re: Backing up Always On MSSQL with Veeam

Post by mikegmi » Jul 11, 2014 4:38 am

Likewise, please let me know when you have released a whitepaper with guidelines, or have a way to backup SQL AlwaysOn databases natively. We too are experiencing issues.

Dave23
Novice
Posts: 5
Liked: never
Joined: Sep 20, 2013 3:38 pm
Full Name: Dave
Contact:

[MERGED] SQL 2012 Availability Groups

Post by Dave23 » Jul 23, 2014 7:14 pm

I know that Veeam doesn't support replicating SQL 2012 Availability groups, but has anyone found a way to make this work? I'm able to replicate both nodes in my cluster from my production to DR site (that are on two different networks), but when I failover and bring both replicas online, the Availability group is no synchronized and neither are the databases because the databases are not in a healthy state. I also have to go into the Failover Cluster Manager and modify the AG listener with a new IP address since the cluster is now on a different network. If anyone has any input on how to make this work that would be great.

Thanks,

Dave

lightsout
Expert
Posts: 208
Liked: 54 times
Joined: Apr 10, 2014 4:13 pm
Contact:

Re: Backing up Always On MSSQL with Veeam

Post by lightsout » Sep 11, 2014 9:06 pm

I applied SQL 2012 SP2 to my machines, and now it seems, I can backup the secondary node. Has anyone else seen this?

v.Eremin
Veeam Software
Posts: 15227
Liked: 1146 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: Backing up Always On MSSQL with Veeam

Post by v.Eremin » Sep 12, 2014 9:38 am

Can you elaborate on what replica the given VM hosts? Only active, only passive, or both active and passive? Thanks.

lightsout
Expert
Posts: 208
Liked: 54 times
Joined: Apr 10, 2014 4:13 pm
Contact:

Re: Backing up Always On MSSQL with Veeam

Post by lightsout » Sep 12, 2014 8:55 pm

Both active & passive nodes are VMs. I only backup one, as it only works if it is the active node.

The ultimate problem was a SQL VSS writer would error on a passive node, causing the failure. I would say that seems to be fixed with SQL 2012 SP2 on one of my clusters. I'm upgrading the other to see if it helps that one further.

v.Eremin
Veeam Software
Posts: 15227
Liked: 1146 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: Backing up Always On MSSQL with Veeam

Post by v.Eremin » Sep 15, 2014 7:54 am

I think we haven't had issues with backing up VMs that host only active node. Or you're saying that you experienced different behavior that have been changed by applying SP2? Thanks.

lightsout
Expert
Posts: 208
Liked: 54 times
Joined: Apr 10, 2014 4:13 pm
Contact:

Re: Backing up Always On MSSQL with Veeam

Post by lightsout » Sep 15, 2014 1:12 pm

Yes, that is what I'm saying. It seems to be the case I can backup passive hosts running SP2.

Not all of my SQL Servers are upgraded yet, so I'm in that process now, but so far it seems to have resolved it.

tsightler
Veeam Software
Posts: 5199
Liked: 2082 times
Joined: Jun 05, 2009 12:57 pm
Full Name: Tom Sightler
Contact:

Re: Backing up Always On MSSQL with Veeam

Post by tsightler » Sep 15, 2014 1:53 pm

I suspect the following change from the SQL2012 SP2 change notes is the reason:
Functionality:
SQL Writer support COPY_ONLY backup: Data Protection Manager (DPM) full backup on the server with AlwaysOn secondary will be converted to COPY_ONLY backup.
Obviously Veeam <> DPM, but we're using the VSS SQL Writer as well and it sounds like this would convert any call to perform a VSS freeze for the database on a passive node to a COPY_ONLY call (i.e. no log truncation), which should work fine for us as well.

vmstrata
Lurker
Posts: 1
Liked: never
Joined: Oct 28, 2014 5:08 pm
Full Name: Chad Giardina
Contact:

Re: Backing up Always On MSSQL with Veeam

Post by vmstrata » Oct 28, 2014 5:09 pm

Hey guys. Any updates on this issue?

lightsout
Expert
Posts: 208
Liked: 54 times
Joined: Apr 10, 2014 4:13 pm
Contact:

Re: Backing up Always On MSSQL with Veeam

Post by lightsout » Oct 28, 2014 8:14 pm

All of my AAG SQL 2012 servers are updated to SP2, and the issues seems to be resolved for me.

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

Re: Backing up Always On MSSQL with Veeam

Post by foggy » Oct 28, 2014 8:16 pm

We are adding full support for Availability Groups backup in Veeam B&R v8, stay tuned.

sjlarsen
Lurker
Posts: 2
Liked: never
Joined: Nov 21, 2014 8:44 am
Full Name: Simon Juul Larsen
Contact:

Re: Backing up Always On MSSQL with Veeam

Post by sjlarsen » Nov 21, 2014 8:46 am

foggy wrote:We are adding full support for Availability Groups backup in Veeam B&R v8, stay tuned.
Any updates on when?
Just updated to v8, and still have this problem:

Code: Select all

21-11-2014 07:05:41 :: Processing SQL04 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: [{e7de7332-63c5-401e-b235-19956f55865b}]. Writer's state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x800423f4].]

Gostev
Veeam Software
Posts: 23112
Liked: 2916 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Backing up Always On MSSQL with Veeam

Post by Gostev » Nov 23, 2014 12:43 am

v8 has added full support for SQL Always On (both at backup and restore). Please, open a support case.

igarcia1
Influencer
Posts: 12
Liked: 4 times
Joined: Feb 10, 2014 5:19 pm
Contact:

Re: Backing up Always On MSSQL with Veeam

Post by igarcia1 » Nov 24, 2014 9:26 pm

The new user guide doesn't really mention, but seems to infer that all the AG nodes need to be in the same job. We have four nodes in the cluster that spans two sites, two nodes at each sites, for which we use separate repositories and vCenter deployments. I started setting up two different jobs for each pair of nodes to backup to each site, but started wondering about the implementation.

This should be okay to do as long as the backup preference is to use the secondary node, correct? The end result would be duplicate backup data (for the databases that span both sites) and truncated logs across the board, no?

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

Re: Backing up Always On MSSQL with Veeam

Post by foggy » Nov 25, 2014 12:02 pm

AG nodes do not necessarily need to be backed up in a single job. What is much more important, is that transaction logs backup should be performed only in one job - if some of the nodes are backed up by a different job, this job should have the 'Do not truncate' setting selected for these VMs.

I agree that user guide should cover that better, will forward your request to the documentation team. Thanks!

Post Reply

Who is online

Users browsing this forum: daniel.triplehorn, Exabot [Bot], seb002 and 37 guests