Snap Mount ESX Host under Avanced Options

PDL usually happens when your storage is attached to a group of hosts, rather than individual hosts. It depends on the array, but when Commvault zones in storage to a host, it re-uses the already established relationships. When we mount a snap datastore, if it zones storage to a clustered group, then all hosts will see and mount the snapshot datastore. When the snapshot is removed, it then is done ungracefully because Commvault does not expect it to be mounted on other hosts other than the one specified.

Its not the only reason, but this seems to be the most prevalent. The solution is to rezone your mount host 1:1 with datastores to the individual host in its own unique group that does not include other hosts.

Another workaround is to try this setting if you have multiple possible HBAs.

Have you tried to leverage proxyless backup copy? That removes the snap mount back to ESXi requirement in certain circumstances (like backup copy), but wont help if you want to restore from snap etc.

https://documentation.commvault.com/11.16/intellisnap_backup_operations_and_backup_copy_operations_run_without_proxy_esxi_host.html