VMware vRealize Orchestrator Plug-In for VMware Site Recovery Manager 8.6 Release Notes

Site Recovery Manager 8.6 \| 11 OCT 2022 \| Build 20555463 VMware vRealize Orchestrator Appliance 8.9 \| 09 AUG 2022 \| Build 20227501 VMware vRealize Orchestrator Plug-In for Site Recovery Manager 8.6 \| 11 OCT 2022 \| Build 20554592 \| Download Check for additions and updates to these release notes.

Site Recovery Manager 8.6 | 11 OCT 2022 | Build 20555463

VMware vRealize Orchestrator Appliance 8.9 | 09 AUG 2022 | Build 20227501

VMware vRealize Orchestrator Plug-In for Site Recovery Manager 8.6 | 11 OCT 2022 | Build 20554592 | Download

Check for additions and updates to these release notes.

What's New in VMware vRealize Orchestrator Plug-In for VMware Site Recovery Manager 8.6

The VMware vRealize Orchestrator Plug-in for VMware Site Recovery Manager 8.6 release adds support for VMware vRealize Orchestrator 8.9.

About the VMware vRealize Orchestrator Plug-In for VMware Site Recovery Manager 8.6

With the VMware vRealize Orchestrator plug-in for VMware Site Recovery Manager, Site Recovery Manager administrators can simplify the management of their Site Recovery Manager infrastructure by extending the robust workflow automation platform of Orchestrator. You build these workflows by using the drag-and-drop capability of the workflow editor in the Orchestrator client. Orchestrator uses the plug-in to access the functionality of Site Recovery Manager and the Site Recovery Manager API. The included prebuilt workflows simplify the process of creating custom workflows.

Installation and Upgrade

The Orchestrator plug-in for Site Recovery Manager software is distributed as an Orchestrator application file.

You must install and configure vRealize Orchestrator before you install the Orchestrator plug-in for Site Recovery Manager, see the Installing and Configuring VMware vRealize Orchestrator 8.9 documentation.

For information about how to install the Orchestrator plug-in for Site Recovery Manager on VMware vRealize Orchestrator 8.9, see the Install or Update a vRealize Orchestrator Plug-In topic in the VMware vRealize Orchestrator 8.9 documentation.

After you install the Orchestrator plug-in for Site Recovery Manager, you must configure the connection between the vRealize Orchestrator instance and the vCenter Server instance on your Site Recovery Manager site. For information about how to configure the connection with your vCenter Server, see the VMware vRealize Orchestrator 8.9 documentation.

After you install the Orchestrator plug-in for Site Recovery Manager, you can find the Site Recovery Manager workflows in the vRealize Orchestrator UI:

Go to Library > Workflows
Search for the workflow by name or switch to tree view from the top right icon. In tree view you can find the workflows under Library >SRM folder.

Before you can run the Site Recovery Manager workflows, you must configure the plug-in to work with your Site Recovery Manager by selecting Library > SRM > Configuration and running the following workflows:

Run the Configure Local Sites workflow.
Run the Configure Remote Site workflow.
Run the Login Remote Site workflow.

You must run the Login Remote Site workflow once per Orchestrator Client session to log in to Site Recovery Manager on the remote site. The Orchestrator automatically logs out of Site Recovery Manager when you log out of the Orchestrator client.

For information about how to uninstall your Site Recovery Manager plug-in, see the Delete a Plug-In topic in the Installing and Configuring VMware vRealize Orchestrator documentation.

Example Workflows

The Orchestrator plug-in for Site Recovery Manager includes example workflows that demonstrate how you can automate Site Recovery Manager operations by using Orchestrator, such as:

Create VM and Protect It:
1. Creates a virtual machine
2. Adds the virtual machine to an existing protection group
Create Protection Group for Array Based Replication, Protect Virtual Machines, Add Protection Group to Recovery Plan:
1. Creates an array-based protection group
2. Protects the virtual machines in a given datastore by adding that datastore to the protection group
3. Adds the new protection group to an existing recovery plan

Caveats and Limitations

The vRealize Orchestrator Plug-In for Site Recovery Manager 8.6 supports vRealize Orchestrator 8.9.1 and 8.10 with certain limitations. For more information, see the Known Issues section.
If you change the Site Recovery Manage certificate, the Site Recovery Manager site is no longer visible in vRO inventory. You must run 'Configure Local Sites' workflow to add the site and accept the new certificate, and then run 'Login Remote Sites' to log in to the site.
If the protection site is not available, you cannot perform the following actions by using vRealize Orchestrator workflows, but you can use the Site Recovery Manager user interface instead:
- Create a recovery plan or change VM recovery settings;
- Add or remove a test network mapping to a recovery plan;
- Add or remove a protection group to an existing recovery plan.

