Cannot perform Recoveries in VMware vCenter Site Recovery Manager (SRM) with SRM Administrator role
search cancel

Cannot perform Recoveries in VMware vCenter Site Recovery Manager (SRM) with SRM Administrator role

book

Article ID: 343305

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

Symptoms:
  • Users with the SRM Administrator role are unable to perform a Failover or a Planned Migration within the SRM plugin.

  • Trying to execute a Recovery when logged in as a user assigned to the SRM Administrator role fails.

  • You see the error:

    Permission to perform this operation was denied.


Environment

VMware vCenter Site Recovery Manager 5.1.x
VMware vCenter Site Recovery Manager 5.5.x
VMware vCenter Site Recovery Manager 5.0.x

Cause

Users with the SRM Administrator role can perform all SRM configuration and administration operations. By default, users with this role cannot run recoveries. For more information, see the SRM Roles Reference section in the Site Recovery Manager Administration Guide.

Resolution

To resolve this issue, you must assign the user with a role that has permission to run Recoveries in SRM.

Also, you can modify the default SRM Administrator role to include the Recovery privilege on the vCenter Server by performing these steps:


  1. In the vSphere Client, navigate to Home > Administration > Roles.
  2. Right-click the SRM Administrator role and select Clone and create a new Role.
  3. Right-click the role and Select Edit role.
  4. Expand Site Recovery Manager > Recovery Plan.
  5. Select the checkbox next to Recovery and select OK to grant the permission.
  6. If your vCenter Servers are running in Linked Mode, you must perform it only once as the roles are replicated between sites. If your vCenter Servers are not running in Linked Mode, you must perform these steps on both vCenter Server instances.
  7. Apply the new role to those users who needs the permission to recover virtual machines using Site Recovery Manager.

Note: Existing users must log out and log back in to the vSphere client for new permission to take effect.