When the current SRM license key has expired
Protecting an existing VM in Protection Group
Adding a new VM to Protection Group
Performing a failover, failback or re-protect activity
Under vCenter Licenses > Assets > Solutions , appliance was showing unlicensed
ERROR
Operation FailedThere are not enough licenses installed to perform the operation.Operation ID: xxxxxxx-xxxxxxx-ae7b-xxxxx
NOTE : Site Recovery Manager preserves the license only during an upgrade within the same version, for example, from version 8.3.0.x to version 8.3.1, or from version 8.4.0.1 to version 8.4.0.2. During an upgrade to a different version, for example, from 8.4 to 8.5 or later, Site Recovery Manager reverts to an evaluation license. After the upgrade, you must Reassign your Site Recovery Manager license key.
Information That Site Recovery Manager Upgrade Preserves
VMware Live Site Recovery 9.0, 9.0.1, 9.0.2, 9.0.2.1, 9.0.2.2, 9.0.2.3, 9.0.2.4
Multiple SRM solutions found under vCenter Licenses > Assets > Solutions.
Improper license key assigned to the SRM solution.
Insufficient license assigned to the SRM solution.
SRM solution is still running with an evaluation key (Appropriate license key is still not assigned to SRM solution).
Check if the license key has a hard limit on the number of CPUs or VMs it can protect and if the limit is hit, in which case you may have to procure a new license key or increase the limit of the existing license by talking to sales rep or VMware license team.
NOTE: The following steps must be performed on Production & Recovery sites by taking appropriate backups of SRM servers.
Remove all the SRM solutions from vCenter Licenses > Assets > Solutions.
Restart srm-server service via VAMI of (Appliance) doing this will allow SRM solution to repopulate in vCenter.
Note: Once the SRM license has been reassigned, it may take time to load (from 1 min to 10 mins "may vary some times"), during this time VC UI needs to Re-login. Once the Licenses Reappears perform reassign. Follow below steps:
If step 2 fails - Reconfigure SRM (Appliance) to re-register its solution with vCenter.
Assign a valid SRM license key to the solution (Follow Step 2), this should resolve the issue.