vRO – Creating a test copy of your appliance

Recently I was investigating the migration of an external vRealize Orchestrator instance to an embedded instance inside vRealize Automation. But for testing purposes I didn’t want to use the production appliances… So I had to create a test vRA and vRO appliance.

I started with vRO. The control Center has the option to export and import the configuration. At first the import didn’t work because of insufficient memory. But after increasing the available memory and importing the configuration from my production appliance, I still was missing important stuff like workflows.

For some reason I didn’t think of the obvious solution: get the files from the production appliance and import them in the test environment. This gave me an EXACT copy. So the next step was to change the host name and the IP configuration.

I started the imported VM (disconnect the nic) and logged on to the console. Then I ran this command:

/opt/vmware/share/vami/vami_config_net

This will let you change the hostname (option 3) and to change the IP address (option 6).

Shutdown the appliance, connect the nic and start it up again. Now you have a copy of your production vRO appliance to work with. I didn’t test it but this might also work with vRA.

Allign SDRS Thresholds and Datastore Usage on Disk Alarms

Last week I was monitoring a relatively large vSphere cluster with several host clusters and datastore clusters. I saw a couple of datastore warnings related to the datastore usage. There were two or three datastores that were more than 75% utilized.

Strange, because other datastores in the same datastore cluster had more than plenty of free space. So why didn’t SDRS kick in to distribute the files more evenly?

The reason for this is that the default warning threshold for the alarm is 75%. However, the default space utilization ratio threshold for SDRS is 80%.

So SDRS only kicks in when the utilization is more than 80%. But by then, the alarm for the datastore usage is already triggered.

My solution for this ‘problem’ was to align both thresholds at 75%. If for some reason SDRS cannot move files to another datastore and it gets even fuller there is still the alarm alert that is set at 85%.