6.7
Table Of Contents
- vCenter Server Upgrade
- Contents
- About vCenter Server Upgrade
- Overview of the vSphere Upgrade Process
- vSphere 6.7 Component Behavior Changes that Affect Upgrade
- Upgrade or Migration Order and Mixed-Version Transitional Behavior for Multiple vCenter Server Instance Deployments
- Differences between Upgrading and Migrating vCenter Server on Windows
- Upgrading or Migrating to vSphere License Service
- Differences Between vSphere Upgrades, Patches, Updates, and Migrations
- Support for Federal Information Processing Standard 140-2
- Support for Transport Security Layer 1.2
- Deployment Topologies with External Platform Services Controller Instances and High Availability
- Moving from a Deprecated to a Supported vCenter Server Deployment Topology Before Upgrade or Migration
- Example Upgrade Paths from vCenter Server version 6.x to version 6.7
- Example Migration Paths from vCenter Server for Windows to vCenter Server Appliance 6.7
- Upgrading vCenter Server for Windows
- About the vCenter Server for Windows Upgrade Process
- vCenter Server for Windows Requirements
- Pre-Upgrade Checks for vCenter Server and Platform Services Controller on Windows
- Hardware Requirements for vCenter Server and Platform Services Controller on Windows
- Storage Requirements for vCenter Server and Platform Services Controller on Windows
- Software Requirements for vCenter Server and Platform Services Controller on Windows
- Database Requirements for vCenter Server on Windows
- Required Ports for vCenter Server and Platform Services Controller
- DNS Requirements for vCenter Server and Platform Services Controller on Windows
- vSphere Web Client Software Requirements
- Before Upgrading vCenter Server
- Verify Basic Compatibility Before Upgrading vCenter Server
- Download the vCenter Server Installer for Windows
- Preparing a vCenter Server Database for Upgrade
- Prepare an Oracle Database for Upgrading vCenter Server
- Prepare Microsoft SQL Server Database Before Upgrading vCenter Server
- Use a Script to Create and Apply a Microsoft SQL Server Database Schema and Roles
- Prepare PostgreSQL Database Before Upgrading vCenter Server
- Database Permission Requirements for vCenter Server
- Verify That vCenter Server Can Communicate with the Local Database
- Preparing for Upgrading the Content Library
- Verify Network Prerequisites Before Upgrading
- Verify Load Balancer Before Upgrading vCenter Server
- Prepare ESXi Hosts for vCenter Server Upgrade
- Verify Preparations Are Complete for Upgrading vCenter Server
- Required Information for Upgrading vCenter Server on Windows
- Upgrading vCenter Server 6.0 or 6.5 on Windows
- Upgrading the vCenter Server Appliance and Platform Services Controller Appliance
- About the Upgrade Process of the vCenter Server Appliance and Platform Services Controller Appliance
- System Requirements for the New vCenter Server Appliance and Platform Services Controller Appliance
- Hardware Requirements for the vCenter Server Appliance and Platform Services Controller Appliance
- Storage Requirements for the vCenter Server Appliance and Platform Services Controller Appliance
- Software Requirements for the vCenter Server Appliance and Platform Services Controller Appliance
- Required Ports for vCenter Server and Platform Services Controller
- DNS Requirements for the vCenter Server Appliance and Platform Services Controller Appliance
- vSphere Web Client Software Requirements
- Preparing to Upgrade the vCenter Server Appliance and Platform Services Controller Appliance
- System Requirements for the vCenter Server Appliance Installer
- Download and Mount the vCenter Server Appliance Installer
- Synchronizing Clocks on the vSphere Network
- Transferring Data from an Existing vCenter Server Appliance
- Prepare ESXi Hosts for vCenter Server Appliance Upgrade
- Determine the Oracle Database Size and the Storage Size for the New Appliance
- Download and Run VMware Migration Assistant on the Source Update Manager Machine
- Prerequisites for Upgrading the vCenter Server Appliance or Platform Services Controller Appliance
- GUI Upgrade of the vCenter Server Appliance and Platform Services Controller Appliance
- Required Information for Upgrading a vCenter Server Appliance 6.0 or 6.5 or Platform Services Controller Appliance 6.0 or 6.5
- Upgrade a vCenter Server Appliance 6.0 or 6.5 with an Embedded vCenter Single Sign-On or Platform Services Controller by Using the GUI
- Upgrade a Platform Services Controller Appliance 6.0 by Using the GUI
- Upgrade a vCenter Server Appliance 6.0 or 6.5 with an External vCenter Single Sign-On or Platform Services Controller Instance by Using the GUI
- CLI Upgrade of the vCenter Server Appliance and Platform Services Controller Appliance
- Migrating vCenter Server for Windows to vCenter Server Appliance
- Overview of Migration from vCenter Server on Windows to an Appliance
- System Requirements for Migrating vCenter Server Deployments to vCenter Server Appliance Deployments
- Pre-migration Checks
- Known Limitations
- Preparing for Migration
- Synchronizing Clocks on the vSphere Network
- Preparing vCenter Server Databases for Migration
- Preparing to Migrate the Content Library
- Prepare Managed ESXi Hosts for Migration
- Preparing vCenter Server Certificates for Migration
- System Requirements for the vCenter Server Appliance Installer
- Determine the Oracle Database Size and the Storage Size for the New Appliance
- Determine the Microsoft SQL Server Database Size and the Storage Size for the New Appliance
- Download and Run VMware Migration Assistant on the Source Windows Machine
- Prerequisites for Migrating vCenter Server and Platform Services Controller
- Required Information for Migrating vCenter Server from Windows to an Appliance
- GUI Migration of vCenter Server with an Embedded vCenter Single Sign-On or Platform Services Controller to an Appliance
- GUI Migration of vCenter Server with an External vCenter Single Sign-On or Platform Services Controller to an Appliance
- CLI Migration of a vCenter Server Installation from Windows to an Appliance
- After Upgrading or Migrating vCenter Server
- Verify Your vCenter Server Appliance Upgrade or Migration Is Successful
- Log in to vCenter Server by Using the vSphere Client
- Install the VMware Enhanced Authentication Plug-in
- Uninstall the TLS Configuration Utility on Windows
- Collect vCenter Server Log Files
- Identity Sources for vCenter Server with vCenter Single Sign-On
- Reregister Solution in vCenter Server after Upgrade or Migration
- Roll Back a vCenter Server Appliance Upgrade or vCenter Server on Windows Migration
- Monitor and Manage Historical Data Migration
- Changing a vCenter Server Deployment Type After Upgrade or Migration
- Patching and Updating vCenter Server 6.7 Deployments
- Patching the vCenter Server Appliance and Platform Services Controller Appliance
- Update the Java Components and vCenter Server tc Server with VIMPatch
- Troubleshooting a vSphere Upgrade
- Collecting Logs for Troubleshooting a vCenter Server Installation or Upgrade
- Errors and Warnings Returned by the Installation and Upgrade Precheck Script
- Upgrade Issues with vCenter Server Containing Host Profiles
- Roll Back a vCenter Server Instance on Windows When vCenter Server Upgrade Fails
- Microsoft SQL Database Set to Unsupported Compatibility Mode Causes vCenter Server Installation or Upgrade to Fail
- Collect Logs to Troubleshoot ESXi Hosts
Procedure
1 Download the vCenter Server installer from the VMware Web site at
https://my.vmware.com/web/vmware/downloads.
vCenter Server is part of VMware vCloud Suite and VMware vSphere, listed under Datacenter &
Cloud Infrastructure.
2 VMware provides a sha-1 hash, a sha-256 hash, or an MD5 message digest for software downloads.
To confirm file integrity, use a sha-1, sha-256, and/or a MD5 utility on your computer to calculate your
own hash for files downloaded from the VMware web site.
See the VMware Web site topic Using Cryptographic Hashes at
http://www.vmware.com/download/md5.html.
3 Mount the ISO image to the Windows virtual machine or physical server on which you want to install
vCenter Server for Windows.
Preparing a vCenter Server Database for Upgrade
vCenter Server requires a database to store and organize server data. You can either upgrade your
embedded database to the bundled PostgreSQL database, or you can continue to use your external
database.
vCenter Server for Windows supports Oracle and Microsoft SQL database as an external database.
Although the database is automatically configured by the installer, you can configure an external
database manually or by using a script. In addition, the data source name user must have a specific list of
permissions.
For information about setting up and configuring a database, see vSphere Installation and Setup.
The database passwords are stored in clear text on the Windows virtual machine or physical host on
which you upgrade vCenter Server and in the vCenter Server Appliance. The files containing the
passwords are protected by using the operating system protection, that is, you must be a Windows local
administrator or a Linux root user to access and read these files.
vCenter Server instances cannot share the same database schema. Multiple vCenter Server databases
can reside on the same database server, or they can be separated across multiple database servers. For
Oracle databases, which have the concept of schema objects, you can run multiple vCenter Server
instances in a single database server if you have a different schema owner for each vCenter Server
instance. You can also use a dedicated Oracle database server for each vCenter Server instance.
You cannot upgrade vCenter Server and point to an older external vCenter Server database. You can
upgrade the vCenter Server 6.0 or 6.5 database to the latest version only by upgrading the
vCenter Server instance connected to that database.
Prepare an Oracle Database for Upgrading vCenter Server
Ensure that your Oracle database meets requirements, that you have the necessary credentials, and that
you complete any necessary cleanup or other preparation before upgrading vCenter Server.
vCenter Server Upgrade
VMware, Inc. 43