Backup Copy Job - One giant one, or one for each Backup job?

Availability for the Always-On Enterprise

Backup Copy Job - One giant one, or one for each Backup job?

Veeam Logoby JoshuaPostSAMC » Thu Mar 09, 2017 7:44 pm

I have 14 backup jobs covering 500 VMs and 76 TB of backup data. I'm doing an initial copy to a separate storage device that will be heading to a DR location as soon as data is seeded.

What do most people do in regards to the copy job? Create one job that includes all backup jobs so there is only one task to manage? I plan to keep the same retention period on all copy jobs, but if I have to do an active full of a set of VMs, I don't necessarily want to do every VM I'm backing up. So I can see it both ways.

Right now I'm leaning towards one copy job for each backup job, but open to comments
JoshuaPostSAMC
Expert
 
Posts: 116
Liked: 16 times
Joined: Thu Jul 30, 2015 7:32 pm

Re: Backup Copy Job - One giant one, or one for each Backup

Veeam Logoby Gostev » Thu Mar 09, 2017 7:50 pm

Hello!

Multiple jobs give you more control, but also more things to manage. What do you like better?

From the product perspective, for 500 VMs you can certainly go with the single one (just make sure you have 9.5 U1 installed).
Gostev
Veeam Software
 
Posts: 21396
Liked: 2349 times
Joined: Sun Jan 01, 2006 1:01 am
Location: Baar, Switzerland

Re: Backup Copy Job - One giant one, or one for each Backup

Veeam Logoby DeadEyedJacks » Mon Mar 13, 2017 3:12 pm

Hi,
We found that when performing synthetic operations, transforms, etc, the backup storage needs as much free space as the largest backup or backup copy job.
So with a single jobs of 500 VMs and 76TB you might well need 76TB+ of free space on the backup repository.

We started off with aggregating backup jobs into fewer backup copy jobs but have since reverted to a one-to-one relationship between backup jobs and copy jobs.
(Environment is 600+ VMs and 1PB source data.)
Microsoft, NetApp, Symantec, Veeam, Veritas and VMware certified professional
MCTS, MCSE, NCDA, NCIE-BR, ASC, SCS, VMTSP, VTS, VCP
DeadEyedJacks
Veeam ProPartner
 
Posts: 85
Liked: 9 times
Joined: Mon Oct 12, 2015 2:55 pm
Location: UK
Full Name: DeadEyedJacks

Re: Backup Copy Job - One giant one, or one for each Backup

Veeam Logoby JoshuaPostSAMC » Mon Mar 13, 2017 4:04 pm

Thanks DeadEyeJacks.

I went ahead and set them up with a one-to-one so I could gradually turn them on and give the granular control Gostev mentioned.
JoshuaPostSAMC
Expert
 
Posts: 116
Liked: 16 times
Joined: Thu Jul 30, 2015 7:32 pm

Re: Backup Copy Job - One giant one, or one for each Backup

Veeam Logoby dellock6 » Fri Mar 17, 2017 4:40 pm

DeadEyedJacks wrote:Hi,
We found that when performing synthetic operations, transforms, etc, the backup storage needs as much free space as the largest backup or backup copy job.
So with a single jobs of 500 VMs and 76TB you might well need 76TB+ of free space on the backup repository.


That's true however only if you don't use per-vm backup chains. With per-vm enabled, the number of VMs in a job doesn't matter in regards to the size of a backup file, as each VM is still stored in its dedicated file.
Luca Dell'Oca
EMEA Cloud Architect @ Veeam Software

@dellock6
http://www.virtualtothecore.com
vExpert 2011-2012-2013-2014-2015-2016
Veeam VMCE #1
dellock6
Veeam Software
 
Posts: 5047
Liked: 1330 times
Joined: Sun Jul 26, 2009 3:39 pm
Location: Varese, Italy
Full Name: Luca Dell'Oca

[MERGED] Backup Copy Job for Multiple VMs

Veeam Logoby CoffeeCup » Fri May 12, 2017 3:58 pm

Hello,

We are running 70+ backup jobs every two hours form the VMWare Cluster. Each job includes two VMs (client based) so we are backing up this way more then 150 VMs. I’m currently adding Backup Copy job to implement GFS schema for each VM. What would be recommended way to setup Backup Copy job: use one job that aggregates all the VMs or split it in multiple (the backup/retention policy for each VM should be the same)? Would it be any difference from the performance/administration point of view? Running one job looks easier but would it be any drawback when, for example, adding new VMs to the job or restoring from the backup?

We are constantly adding more backup jobs and looks like our current backup schema is about too change so I’m looking for some kind of “Best Practice” recommendation of using Veeam in busy constantly growing environment.

Thank you very much
CoffeeCup
Influencer
 
Posts: 16
Liked: never
Joined: Wed Jul 15, 2015 4:19 pm
Full Name: Luba

Re: Backup Copy Job - One giant one, or one for each Backup

Veeam Logoby foggy » Fri May 12, 2017 4:44 pm

Hi Luba, seems you're perfectly getting all pros and cons of each approach. It's totally up to you to decide what fits your environment best or to find some middle ground. Some additional considerations are mentioned above.
foggy
Veeam Software
 
Posts: 14743
Liked: 1081 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson


Return to Veeam Backup & Replication



Who is online

Users browsing this forum: Bing [Bot], Google Feedfetcher, Yahoo [Bot] and 58 guests