Known Issues

New - The Configure Local Sites workflow fails when using the plug-in with vRealize Orchestrator 8.9.1 and 8.10

When you run the Configure Local Sites workflow, the workflow fails at the Validate step with the following exception: "com.vmware.vim.vmomi.core.exception.CertificateValidationException: Server certificate chain is not trusted and thumbprint doesn't match"

Workaround:

SSH into the vRealize Orchestrator appliance.

To synchronize the local keystore with vRealize Orchestrator, run the following command:

vracli cluster exec -- bash -c 'base64 -d <<< "a3ViZWN0bCAtbiBwcmVsdWRlIGV4ZWMgLXQgJChrdWJlY3RsIGdldCBwb2QgLW4gcHJlbHVkZSAtbCBhcHA9dmNvLWFwcCAtbyBqc29ucGF0aD0iey5pdGVtc1swXS5tZXRhZGF0YS5uYW1lfSIgLS1maWVsZC1zZWxlY3RvciBzcGVjLm5vZGVOYW1lPSQoY3VycmVudF9ub2RlKSkgLWMgdmNvLXNlcnZlci1hcHAgLS0gYmFzaCAtYyAiYmFzZTY0IC1kIDw8PCAnUzFOZlVFRlVTRDBpTDNWemNpOXNhV0l2ZG1OdkwyRndjQzF6WlhKMlpYSXZZMjl1Wmk5elpXTjFjbWwwZVM5cWMzTmxZMkZqWlhKMGN5SUtURTlIWDBaSlRFVTlKRXhQUTBGTVNFOVRWRjlNVDBkZlJrbE1SVjlFU1ZKRlExUlBVbGt2ZG5KdlgyeHZZMkZzWDJ0bGVYTjBiM0psWDNONWJtTXViRzluQ2dwR1NWQlRYMDFQUkVWZlJVNUJRa3hGUkQwaVpXNWhZbXhsWkNJS1JrbFFVMTlOVDBSRlgxTlVVa2xEVkQwaWMzUnlhV04wSWdwcFppQmJXeUFpSkVaSlVGTmZUVTlFUlNJZ1BYNGdYaWdrUmtsUVUxOU5UMFJGWDBWT1FVSk1SVVI4SkVaSlVGTmZUVTlFUlY5VFZGSkpRMVFwSkNCZFhRcDBhR1Z1Q2lBZ0lDQkxVMTlVV1ZCRlBTSkNRMFpMVXlJS1pXeHpaUW9nSUNBZ1MxTmZWRmxRUlQwaVNrdFRJZ3BtYVFvS0NteHZaMTl0WlhOellXZGxLQ2tnZXdvZ0lHVmphRzhnSWxza0tHUmhkR1VnTFMxMWRHTWdJaXNsUmxRbFZDNGxNMDVhSWlsZElDUXhJaUErUGlBa1RFOUhYMFpKVEVVS2ZRb0tablZ1WTNScGIyNGdhVzV6ZEdGc2JGOWpaWEowS0NrZ2V3b2dJQ0FnYkc5allXd2dZV3hwWVhNOUpERUtJQ0FnSUd4dlkyRnNJSEJsYlY5emRISnBibWM5SkRJS0lDQWdJR2xtSUZzZ0xYb2dJaVJoYkdsaGN5SWdYVHNnZEdobGJnb2dJQ0FnSUNBZ0lHVmphRzhnSWtObGNuUnBabWxqWVhSbElHRnNhV0Z6SUdseklHVnRjSFI1TGlCRGIzVnNaQ0J1YjNRZ2MzbHVZMmh5YjI1cGVtVWdkR2hsSUdObGNuUnBabWxqWVhSbExpSUtJQ0FnSUNBZ0lDQnNiMmRmYldWemMyRm5aU0FpUTJWeWRHbG1hV05oZEdVZ1lXeHBZWE1nYVhNZ1pXMXdkSGt1SUVOdmRXeGtJRzV2ZENCemVXNWphSEp2Ym1sNlpTQjBhR1VnWTJWeWRHbG1hV05oZEdVdUlnb2dJQ0FnSUNBZ0lISmxkSFZ5YmlBeENpQWdJQ0JtYVFvZ0lDQWdhV1lnV3lBdGVpQWlKSEJsYlY5emRISnBibWNpSUYwN0lIUm9aVzRLSUNBZ0lDQWdJQ0JsWTJodklDSkRaWEowYVdacFkyRjBaU0J3WlcwZ2FYTWdaVzF3ZEhrdUlFTnZkV3hrSUc1dmRDQnplVzVqYUhKdmJtbDZaU0JqWlhKMGFXWnBZMkYwWlRvZ0pHRnNhV0Z6SWk0S0lDQWdJQ0FnSUNCc2IyZGZiV1Z6YzJGblpTQWlRMlZ5ZEdsbWFXTmhkR1VnY0dWdElHbHpJR1Z0Y0hSNUxpQkRiM1ZzWkNCdWIzUWdjM2x1WTJoeWIyNXBlbVVnWTJWeWRHbG1hV05oZEdVNklDUmhiR2xoY3k0aUNpQWdJQ0FnSUNBZ2NtVjBkWEp1SURJS0lDQWdJR1pwQ2dvZ0lDQWdaV05vYnlBaVUzbHVZMmh5YjI1cGVtbHVaeUJqWlhKMGFXWnBZMkYwWlNBa1lXeHBZWE1nZEc4Z2JHOWpZV3dnYTJWNWMzUnZjbVVpQ2lBZ0lDQnNiMmRmYldWemMyRm5aU0FpVTNsdVkyaHliMjVwZW1sdVp5QmpaWEowYVdacFkyRjBaU0IzYVhSb0lHRnNhV0Z6T2lBa1lXeHBZWE1nZEc4Z2JHOWpZV3dnYTJWNWMzUnZjbVV1WEc0Z1EyVnlkR2xtYVdOaGRHVTZJRnh1SUNSd1pXMWZjM1J5YVc1bklnb0tJQ0FnSUhSbGMzUWdMV1FnTDNWemNpOXNhV0l2ZG1OdkxXTnNhUzltYVhCekx5QjhmQ0J5Y0cwZ0xXa2dMUzF1YjJSbGNITWdMM1pqYnkxalptY3RZMnhwTG5Kd2JRb2dJQ0FnUWtOZlJrbFFVMTlLUVZKVFBTUW9abWx1WkNBdmRYTnlMMnhwWWk5MlkyOHRZMnhwTDJacGNITXZJQzF1WVcxbElDY3FabWx3Y3lvbklDMTBlWEJsSUdaOGVHRnlaM01nZkhSeUlDY2dKeUFuT2ljcENpQWdJQ0JDUTE5UFVGUlRQU0l0Y0hKdmRtbGtaWEp3WVhSb0lDUjdRa05mUmtsUVUxOUtRVkpUZlNBdGNISnZkbWxrWlhJZ2IzSm5MbUp2ZFc1amVXTmhjM1JzWlM1cVkyRnFZMlV1Y0hKdmRtbGtaWEl1UW05MWJtTjVRMkZ6ZEd4bFJtbHdjMUJ5YjNacFpHVnlJZ29LSUNBZ0lHTmxjblJmWm1sc1pUMGtLRzFyZEdWdGNDQXZkRzF3TDJObGNuUXVNUzVZV0ZndWNHVnRLUW9nSUNBZ1pXTm9ieUFpSkhCbGJWOXpkSEpwYm1jaUlENGdKR05sY25SZlptbHNaUW9nSUNBZ2JHOWpZV3dnY21WemRXeDBQU1FvYTJWNWRHOXZiQ0FrUWtOZlQxQlVVeUF0YTJWNWMzUnZjbVVnSkV0VFgxQkJWRWdnTFhOMGIzSmxkSGx3WlNBa1MxTmZWRmxRUlNBdGMzUnZjbVZ3WVhOeklDUkxVMTlRUVZOVFYwOVNSQ0F0YVcxd2IzSjBZMlZ5ZENBdGJtOXdjbTl0Y0hRZ0xXRnNhV0Z6SUNJa1lXeHBZWE1pSUMxbWFXeGxJQ0lrWTJWeWRGOW1hV3hsSWlrS0lDQWdJR3h2WjE5dFpYTnpZV2RsSUNJa2NtVnpkV3gwSWdvS0lDQWdJSEp0SUMxbUlDUmpaWEowWDJacGJHVUtmUW9LWldOb2J5QWlRMkZzWTNWc1lYUnBibWNnZGxKUElFTmxjblJwWm1sallYUmxjeTRpQ2t0RldWTlVUMUpGWDB4SlUxUTlKQ2d2ZFhOeUwyeHBZaTkyWTI4dlkyWm5MV05zYVM5aWFXNHZkbkp2TFhSb2FXNHRZMlpuTG5Ob0lHdGxlWE4wYjNKbElHeHBjM1FwQ214dloxOXRaWE56WVdkbElDSkxaWGx6ZEc5eVpTQmpiMjUwWlc1ME9pQWtTMFZaVTFSUFVrVmZURWxUVkNJS0NpTWdRMjkxYm5RZ2RHaGxJR05sY25ScFptbGpZWFJsY3dwalpYSjBYMk52ZFc1MFBTUW9aV05vYnlBaUpFdEZXVk5VVDFKRlgweEpVMVFpSUh3Z1ozSmxjQ0FpUVd4cFlYTTZJaUI4SUhkaklDMXNLUXBzYjJkZmJXVnpjMkZuWlNBaVJtOTFibVFnSkdObGNuUmZZMjkxYm5RZ1kyVnlkR2xtYVdOaGRHVnpMaUlLQ2lNZ1NYUmxjbUYwWlNCdmRtVnlJR05sY25ScFptbGpZWFJsY3dwbWIzSWdhVzVrWlhnZ2FXNGdKQ2h6WlhFZ01TQWtZMlZ5ZEY5amIzVnVkQ2s3SUdSdkNpQWdZM1Z5Y21WdWRGOWpaWEowUFNRb1pXTm9ieUFpSkV0RldWTlVUMUpGWDB4SlUxUWlJSHdnWVhkcklDSXZRV3hwWVhNNkwzdHBLeXQ5YVQwOUpHbHVaR1Y0SWlrS0lDQmpkWEp5Wlc1MFgyRnNhV0Z6UFNRb1pXTm9ieUFpSkdOMWNuSmxiblJmWTJWeWRDSWdmQ0JoZDJzZ0p5OUJiR2xoY3pvdklIdHdjbWx1ZENBa01uMG5LUW9nSUdOMWNuSmxiblJmY0dWdFBTUW9aV05vYnlBaUpHTjFjbkpsYm5SZlkyVnlkQ0lnZkNCaGQyc2dKeTlDUlVkSlRpQkRSVkpVU1VaSlEwRlVSUzhzTDBWT1JDQkRSVkpVU1VaSlEwRlVSUzhnZTNCeWFXNTBJQ1F3ZlNjcENpQWdhVzV6ZEdGc2JGOWpaWEowSUNJa1kzVnljbVZ1ZEY5aGJHbGhjeUlnSWlSamRYSnlaVzUwWDNCbGJTSUtaRzl1WlE9PScgfCBiYXNoIC0i" | bash -'

