Backup Strategy

[willymaykett]

Hi,

I have a number of vm's I am going to backup.
I am wondering what is the best way to backup. Is it to create one job, and attach multiple vm's to this job. It looks like if I do this way, each vm gets processed one at a time.
I was thinking about setting up multiple jobs, each with a small number of vm's, and each pointing to a seperate disk array for performance.

What is the best way to configure the backup (and later, replication) schedule? I am also hoping to then fire off a backup script to doa backup to tape after the job is finished.

Thanks

[Gostev]

Hello, I recommend that you create large jobs with multiple VMs in each to get advantage of deduplication. You do not really need to point jobs to separate disk arrays, because the data gets heavily compressed and deduped, so the target storage is rarely a bottleneck. Most common bottlenecks are source (production) storage access speed, and CPU on Veeam Backup server.

[willymaykett]

Thanks Anton.

I have performed a test and selected 5 vm's. Some vm's have multiple disks, and I want to selectively choose which disks I back up for each vm. But it appears to be either all the disks on all the vm's or only the disks I select, but it applies to all the vm's. I can't pick disk 0 for vm0, then disk 0 and 1 for vm1.

Is this correct?

Thanks

[Gostev]

Correct, selective choise of disks per VM is a feature of version 5.

[Neurobit]

Can VMs be added & removed from existing jobs as needed?
Or, once a job is created, am I stuck with whatever VMs are initially selected?.

Thanks,
Paul

[Gostev]

Yes, sure - you can add and remove VMs.

[Neurobit]

Excellent. Thanks for the prompt reply.