Multiple SQL Servers backed up using Veeam

Availability for the Always-On Enterprise

Multiple SQL Servers backed up using Veeam

Veeam Logoby antman157 » Tue Dec 06, 2016 1:48 pm

Hello,

We currently have 3 SQL servers in production. What is the best practice to back these 3 servers up? By using individual jobs or as a group? Right now I have them grouped and they will kick the first job off tonight. My concern is if I have to restore one of the servers I will have to wait for all 3 jobs to import, correct? I've turned VSS on and they will do a transform on Saturday night's. Using reverse incremental each night. Currently I have these VMs in random jobs and I am trying to group them by function. My only fear is the time it would take to restore 1 of them if it was needed.

How do you handle multiple SQL servers?

Data:
Size of VMs
1) 1.2TB
2) 750 GB
3) 47GB (Mirror)

OS version
2008R2 / SQL 2008
2012R2 / SQL 2012
antman157
Influencer
 
Posts: 12
Liked: 1 time
Joined: Wed Apr 03, 2013 2:53 pm
Full Name: Anthony Jones

Re: Multiple SQL Servers backed up using Veeam

Veeam Logoby foggy » Tue Dec 06, 2016 2:03 pm

antman157 wrote:My only fear is the time it would take to restore 1 of them if it was needed.

Time required for restore doesn't depend much on the number of VMs in the job.
foggy
Veeam Software
 
Posts: 15272
Liked: 1131 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Multiple SQL Servers backed up using Veeam

Veeam Logoby antman157 » Tue Dec 06, 2016 2:14 pm

It would just take longer for Veeam to read the tape and information correct? Because I would just be restoring the 1 VM
antman157
Influencer
 
Posts: 12
Liked: 1 time
Joined: Wed Apr 03, 2013 2:53 pm
Full Name: Anthony Jones

Re: Multiple SQL Servers backed up using Veeam

Veeam Logoby foggy » Tue Dec 06, 2016 2:19 pm

Ok, you didn't mention tape in your original post. ;) However, even in this case, you can use direct restore to infrastructure, which eliminates the effect of large backup files.
foggy
Veeam Software
 
Posts: 15272
Liked: 1131 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Multiple SQL Servers backed up using Veeam

Veeam Logoby Gostev » Tue Dec 06, 2016 2:20 pm

If you mean restoring directly from tape, then Veeam will only read the required information (data blocks belonging to the restored VM).
Gostev
Veeam Software
 
Posts: 21603
Liked: 2405 times
Joined: Sun Jan 01, 2006 1:01 am
Location: Baar, Switzerland

Re: Multiple SQL Servers backed up using Veeam

Veeam Logoby antman157 » Tue Dec 06, 2016 2:43 pm

Oops, I apologize. Our setup copies the backup to tape -- Tape is sent offsite -- Then at DR, tape is imported to the repository in DR then the restore is brought into VMware.
antman157
Influencer
 
Posts: 12
Liked: 1 time
Joined: Wed Apr 03, 2013 2:53 pm
Full Name: Anthony Jones

Re: Multiple SQL Servers backed up using Veeam

Veeam Logoby skrause » Tue Dec 06, 2016 2:47 pm

If you use reverse incremental it will keep your snapshots open longer while it does the nightly transforms of the full backup file so you will have a higher likelihood of snapshot removal stuns causing connections to the DB to be interrupted temporarily. That would be a bigger concern for me than the amount of time to do a restore from tape, especially considering the size of the VMs.
Steve Krause
Veeam Certified Architect
skrause
Expert
 
Posts: 308
Liked: 45 times
Joined: Mon Dec 08, 2014 2:58 pm
Full Name: Steve Krause

Re: Multiple SQL Servers backed up using Veeam

Veeam Logoby antman157 » Tue Dec 06, 2016 2:49 pm

How do you do your SQL incremental backups? Just curious if there's a better way and a reverse.
antman157
Influencer
 
Posts: 12
Liked: 1 time
Joined: Wed Apr 03, 2013 2:53 pm
Full Name: Anthony Jones

Re: Multiple SQL Servers backed up using Veeam

Veeam Logoby skrause » Tue Dec 06, 2016 3:04 pm

For stand alone SQL boxes, I just do a standard forward incremental job. If you are concerned about disk space on the repository you can always do Forever incremental or transform previous chains to rollbacks. Either way, you can set up your tape job in such a way as to create a synthesized VBK for your "oh shit" moment when you have to restore from offline media. I do copy only on application aware for all of our SQL servers because we have a DBAs who do individual database backups/restores.

My "production" setup is considerably more intricate than most people's setups. We use a 3-headed always-on availability group for our production SQL boxes (2 synchronous with automatic failover in primary datacenter and 1 asynchronous in failover DC 150 miles away connected via a 10GB link). The two synchronous replicas are backed up in separate jobs which are chained to avoid both getting a snapshot stun at the same time which would make the core applications that use databases on those servers inaccessible for more than the momentary blip that happens when the AlwaysOn fails over.
Steve Krause
Veeam Certified Architect
skrause
Expert
 
Posts: 308
Liked: 45 times
Joined: Mon Dec 08, 2014 2:58 pm
Full Name: Steve Krause


Return to Veeam Backup & Replication



Who is online

Users browsing this forum: Google Feedfetcher and 7 guests