Since policies are specific to a given vCenter you must also create corresponding policies on the recovery vCenter.
One example is a storage policy called SRM-tag-m50_1-m20_1 on the source site that looks for the tag category called srmDiscovery and a tag with the value of srm-PG-1:
The datastores are tagged with that tag, and the VMs have that policy:
On the remote vCenter, a policy is created that looks for that same tag:
When datastores are failed over from one vCenter to the other, SRM will ensure the tags on the source copy of the datastore are re-applied to the corresponding recovery datastores. The VMs that are on those datastores that are failed over in the recovery plan will be reconfigured to have the second storage policy. Since the second policy looks for those tags, the VMs will be in compliance and failover will succeed. Before that can happen, you must instruct what policies on the source policy map to what policies on the target vCenter. To do so, log into SRM and enter the appropriate site pair, and expand Configure > Storage Policy Mappings and then click New.
Choose automatic or manual mappings (if the names are different like above, choose manual, if the names are the same let SRM do it for you automatically).
Choose the source policy and then the target policy and click Add Mappings.
Click Next.
Select the reverse mapping to enable failback.
Click Next, then Finish to confirm.
Using Different Tags in each vCenter
An important thing to note is that both the source and target policies must also be compatible with the datastores before failed over. In other words, the storage policy on the recovery vCenter must look for tags that are already on the source VMFS datastores before SRM has failed them over. So while the policies on each side do not need to look for the same tags, the tags that are needed on the recovery side must already be added to the source datastores prior to recovery.
In the below case there is a policy on the source side that looks for the tag srm-PG01-vc01:
In SRM that policy is mapped to a policy on the target vCenter:
The target policy is looking for a different tag called srm-PG01-vc02:
The datastore only has the tag described in the first policy though:
If you attempt to failover this datastore now with SRM, the failover will not complete successfully. Prior to recovering the VMs, SRM will run a compliance check on the recovered datastores with the corresponding mapped policy. The datastore(s) will not be in compliance as the srm-PG01-vc02 tag will not appear.
SRM will automatically copy tags over from the source datastore to the recovered datastore, so if you are using different tags on the recovery datastore than what is needed on the protected site, ensure that those tags are already on the datastore prior to failover:
Note that if you add a tag to a datastore and immediately attempt a test or full recovery, the recovery might still fail with a compliance error. It can take a few minutes for SRM to sync new tags on source datastores.
On the recovered datastores, all of the tags will appear:
Which will allow for the failover to complete successfully: