vCloud Usage Meter 3.5 is installed as a new appliance. You can optionally import configuration data (all data displayed on the Manage page), but not measurements, customers, and rules, from earlier versions by following this procedure.

About this task

Note:

After importing data, you might need to edit the following products:

  • NSX Manager: Enter the referencing vCenter server host name or IP address in the vCenter Host Name or IP text box and select the NSX Edition type. If you had selected NSX standalone reporting, you must select it again from Manage > Reports page because NSX now has three editions, select the reporting type for each edition.

  • Horizon DaaS: Enter the number of VDI Session Model value.

Prerequisites

  • Back up or snapshot the vCloud Usage Meter virtual appliance that you are importing from, in case an unexpected error occurs during the import process.

  • Verify that you have the TCP hostname or IP address of the older vCloud Usage Meter virtual appliance, and its root or usgmtr and Web application passwords.

Procedure

  1. Back up the vCloud Usage Meter appliance that you are importing from, to protect against the unlikely event that the importing process harms that vCloud Usage Meter
  2. Turn on sshd on the old vCloud Usage Meter with the service sshd start command.
  3. Create an SSH connection to the vCloud Usage Meter 3.5 instance. Log in as usgmtr and change to root.
  4. Run the importum <hostname> <version> command.

    <hostname> is the TCP hostname or IP address of the old vCloud Usage Meter and <version> is either 333 for vCloud Usage Meter 3.3.3 or 340 vCloud Usage Meter 3.4.0.

    Importum uses ssh and scp to export the database from the old system and copy it and the keystore files to vCloud Usage Meter 3.5. You are prompted twice, once by ssh and once by scp for the usgmtr password of vCloud Usage Meter 3.4.0 (or the root password if using vCloud Usage Meter 3.3.3).

    Customers and Customer rules are not migrated using Importum. For more information about importing Customers and Customer rules see Import Customers and Rules.

    Note:

    The log file might contain the following error messages, which you can ignore.

    • ERROR: must be owner of extension plpgsql

    • WARNING: no privileges could be revoked for "public"

    Other errors are considered as installation failures and a support request can be opened to report such occurrence.

  5. Turn off sshd on the old vCloud Usage Meter with the service sshd stop command.

Results

The password for the vCloud Usage Meter 3.5 Web application is set to the password of the old system. You can change it with the webpass command. Any self-signed VMware product certificates you accepted on the old vCloud Usage Meter are copied to vCloud Usage Meter 3.5. Any changes you made to web.xml or default.props on the old system are not preserved. You can run the 3.5 system in parallel with the old system to ensure it is working correctly. You can run the import script more than once.

What to do next

Monitor results to ensure continuous data collection.

After upgrading to vCloud Usage Meter 3.5, products such as vRealize Automation servers, which were added in previous vCloud Usage Meter versions, might get set as inactive (0.0.0.0). After the upgrade is completed, reactivate the products set to ‘Inactive’ from the Manage > Products page.