However, if you navigate to another host and then back again, both the stop sign and the check mark are gone.
The only way to discover this, when you wonder why the VM is zipped in zero seconds to zero bytes, is to locate the log file and find an innocent entry in the log file that points you in the right direction:
- Removing excluded VMs
- Job has been stopped successfully.
Code: Select all
[15.04.2023 11:23:18.487] <01> Info Expanding policies ('0' objects)
[15.04.2023 11:23:18.487] <01> Info Retrieved 2 hierarchy objects, 0 SCVMM(s), 0 Cluster(s), 0 Host(s), 2 Virtual Machine(s), 0 Volume(s)
[15.04.2023 11:23:18.503] <01> Info Removing excluded VMs
[15.04.2023 11:23:18.519] <01> Info Creating plain list of tasks:
[15.04.2023 11:23:18.566] <01> Info [SharedSnapshotHolder] Printing shared snapshot contexts
[15.04.2023 11:23:18.566] <01> Info Created task order:
[15.04.2023 11:23:18.566] <01> Info Licensing hosts from all backup tasks
[15.04.2023 11:23:18.582] <01> Info
[15.04.2023 11:23:18.598] <01> Info Job has been stopped successfully. Name: [tsfionia_2023-04-15T112308], JobId: [ec722dde-0c17-4fb7-8f4b-2ce7a469c290]