Knowledge Base

Upgrading your vCenter Server installation with vCenter Server Heartbeat installed

1. Using the vCenter Server Heartbeat Console on the Secondary server, click System on the left navigation panel to open the Status and Control page, then click Switchover. Wait for the operation to complete successfully.
2. Shutdown vCenter Server Heartbeat, leaving the protected applications running on Secondary (active) server.
3. Using the Service Control Manager, configure Neverfail Server R2 service Startup Type to Manual on both Primary and Secondary servers.

1. Start VMware vCenter Installer for the version you want to upgrade to and select vCenter Server from the list.
   
   Important: Before proceeding with the database upgrade, perform a backup of the existing vCenter Server database and SSL certificates.
   
   
2. On the Database Upgrade page, select the option Yes, I want to upgrade the vCenter Server database.
3. Continue with vCenter Server installation and record all configuration settings used.
   
   Note: On the vCenter Server service account information page, VMware recommends providing the same credentials used for the current service (open the Service Control Manager and check the Logon As Account for VMware VirtualCenter Server service).
   
   
4. If asked, do not reboot the server.
5. When the vCenter Server upgrade process ends successfully, VMware recommends that you upgrade the existing extensions on the server. Details for each component upgrade can be found below.
6. Verify that vCenter Server and all updated extensions are operational.
7. If the upgrade on the Secondary server fails:
   1. Research the cause of the upgrade failure.
   2. If the issue can be resolved, proceed with upgrade procedure. Otherwise, revert to a previous version.
      
      To revert to a previous version:
      1. Uninstall the upgraded components.
      2. On the Secondary server, launch the vCenter Server Heartbeat Configure Server wizard and click the Machine tab. In the Current Role section choose Passive and click Finish.
      3. Reboot the server. vCenter Server Heartbeat starts and vCenter Server is stopped.
      4. On the Primary server, launch the vCenter Server Heartbeat Configure Server wizard and click the Machine tab. In the Current Role section choose Active and click Finish.
      5. Restart vCenter Server Heartbeat on the Primary Server and allow the system to synchronize.
      6. Start the vCenter Server Heartbeat Console and check that the system completes the Full System Check.
         
         
8. Change the server role to Secondary/passive.
   1. Launch the vCenter Server Heartbeat Configure Server wizard and click the Machine tab. In the Current Role section choose Passive and click Finish.
   2. Reboot the Secondary server.

1. Change the server role to Primary/active:
   1. Launch the vCenter Server Heartbeat Configure Server wizard and click the Machine tab. In the Current Role section choose Active and click Finish.
   2. Open a command prompt and navigate to <install_directory>\VMware\VMware vCenter Server Heartbeat\R2\Bin.
   3. Run the command:
      
      nfpktfltr.exe setfilter PassThru
      
      
   4. Verify the packet filter’s state to be passthru by running the command:
      
      nfpktfltr.exe getstate
      
      
2. Start VMware vCenter Installer for the version you want to upgrade to and select vCenter Server from the list.
3. On the Database re-initialization warning page, select the Do not overwrite, leave my existing database in place option and proceed with the installation process.
4. Continue with vCenter Server installation, using the identical configuration settings as used for installation on the Secondary server.
5. When the vCenter Server upgrade process ends successfully, VMware recommends that you upgrade the existing extensions on the server. Details for each component upgrade can be found below.
6. Since Orchestrator was introduced by the upgrade process and it was not configured on the Secondary server after upgrade, it is necessary to configure it at this time.
7. If asked, reboot the server.
8. Verify that vCenter Server and all updated extensions are operational.
9. Using the Service Control Manager, configure Neverfail Server R2 service Startup Type to Automatic on both Primary and Secondary servers.
10. Start vCenter Server Heartbeat on both servers.
11. Launch the vCenter Server Heartbeat Console and connect to the server pair.
    1. Check that the system completes the Full System Check and is replicating.
    2. Navigate to the vCenter Server Heartbeat Console Application > Tasks page and manually run the Protected Service Discovery task.

1. Shutdown vCenter Server Heartbeat.
2. Launch the Configure Server wizard and set the Secondary server Current Role to Passive.
3. Start vCenter Server Heartbeat on the Secondary server.
4. Start the Configure Server wizard on the Primary server and set the server Current Role to Active.
5. Start vCenter Server Heartbeat on the Primary server.
6. Launch the vCenter Server Heartbeat Console and verify that the system completes the Full System Check.
7. Investigate the cause of the vCenter Server failure on the Secondary server.

Installing vCenter Orchestrator Server as a Service

1. Using vCenter Orchestrator Web Configuration:
   1. Configure vCenter Orchestrator Server.
   2. Install vCenter Orchestrator Server, and then start it.
      
      
2. Navigate to the vCenter Server Heartbeat Console Application > Tasks page and manually run the Protected Service Discovery task. 
3. Using the vCenter Server Heartbeat Console, perform a switchover and wait for it to complete.

1. Ignore the vCenter Server Heartbeat warning:
   
   Could not find service: VMWAREORCHESTRATOR.
   
   
2. Using the vCenter Orchestrator Web Configuration, install vCenter Orchestrator Server as service then start it.

Upgrading Update Manager to 4.0 or any of its updates with a Remote SQL Database

1. Start VMware vCenter Installer for the version you want to upgrade to and select vCenter Update Manager from the list.
   
   Important: Perform a backup of the existing Update Manager database before proceeding with the next step.
   
   
2. On the Database Upgrade page select the option Yes, I want to upgrade the Update Manager database.
3. Continue with the install process.
4. When the upgrade is complete, verify that vCenter Update Manager is operational.

1. Using the Service Control Manager, start the VMware VirtualCenter Server service.
2. Start VMware vCenter Installer for the version you want to upgrade to and select vCenter Update Manager from the list.
3. During the vCenter Update Manager upgrade, provide the same configuration settings used during the upgrade process on the Secondary server.
4. On the Database re-initialization warning page, select the Do not overwrite, leave my existing database in place option and proceed with the installation process.
5. When the upgrade is complete, verify that vCenter Update Manager is operational.

Upgrading vCenter Converter from 4.0 to any of its updates

1. Start VMware vCenter Installer for the version you want to upgrade to and select vCenter Converter from the list.
2. Provide vCenter Server, vCenter Converter Server information and record all configuration settings used.
3. In the event that errors are encountered during the upgrade process, research the cause of the upgrade failure. If the issue can be resolved then it is safe to proceed with the upgrade procedure.

1. Using the Service Control Manager, start the VMware VirtualCenter Server service.
2. Start VMware vCenter Installer for the version you want to upgrade to and select vCenter Converter from the list.
3. Provide vCenter Server, vCenter Converter Server information. Make sure these are the same as those used during the upgrade on the Secondary server.
4. In the event that errors are encountered during the upgrade process, research the cause of the upgrade failure. If the issue can be resolved then it is safe to proceed with the upgrade procedure.