my network guy is just implementing the lastest version of Networker. He ask me to create Resource Pools in our Vcenter in order to group the VMs. He wants to use these Resource Pools for the Backup jobs. I was wondering if this is a common practice or if there is a better way to group VMs for backup jobs. Any input is appreciated.
We run Vsphere 5.1, esx 5.1 U1, and NW 8.1 with Datadomain
Resource pools are really there to compartmentalize resources in a cluster or vSphere environment. If the goal is to logically group VMs, I've personally utilized folders within a vSphere environment.
This is an example of using vSphere folders:
In this example the 'Exchange 2013' folder will contain all VMs for the Exchange environment. This would be the ideal way to group VMs in a vSphere environment.
Is this similar to what you're seeing in the vSphere Web Client below? I see the resource group too, but am only able to select the disk. Let me know, thanks.
Thanks Steven. You're spot on. Folders should be used here as resource pools aren't appropriate. I wouldn't trying to shoe horn resource pools into the environment to conform to the backups. You might end up potentially seeing some strange things with your VMs and vSphere environment.
I attached some good guidance on resource pools.
If you want to forward me that case, we can take that two front approach with this.
mikuszed
90 Posts
1909
0
Posted December 5th, 2013 15:00
Hi Quasimonto,
Resource pools are really there to compartmentalize resources in a cluster or vSphere environment. If the goal is to logically group VMs, I've personally utilized folders within a vSphere environment.
This is an example of using vSphere folders:
In this example the 'Exchange 2013' folder will contain all VMs for the Exchange environment. This would be the ideal way to group VMs in a vSphere environment.
Hope this helps,
-Ed