Skip to main content

Hi

 

Just like a ‘Plan’ can be created as a base plan and additional plans ‘derived’ from the base plan….

Does/ will  such a concept exist for VM Groups

 

The idea of

  1. Having a ‘base’ VM Group
  2. creating multiple derivative VM groups, with partial optional overrides  
  3. then having the derivative VM groups ‘update’ when the base group is updated

This would be incredibly useful

PS: There are mechanisms to come up with a ‘coded’ solution to this (and there is a subclient cloning process), but having a solution within the Admin Center would be ideal

 

 

 

 

 

 

 

That’s a cool idea!  I’ll pass this up the chain and see if there’s anything in the works.

@YYZ , would you mind sharing the use case with a bit more context?  What types of changes would you propagating down?

If you could describe the exact issue we hope to solve and how you’d propose we accomplish this, that will help!

Hi Mike

4 vCenters

Dev,

Test,

Pre-Prod,

Prod

 

Single CommServe

VMs are backed up entirely on a rules based regime

Different VM Groups for the one vCenter have different ‘requirements’

There would be 20 VM groups per vcenter

The same VM’s (roughly) live in each vcenter

eg

VM-Banking99-Dev

VM-Banking99-Test

etc

 

and we can have (roughly)  the same backup across the 4 vcenters

a VMgroup (might) have a  rule

VM=VM-Banking9*

and this will pick up the ‘that’ VM across all 4 environments

 

We dont have to go and create unique ‘subclients’ for all 4 vcenters

AND better yet; changes to the ‘VM Group’ plan at the base level can ‘ripple’ through the derived

 

eg if Dev change the name of the VM to VM-Systems99-Dev, and then roll that VM out into Production, we only have to make the change to the ‘Base’ group, rather than having to edit filters across all our VMgroups (aka subclients)

 

 

 

 

 

This makes good sense now.  I’ll look into this to see if a) we have something that solves it (non-coded as you said) and b) if I can get a CMR submitted.

I’ll be in touch!

FYI, I created CMR 313217 for this issue.

As usual, no ETA on inclusion though I wanted to be sure you had it for your records.

Mike

Thanks for carrying forward and feeding back.

 

Anything for a Rush fan!

Reply


Terms & ConditionsCookie settings