Note: You must run the command after the workflow fails, otherwise the certificate is not imported and is not synchronized.

Re-run the Configure Local Sites workflow.

No Site Recovery Manager sites are displayed in the vRealize Orchestrator inventory if the user does not have privileges on all of the sites in an N:1 shared recovery site configuration

You can have more than one Site Recovery Manager instance installed against a certain vCenter Server instance. If you run the Configure Local Sites workflow with a user that does not have privileges on all Site Recovery Manager instances, no Site Recovery Manager sites are displayed in the vRealize Orchestrator inventory. The Site Recovery Manager sites that the user has privileges on are also not displayed.

Workaround: Run the Configure Local Sites workflow with a user that has privileges on all Site Recovery Manager instances.
Running Configure Remote Site workflow fails for a Site Recovery Manager instance that is paired after it has been added to vRealize Orchestrator

If you add an unpaired Site Recovery Manager to a vRealize Orchestrator inventory and then pair it, running the execution of Configure Remote Site workflow fails.

Workaround: Restart the vRealize Orchestrator server.
Running the Configure Local Sites, Remove Local Sites, or Configure Remote Site workflow makes the existing sessions to the remote sites invalid

Running the Configure Local Sites, Remove Local Sites, or Configure Remote Site workflow makes the established sessions between the local sites and their remote sites invalid.

Workaround: Log in to the remote sites again.
An error occurs if you call the Server.findAllForType(string type, string query) method

You cannot find an object by using only the type name. The following error occurs if you pass only the type argument to the Server.findAllForType(string type, string query) method : Unable to execute 'fetchAll' for type : … : 'java.lang.NullPointerException'.

Workaround:You must pass the optional query argument if you call the Server.findAllForType(string type, string query) method.

For example: x = Server.findAllForType(type, "");.