Symptoms
· Running a Test Recovery from Protected and/or Recovery site fails
· Running a Plan Migration from Protected and/or Recovery site fails
· Even after adding the license to the vCenter Server, you see error:
There are not enough licenses installed to perform the operation.
Cause
This issue occurs when a license is not assigned to an individual asset.
If you have re-installed vCenter Server or never used the SRM from Recovery to Production site, the license for an SRM asset can be unassigned.
Resolution
To resolve this, ensure the key is assigned to the SRM solution in the vCenter Server for re protecting the virtual machines on both production and disaster recovery site. You have to login to each vCenter separately and check.
The procedure to assign the license if not available is:
For 5.x C# Client:
1. In the vSphere Client, select Home > Administration > Licensing.
2. Click Manage vSphere Licenses.
3. Click Next to navigate to the Assign Licenses page.
4. Click the ESX, vCenter Server, or Solutions tab to display the available assets.
5. Select the assets to show.
6. In the Asset window, select one or more assets to license.
7. To select multiple assets, use Ctrl-click or Shift-click.
8. In the Product window, select an appropriate license key and click Next.
For 6.x Web Client:
1. In the vSphere Client, select Home > Administration > Licensing.
2. Click the Assets tab.
3. Click Solutions session.
4. Identify and select the SRM extension.
5. In the All Actions Menu, select Assign License.
6. In the Assign License window, select an appropriate license key and click Next.
If the license key you assign has a strong limit, the license capacity must be greater than or equal to the required license use for the asset. Otherwise, you cannot assign the license key. Check the EULA of the license to determine whether it has a strong limit.
Note: If you are Reprotecting your virtual machined, ensure that this has been done for both Protected and Recovery vCenter Servers.