8.0
Table Of Contents
- vCenter Server Installation and Setup
- Contents
- About vCenter Server Installation and Setup
- Introduction to vSphere Installation and Setup
- Deploying the vCenter Server Appliance
- File-Based Backup and Restore of vCenter Server
- Image-Based Backup and Restore of a vCenter Server Environment
- After You Deploy the vCenter Server Appliance
- Log In to vCenter Server by Using the vSphere Client
- Install the VMware Enhanced Authentication Plug-in
- Repoint vCenter Server to Another vCenter Server in a Different Domain
- Repoint a Single vCenter Server Node to an Existing Domain without a Replication Partner
- Repoint a vCenter Server Node to an Existing Domain with a Replication Partner
- Repoint a vCenter Server Node to a New Domain
- Syntax of the Domain Repoint Command
- Understanding Tagging and Authorization Conflicts
- vCenter Server Domain Repoint License Considerations
- Troubleshooting vCenter Server Installation or Deployment
If you create a linked clone virtual machine after the backup and you restore vCenter Server
from the old backup, then after the restore, the vCenter Server does not know about the
new linked clone virtual machine until vCenter Server discovers the new linked clone virtual
machine. If you remove all existing virtual machines before the new linked clone virtual
machine is discovered, then the removal of existing virtual machines corrupts the new linked
clone due to missing disks. In order to avoid this, you must wait until all linked clone virtual
machines are discovered by the vCenter Server before you remove virtual machines.
n Restoring vCenter Server from a backup that was taken during virtual machine registration.
If you are registering a virtual machine during the backup and you restore vCenter Server
from the old backup, then after the restore, the virtual machine is marked as orphaned in the
vCenter Server instance. You must manually add the virtual machine to the vCenter Server
inventory.
vSphere High Availability
Restoring vCenter Server from a backup might cause it to rollback to older version for the vSphere
HA cluster state (HostList, ClusterConfiguration, VM protection state) while the hosts in the cluster
have the latest version for the cluster state. You need to make sure the vSphere HA cluster state
stays the same during restore and backup operations. Otherwise, the following problems might
occur.
n If hosts are added or removed to or from the vSphere HA cluster after backup and before
vCenter Server restore, virtual machines could potentially failover to hosts not being managed
by the vCenter Server but are still part of the HA cluster.
n Protection state for new virtual machines is not updated on the vSphere HA agents on the
hosts that are part of the vSphere HA cluster. As a result, virtual machines are not protected or
unprotected.
n New cluster configuration state is not updated on the vSphere HA agents on the hosts that are
part of the vSphere HA cluster.
vCenter High Availability
Restoring vCenter Server requires vCenter HA to be reconfigured.
Storage Policy Based Management
Restoring vCenter Server from a backup can lead to the following inconsistencies related to
storage policies, storage providers, and virtual machines.
n Registered storage providers after backup are lost.
n Unregistered storage providers after backup re-appear and might show different provider
status.
n Changes, such as create, delete, or update, performed on storage policies after backup are
lost.
vCenter Server Installation and Setup
VMware, Inc. 54