Some additional information....
Our QA teams have tested this behavior twice and can confirm that powering off a VM, performing a vMotion or suspending a vm helps to prevent corruption during backup or replica jobs.
In vSphere 8.0 Update 2, to optimize the open and close process of virtual disks during hot extension, the disk remains open during hot extend operations. Due to this change, incremental backup of virtual disks with CBT enabled might be incomplete, because the CBT in-memory bitmap does not resize, and CBT cannot record the changes to the extended disk block. As a result, when you try to restore a VM from an incremental backup of virtual disks with CBT, the VM might fail to start.
Therefore, our QA team's initial recommendations were indeed valid. However, it's important to note that the term 'CBT reset' is misleading. The root cause of corruption was attributed to another factor, not CBT itself. Instead, the issue stemmed from a separate entity operating within the process, and resetting the process identifier effectively resolved the problem.
Our QA teams have tested this behavior twice and can confirm that powering off a VM, performing a vMotion or suspending a vm helps to prevent corruption during backup or replica jobs.
In vSphere 8.0 Update 2, to optimize the open and close process of virtual disks during hot extension, the disk remains open during hot extend operations. Due to this change, incremental backup of virtual disks with CBT enabled might be incomplete, because the CBT in-memory bitmap does not resize, and CBT cannot record the changes to the extended disk block. As a result, when you try to restore a VM from an incremental backup of virtual disks with CBT, the VM might fail to start.
Therefore, our QA team's initial recommendations were indeed valid. However, it's important to note that the term 'CBT reset' is misleading. The root cause of corruption was attributed to another factor, not CBT itself. Instead, the issue stemmed from a separate entity operating within the process, and resetting the process identifier effectively resolved the problem.
Statistics: Posted by Sturniolo — Mar 26, 2024 8:29 pm