ViPR 2.2 - Upgrade EMC ViPR to version 2.2
Table of Contents
- If you have a previous version of ViPR Controller that is running Data Services, you cannot upgrade to ViPR 2.2. ViPR 2.2 is compatible with Controller-only environments. You must contact EMC Customer Support to upgrade ViPR running Data Services.
- Before upgrading the Controller-only environment, even if Data Services is not deployed, you must verify that there are no extra node ID addresses configured. In the ViPR UI, check Extra Nodes ID addresses field. . Remove any values from the
- In a multisite (geo) configuration, don't start an upgrade under these conditions:
- if there are add, remove, or update VDC operations in progress on another VDC.
- if an upgrade is already in progress on another VDC.
- if any other VDCs in the federation are unreachable, or have been manually disconnected, or if the current VDC has been disconnected.
In these cases, you should manually disconnect the unreachable VDC, and reconnect any disconnected VDC.
- In the unlikely event that you need to revert to the previous ViPR version, you should make a backup of the ViPR internal databases before upgrading. Refer to EMC ViPR native backup and restore service.
- Prepare for the ViPR virtual appliance to be unavailable for provisioning operations for approximately 1 minute for every 10,000 file shares, volumes, block mirrors, and block snapshots in the ViPR database. Plan for system management operations to be unavailable for an additional period of 8 minutes (for a 2+1 Controller node deployment) or 12 minutes (for a 3+2 Controller node deployment).
- Verify that all ViPR orders have completed before you start the upgrade.
- If RecoverPoint is used, upgrade RecoverPoint to a version supported by ViPR 2.2, before upgrading ViPR itself. Refer to the EMC ViPR Support Matrix for supported RecoverPoint versions.
Before you begin
- This operation requires the System Administrator role in ViPR.
- Refer to the pre-upgrade planning steps above.
- If necessary, configure the upgrade repository, including the credentials for accessing it, on the page of the ViPR UI. Default repository is https://colu.emc.com/soap/rpc.
- If your site cannot access the EMC repository, an alternative method of upgrade, for dark sites, is described in Upgrading EMC ViPR from an internal location.
- Verify that the ViPR controller status is Stable ( ).
- Select .
- Select an available
ViPR version and
The downloaded software is stored on the VM and can be installed at anytime.
- In the Software Versions list, click
Install next to the version that you want to upgrade to.
A rolling upgrade is performed on the ViPR VMs.The System Maintenance page opens while installation is in progess, and shows you the current state of the upgrade process.Wait for the system state to be Stable before making provisioning or data requests.
After you finish
Note the following about ViPR after an upgrade:
- Modified ViPR catalog services are always retained on upgrade, but to obtain new services, and original versions of modified services, go to Edit Catalog, and click Update Catalog.
- The upgrade process returns the trust store to its default contents. So if you removed certificates from the VIPR trust store before upgrade, they are returned to the trust store upon upgrade. Note that ViPR version 2.2 also adds a default list of certificates.
- After upgrading to version 2.2, any array with meta volumes need to be rediscovered, before you attempt to ingest those meta volumes.
- After upgrading to version 2.2, root login is disabled. To log in to ViPR Controller via the console, connect via SSH as svcuser, then switch user to root (su - root).
- After upgrading to version 2.2, rediscover your RecoverPoint Data Protection Systems. This refreshes ViPR Controller's system information and avoids inconsistencies when applying RecoverPoint protection with ViPR 2.2.