Running the vCenter Server on SimpliVity has always been an available option but to do so required custom configuration modifications. With the latest release of SimpliVity OmniStack, running the vCenter Server on the SimpliVity Data Virtualization Platform (DVP) is now fully supported without any modifications to the standard configuration of the OmniStack software. This allows the vCenter Server to be protected (backed up, replicated, and restored) using SimpliVity data protection features and further reduces the physical infrastructure footprint in the datacenter.
SimpliVity supports both the Windows vCenter Server and the vCenter Server Appliance (VCSA). The vCenter Server is required for the SimpliVity deployment, because of this the vCenter Server which will be managing the SimpliVity environment must first be deployed outside the environment and then migrated on to the SimpliVity DVP once the deployment has been completed.
There are several methods which can be used to migrate the vCenter Server into the SimpliVity environment. A few of these methods include:
- Using vMotion to migrate both the storage and running state of the vCenter virtual machine to a SimpliVity host.
- Using Storage vMotion to move storage and then removing and re-adding the vCenter virtual machine to inventory on a SimpliVity host.
- P2Ving or V2Ving the vCenter Server to a SimpliVity host.
- Copying (using scp for example) the vCenter Server virtual machine files to a SimpliVity datastore and adding the virtual machine into inventory on a SimpliVity host.
In this post I am going to look at the two most common methods: using vMotion to migrate both the storage and running state of the vCenter virtual machine to a SimpliVity host, and using Storage vMotion to move storage and then removing and re-adding the vCenter virtual machine to inventory on a SimpliVity host.