Verify and document the current status of the environment before starting the upgrade process. This will help you assess the success of the upgrade.


Refer to Manage ViPR SRM System Health for details about verifying the health of your system.

Refer to the ViPR SRM Performance and Scalability Guidelines Service Assurance Suite SolutionPack Performance and Scalability Guidelines for details about determining configuration size.

Note: The Topology-Mapping-Service module, by default, is configured with 2GB max heap. For those installed on the Frontend and Backend hosts, actual maximum consumption is under 128MB. The additional memory need not be considered for sizing calculations. The Topology-Mapping-Service installed on the Collector host should have its full 2GB max heap considered.


  1. Look for blank reports and graphs. Determine if there are any blank reports caused by collection errors. Resolve any issues or document them for later follow up.
  2. Look for broken links and resolve any issues or document them for later follow up.
  3. Validate that end-to-end topology is working. Resolve any issues.
  4. Review the existing backend and databases. Check Report Library > System Health > Inventory > Backends and Report Library > System Health > Inventory > Databases Instances.
    • Check backend thresholds to verify that you have room to accommodate new sizing
    • Add additional backends and databases as required.
    • Refer to the Watch4net Database Split v1.2 document for help if you need to manually move data to redistribute the metrics.
  5. Review and document any customizations.
    For example:
    • Polling intervals
    • Timeout values

What to do next

Engage VMware Smart Assurance Support to resolve any observed issues prior to proceeding with the upgrade.