Environment
PlateSpin Protect 10.2
Situation
When viewing or editing an existing workload, the volume-to-datastore mapping does not reflect the actual information seen when viewing the target failover VM's settings, or states that the datastore is missing.
Resolution
This issue is cosmetic and will not disrupt the continued operation of the workload protection.
Cause
The information shown in the workload configuration will reflect the settings used when initially adding and preparing the workload. This issue can occur if any of the following happen:
1. The target failover VM moves to another datastore, via VMWare Storage vMotion or Storage DRS
2. One or more of the datastores selected when originally configuring the workload is renamed
3. One or more of the datastores selected when originally configuring the workload is removed