vCenter Split

[Toine00]

Hi,

My company is splitting in 2 separate organizations.

The current vCenter server 7.0 got a lot of objects: Datacenters, hosts, roles, folders, permissions, ...

Some Datacenters, and the attached hosts, VMs, folders, etc. need to move to a new vCenter, itself related to a new AD domain, but with keeping permissions too. 

AD will be migrated with ADMT.

What would be the best option for this split migration?

I thought about several scenarios:

Scenario 1: vCenter cloning, then changing hostname and IP address and connecting some hosts to the new vCenter

Scenario 2: Build a new vCenter, join to the new domain, export settings from current vCenter with this export script, connect hosts to the new vCenter, import settings with this import script.

The script way may be risky and is missing some objects: dvSwitches, events, etc.

What do you think?

 

[Scott Vessey]

Don’t forget to buy a second vCenter license, and split your license keys as needed between the 2 entities. You may also need to consider support contracts for both entities. Talk to whoever you obtained your licenses through to ensure you don't do anything in breach of your contract.