Cluster Rename in Large Environment - Possible Issues?

[slanger]

For a large installation (several thousand VM's, couple hundred hosts) is there any reason not to rename clusters? I have changed cluster names in much smaller environments with no ill effects.  We already know it will not affect the backup product in use, and we will have to adjust some queries for custom groups in vROps after the changes.

Anything else to keep in mind?  Any gotchas that we might be missing?  thanks for any input on this.

[edit: of this is the wrong place to post this question, please direct me to the proper forum, thanks!]

[vervoortjurgen]

vShield manager/NSX?

DRS rules

vDS switches

Self created alarms..

Backup (if you selected your cluster as backup source will affect backup)

Host profiles

SRM!!

...

top of my head what i can think of but i think should be ok to change name.

[slanger]

Thank you... I'm wondering how DRS rules would be affected.  They should stay put through a simple rename of the cluster, no?

vDS Switches... wont they remain intact through a cluster rename?    I cant find any documentation from VMware on this... they should have a KB.

[Wh33ly]

DRS rules stay in place indeed, they are not affected by changing the name.

We don't use vDS here so can't help you on that one.

[kclark2907]

The parent of vDS Switches is the datacenter not the cluster, that said you can rename your cluster or datacenter without affecting the vDS (just tested this in a dev environment)

[markdjones82]

Renaming of a cluster should not affect anything that I am aware of.  The API's use UUID's for objects when communicating between products.  The name is really just used for the GUI and things like Powercli scripts.