testing exchange item level restore leaves behind orphaned datastore and VM
I was testing the Exchange item level restore and read that it had to temporarily mount the database to do the item level restore - I saw it create the temporary datastore 564D453D-84D6-4C70-4488-C12F9691CA10 and then after the restore it went to (inactive).
I also see a temporary-0308somenumber (orphaned) in my vCenter tree node.
I thought it would clean these item up after itself, am I safe to just delete these items?
Backup 12.5 (vmware)
The temporary VM which is mounted from backup via "Run VM from Backup" feature should be removed automatically after 30 minutes of idleness (if you performed browsing of Exchange items) and right after recovery is completed if you perform Exchange mailboxes recovery. Note that orphaned VM may be left if your Acronis Backup for VMware (former vmProtect) appliance/Windows Agent is connected directly to ESXi host rather than to vCenter which manages this ESXi host. In this case it is safe to remove such orphaned VM manually from vSphere client (Delete from Disk).
I have a similar problem.
In order to extract a mailbox I mouted 2 restore points (run VM from backup).
After completing that task, I wanted to unmount the VM's, but they don't show up under Mounted VM(s).
So now I am left with 2 mounted backup's and an extra NFS datastore (/vmfs/volumes/564DFA2F-7D0B-BEF0-EE53-EE4E16B54211) pointing to the Appliance.
So how do I get rid of these?
Can I just use "Delete from disk" to delete the _mount VM's and then unmount and remove the NFS datastore?
If the Exchange items recovery (using temporary mounted VM) completed then it's safe to remove both the NFS datastore and the VMs using "Delete from disk" option. Note that there is also an auto-cleanup logics implemented on Acronis appliance side, which can clean up such traces automatically after reboot of appliance (or restart of Windows agent) is performed. Therefore I'd recommended cleaning up the traces and reboot the appliance after that.