Temporary Recovery for Testing Purposes

In this scenario, we recover the VM called yVM to the ESXi host located at 192.168.0.26:

[root@localhost bin]# sudo -u bacula /opt/bacula/bin/mount-vm
Automatically Selected Catalog: BaculaCatalog
Automatically Selected Client: localhost-fd

Job list:
1: LinuxEtc.2020-08-31_07.08.04_04
2: vsphere_hbck-centos7.2020-08-27_06.39.21_03
3: vsphere_hbck-centos7.2020-08-31_08.01.58_03
4: vsphere_yVM.2020-09-22_08.03.07_08
Select a Job: 4
Selected vsphere_yVM.2020-09-22_08.03.07_08
Automatically Selected Virtual Machine: yVM (14)
Automatically Selected Disks: 0

Action list:
1: Mount guest filesystem locally
2: Export guest filesystem through SMB
3: Export guest virtual machine to vSphere instance (Instant Recovery)
4: Cleanup
Select an Action: 3
Selected Export guest virtual machine to vSphere instance (Instant Recovery)
I: Instant Recovery Mode
I: NFSv4 detected.
Select where you want to mount the Virtual Machine

ESXi Host list:
1: [192.168.0.26]
    (administrator@vsphere.local, https://192.168.0.15/sdk)

2: [192.168.0.8]
    (administrator@vsphere.local, https://192.168.0.15/sdk)

Select an ESXi Host: 1
Selected [192.168.0.26]
    (administrator@vsphere.local, https://192.168.0.15/sdk)

[sudo] password for bacula:
Creating NFS Datastore...
OK: Registered this machine as a NFS Datastore (name=bir-14-6959, host=192.168.0.26)
Creating Virtual Machine...
OK: The Virtual Machine is now available (name=yVM-6959, host:192.168.0.26, datastore:bir-14-6959)

Action list:
1: Migrate Virtual Machine to a permanent Datastore
2: Cleanup
Select an Action: 2
Selected Cleanup
end