We are now using 12.2 and are using this new function. It is better to have it, but it is still far from satisfactory.
Last night we had the situation again where a backup job with hardware snapshots did not start due to a vcenter snapshot for all VMs. At least all VMs were processed after the default wait time. The VM with the snapshot was marked with fail and then tried several times with the same method, which of course did not work. Why is there not a failback to no hardware snapshot support (e.g. nbd or whatever). So I have to keep intervening, change the job manually and send another retry. Every day until the customer has deleted his authorized snapshot.
I still see an urgent need for action here and would like the last missing step to be implemented as soon as possible.
Last night we had the situation again where a backup job with hardware snapshots did not start due to a vcenter snapshot for all VMs. At least all VMs were processed after the default wait time. The VM with the snapshot was marked with fail and then tried several times with the same method, which of course did not work. Why is there not a failback to no hardware snapshot support (e.g. nbd or whatever). So I have to keep intervening, change the job manually and send another retry. Every day until the customer has deleted his authorized snapshot.
I still see an urgent need for action here and would like the last missing step to be implemented as soon as possible.
Statistics: Posted by Spex — Sep 20, 2024 9:52 am