Currently I have two backup jobs running each evening, they are linked together, once the first job finishes the second starts
The first job is for my 4 Linux VMs
Under Storage...Advance Settings...vSphere tab the checkbox "Enable VMware Tools quiescence" is checked
Under Guest Processing the checkbox "Enable application-aware processing" is unchecked
The second job is for my 36 Windows VMs
Under Storage...Advance Settings...vSphere tab the checkbox "Enable VMware Tools quiescence" is unchecked
Under Guest Processing the checkbox "Enable application-aware processing" is checked
Since the settings to backup a Linux VM and a Windows VM are different, do these have to be run as two separate jobs?
I am going to throw one more curve into this. I actually have 4 different jobs
Backup of 4 Linux VMs with source being a Nimble production array and the target being a Nimble array in our DR site
Backup of 36 Windows VMs with source being a Nimble production array and the target being a Nimble array in our DR site
Backup of 4 Linux VMs with source being a Nimble production array and the target being an Exagrid box off campus
Backup of 36 Windows VMs with source being a Nimble production array and the target being an Exagrid box off campus
The two Nimble arrays are connected by a 10 gig connection on campus. Our off campus Exagrid box has a 500Mbps connection. Should I start all 4 of these jobs at the same time and let Veeam sort it out? Right now I have these 4 chained
You can start first and second backup jobs at the same time and let Veeam sort it out.
Then I'd highly recommend to replace other two backup jobs by backup copy jobs that will be moving data blocks from the DR site repository to the off campus.
Thus, you will significantly reduce the workload on the production and let Veeam to allocate resources in the best way. Thanks!
We cannot use a Backup Copy job to backup to the Exagrid. When running Veeam forever forward incremental, when the number of restore points exceeds the retention, a transform happens. The oldest incremental is rolled into the full and then deleted. The Exagrid does a poor job of this transform since it would need to drag data out of the archive. To prevent the Exagrid from doing this transform, a full or synthetic backup must be run before this transform point is reached. A Backup Copy job only allows a full backup, not a synthetic full. Doing a full backup across our WAN connection would not work, not enough bandwidth. For this reason, we use a Backup job to the Exagrid. The Exagrid backup jobs have a retention of 10 days so by running a synthetic full each Saturday, the transform never takes place. This synthetic full happens directly on the Exagrid box so no data traverses the WAN.
If my understanding of all of this is off, please let me know
Your understanding is correct, but synthetic full also requires data to be retrieved from the archive unless the entire week chain is stored in the landing page, which then can be achieved with the backup copy as well.
That is true but I thought that the Exagrid box has some technology built in so a synthetic full will be faster than the transform process? If both of them take equally long and are both done directly on the Exagrid box them perhaps I should consider moving to a Backup Copy job. Your thoughts?
I do Linux and Windows VM's in 1 job. I enable "VMware Tools quiescence" and also enable "application-aware image backups", you can set different credentials for certain VM's or even disable it for certain VM's in the job.