Discussions specific to the VMware vSphere hypervisor
Post Reply
Fiskepudding
Expert
Posts: 213
Liked: 26 times
Joined: Feb 01, 2012 7:24 am
Full Name: Espen Dykesteen
Contact:

Considerations, selecting entire ESX host in backup jobs?

Post by Fiskepudding » Mar 20, 2012 12:58 pm

Hello

It seems very convenient to select an entire ESX host when creating the backup job.
I am thinking one HOST for each job.

Lets say the host has 15 VM's with total of 3 TB data.
I guess there will better deduplication, so storage space is reduced some.

But is this generally a good idea? I am thinking about restore issues, and especially "Instant VM recovery".
How well will this play out, when running 15 VM's from the same deduped and compresses file?
If there were a optoin that planned the job for all VM's on the host but actually did split the VMS in different .vbk files i guess i would have been less concerned.

Anyone given this a thought, or have experience with this?

Thanx

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

Re: Considerations, selecting entire ESX host in backup jobs

Post by foggy » Mar 20, 2012 1:46 pm

Espen, placing several VMs in a single job is a common practice and the number of VMs in a job does not affect the restore speed of a particular VM. However, if we are talking about Instant Recovery of several VMs, I would like to pay your attention at this thread as it contains some good considerations about the whole concept and usage of this functionality, which could be useful in regard to your question.

Fiskepudding
Expert
Posts: 213
Liked: 26 times
Joined: Feb 01, 2012 7:24 am
Full Name: Espen Dykesteen
Contact:

Re: Considerations, selecting entire ESX host in backup jobs

Post by Fiskepudding » Mar 20, 2012 1:57 pm

Thanx, good thread.

dellock6
Veeam Software
Posts: 5683
Liked: 1603 times
Joined: Jul 26, 2009 3:39 pm
Full Name: Luca Dell'Oca
Location: Varese, Italy
Contact:

Re: Considerations, selecting entire ESX host in backup jobs

Post by dellock6 » Mar 21, 2012 8:22 am

You would also say seelcting an ESX as backup source is good only if your VMs are not managed in a cluster, since using vMotion or HA will move the VMs into other hosts and so your backup jobs will have different VM lists from time to time, and so the VM moved into a new ESX will have to get a full backup.
Usually clusters, resource pools or datastore (even VM folders) are good "high-level" selections for backup of multiple VMs.
Luca Dell'Oca
Principal EMEA Cloud Architect @ Veeam Software

@dellock6
https://www.virtualtothecore.com/
vExpert 2011 -> 2019
Veeam VMCE #1

Post Reply

Who is online

Users browsing this forum: No registered users and 16 guests