You can perform an upgrade installation as long as your environment meets the Virtual Storage Console for VMware vSphere requirements. There are several things you should consider and record before you upgrade your version of VSC.
VSC 6.2 requires 64-bit Windows servers. If you have a32-bit Windows environment, you must perform special steps and manually move certain data to upgrade to a 64-bit Windows system. For information about doing this, see Upgrading from a 32-bit installation to a 64-bit installation of VSC for VMware vSphere.
In addition, VSC 6.2 requires that the vCenter Server be running vSphere 5.5 or later. If you attempt to install VSC 6.2 on an earlier version of vSphere, you receive an error message. This message varies depending on whether you have thick provisioning enabled. With thick provisioning, the message is similar to the following:
The VSC plugin is only available in the vSphere web client.
Without thick provisioning, the error message is the following:
Registration failed with the following message: NVPF-00017: This version of vCenter (5.1.0) found at https://00.00.000.000:443/sdk is not supported. Please upgrade to vCenter 5.5 or later.
VSC automatically rediscovers your storage after you perform an upgrade. It is a good practice to record your storage system information before the upgrade so that you can confirm that all of the storage systems were rediscovered after the upgrade.
If you are using backup and restore features, it is important to record the storage systems used for those operations and the credentials associated with them. Prior to VSC 4.2, the Backup and Recovery plug-in managed its own storage system discovery and credentials. Because VSC did not discover those storage systems, they might not appear in the list of storage systems that VSC manages.
After an upgrade, when you check the storage systems used for backup and restore operations, you should also verify that the systems have at least the minimum credentials required to perform these operations. You can use VSC to update the credentials.
If any storage systems are missing after the upgrade, you can select the Update All icon to force VSC to discover storage systems. If that does not work, you can manually add the storage system by using the Add icon found on the VSC Storage System page or the Add storage system option found in the vCenter Actions menu.
You should not modify the VSC standard roles. If you make changes to these roles, you lose those changes when you upgrade your VSC installation or restart the VSC Windows service. These roles return to the current default values each time you install VSC, restart the VSC Windows service, or modify your VSC installation.
If you made any changes to these roles, you should record the changes. After you upgrade your installation, you can create new roles that reflect those changes.
The upgrade process overwrites the existing preferences files with new preferences files for features that VSC uses. It is a good practice to record changes you made to preference files before an upgrade.
For provisioning and cloning tasks, VSC creates a backup of the preferences file, etc/kamino/old_kaminoprefs.xml. If you modified the etc/kamino/kaminoprefs.xml preferences file, you can copy the changes from etc/kamino/old_kaminoprefs.xml to the new file that VSC creates during the upgrade.
If you are using VASA Provider for clustered Data ONTAP, you must unregister it before you upgrade your VSC software. If you do not unregister it, you might not be able to see the VASA Provider section of the VSC GUI when you register the VASA Provider server in the upgraded installation.
From the vSphere Web Client's Home page, click . Enter the vpserver password and select Unregister.
You must remove the user interface (UI) extensions that are cached on the vCenter Server before you upgrade VSC or VASA Provider.