Keep signature refresh
When the linked target is mounted with the same signature, a refresh of the linked target does not overwrite it. The datastore does not have to be deleted. There are two different procedures that can be used. The first ensures a clean refresh but takes longer. The second is quicker but has the potential to cause issues. Either is acceptable. The following are the recommended steps for a clean refresh.
- Shut down all VMs on the linked target datastore.
- Remove the VMs from inventory.
- Unmount the datastore from each ESXi host by using the CLI.
- Relink the target device.
- Remount the datastore on an ESXi host by using the CLI.
- Re-register the VMs.
The following steps provide a quicker refresh.
- Shut down all VMs on the linked target datastore.
- Relink the target device.
- Refresh the contents (within the vSphere Client).
Some caveats around this procedure include:
- It may be necessary to unmount and remount the datastore on each ESXi host with the CLI, if the datastore:
- Fails to refresh (folder dates do not revert).
- Shows no content.
- If the registered VMs from the datastore are named differently than the original VMs, the registered VM reverts to the original VM name. For example, the VM in the linked target was named TEST, but the VM was registered as TEST_VM. This scenario may occur automatically, or when a power-on is attempted (the power-on will error and at that point the VM is renamed).
It is possible that some other unforeseen event may occur, which is why the clean refresh is recommended.