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
After you restore vCenter Server, the vCenter Server view of the virtual machines may be out
of sync with the ESXi view of the virtual machines. This is also true if you performed the backup
while there were in-flight operations on vCenter Server. If virtual machines disappear after you
restore vCenter Server, you can refer to the following cases.
a The missing virtual machine is located on the destination ESXi host and is registered with
the destination ESXi host, but it is not in the vCenter Server inventory. You must manually
add the virtual machine to the vCenter Server inventory.
b The missing virtual machine is located on the destination ESXi host, but it is not registered
with the destination ESXi host and it is not in the vCenter Server inventory. You must
manually register the virtual machine to the ESXi and add the virtual machine back to the
vCenter Server inventory.
c The missing virtual machine is located on the destination ESXi host, but it is not registered
with the destination ESXi host. Within the vCenter Server instance, the missing virtual
machine is marked as orphaned. You must remove the virtual machine from the vCenter
Server inventory and add it again.
n Restoring vCenter Server from a backup that has an out of date linked clone virtual machine
layout.
If you create a linked clone virtual machine after the backup and you restore vCenter Server
from the old backup, then after the restore, 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. To avoid this corruption, you must wait until all linked clone virtual
machines get discovered by the vCenter Server before you remove virtual machines.
vSphere High Availability
Restoring vCenter Server from a backup may cause it to roll back 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. Ensure that the vSphere HA cluster state stays the
same during restore and backup operations. Otherwise, the following potential problems are
present.
n If hosts are added or removed to/from the vSphere HA cluster after backup and before
vCenter Server restore, virtual machines could potentially fail over to hosts not managed by
the vCenter Server but are still part of the HA cluster.
n Protection states for new virtual machines are not updated on the vSphere HA agents on the
hosts which are part of the vSphere HA cluster. As a result, virtual machines are not protected/
unprotected.
n New cluster configuration state is not updated on the vSphere HA agents on the hosts which
are part of the vSphere HA cluster.
vCenter Server Installation and Setup
VMware, Inc. 67