If the volume is a valid VMFS datastore or RDM and it is intended to be in the pod and the removal of it would be difficult or inconvenient it is possible to resolve this without following the steps for a non-VMware volume.
Let's say the 4th volume listed here is a VMFS that was created after recovery and before reprotect:
This causes the reprotect to fail. An option to allow the SRA to bypass this is to manually tag the volume. SSH into the FlashArray hosting the promoted pod.
Review the puresra-failover tags on the current promoted pod (replace <pod name> with the pod name):
purevol list <pod name>* --tag --namespace puresra --filter 'key="puresra-failover"'
Copy the value which will be a long UUID like 49e593f1-7498-2cd1-86dc-d1ca09f101ff.
Run:
purevol tag <pod name::volume name> --key puresra-failover --value <UUID> --namespace puresra --non-copyable
Replacing the <pod name::volume name> with the pod name and the name of the volume with the missing tag and then replace <UUID> with the value you copied above.
Now all of the volumes in the pod are tagged with puresra-failover:
Secondly, depending on when they are created, they are also likely missing the puresra-demoted tag. If the volume was present before the recovery it will have it, if it was created sometime after the recovery it will not.
To check, go to the array where the ActiveDR for this pair is promoted and run:
purevol list <pod name>* --tag --namespace puresra --filter 'key="puresra-demoted"'
If that volume does not have the demoted tag add it as well. Note that the UUID is DIFFERENT than the previous UUID. The value of the puresra-failover tag is the UUID of promoted pod. The value for the puresra-demoted tag is the UUID of the demoted pod.
Copy the value which will be a long UUID like e184134e-5a94-9f76-5c53-ae33e6df93d5.
Run:
purevol tag <pod name::volume name> --key puresra-demoted --value <UUID> --namespace puresra --non-copyable
Replacing the <pod name::volume name> with the pod name and the name of the volume with the missing tag and then replace <UUID> with the value you copied above.
Now all of the volumes in the pod are tagged with puresra-demoted as well.
First re-run a Device Discovery for that pod pair:
If you see this error another volume is missing a tag or you did not tag it correctly.
Verify your tags are uniform and repeat the discovery until there are no errors on that pod pair:
Now re-run the reprotect:
The process will run:
And complete. Note that after the reprotect you will need to edit the protection group and ensure the datastore was added and protected.
While this process will also work for non-VMware volumes to--this is just delaying the process to fix it. It is best to take care of it now if the volume is a non-VMware volume.