public:announcement:ahsay_upgrade_advisory_29475
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
public:announcement:ahsay_upgrade_advisory_29475 [2021/02/02 11:15] yuk.cheng |
public:announcement:ahsay_upgrade_advisory_29475 [2021/02/19 16:55] (current) edward.chan correct typo |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| ====== Ahsay Upgrade Advisory (#29475) - Critical Issue with AhsayOBM v7 & v8 VMware Workstation and VMware ESXi backup ====== | ====== Ahsay Upgrade Advisory (#29475) - Critical Issue with AhsayOBM v7 & v8 VMware Workstation and VMware ESXi backup ====== | ||
| - | We have recently confirmed a critical issue related to VMware virtual machine backups on **all VMware Workstation and some VMware ESXi backup sets**, which occurs when the guest VM is created with the VMDK file that are split into individual 2GB VMDK files. | + | We have recently confirmed a critical issue related to VMware virtual machine backups on **all VMware Workstation and some VMware ESXi backup sets**. |
| + | |||
| + | This issue only affects guest VMs created using the option **Split virtual disk into multiple files**, which causes the VMware host to create multiple VMDK files up to 2GB each as the guest VM grows. //Example setting for VMware Workstation 12.0// | ||
| + | |||
| + | {{:public:announcement:vm_workstation_01.png?direct&400|}} | ||
| Due to this bug, AhsayOBM is unable to fully retrieve the correct number of 2GB VMDK files for the guest VM, which causes the backup job to miss some of these 2GB VMDK files. Even though AhsayOBM reports the backup job is successful the guest VM is no longer recoverable. | Due to this bug, AhsayOBM is unable to fully retrieve the correct number of 2GB VMDK files for the guest VM, which causes the backup job to miss some of these 2GB VMDK files. Even though AhsayOBM reports the backup job is successful the guest VM is no longer recoverable. | ||
| Line 8: | Line 12: | ||
| ===== What are the affected AhsayOBM versions? ===== | ===== What are the affected AhsayOBM versions? ===== | ||
| * AhsayOBM v7.3.0.0 to v7.17.129 | * AhsayOBM v7.3.0.0 to v7.17.129 | ||
| - | * AhsayOBM v8.1.0.24 to 8.3.6.125 | + | * AhsayOBM v8.1.0.24 to v8.3.6.125 |
| - | ===== What are the affected VMware versions? ===== | + | ===== What are the potentially affected VMware versions? ===== |
| - | * VMware Workstation 10.x to 16.x | + | * VMware Workstation 10.x, 11.x, 12.x, 14.x, 15.x, and 16.x |
| * VMware ESXi 5.0 | * VMware ESXi 5.0 | ||
| + | |||
| + | ===== How do I identify the affected guest VMs? ===== | ||
| + | * To verify if the guest VM in your clients backup set is affected by this issue. Please check the guest VMs for the presence of multiple VMDK files, with file size up to 2GB on the VMware host, as highlighted in the following example | ||
| + | {{:public:announcement:vmwaredisks1-2gb-new.jpg?direct&650|}} | ||
| ===== What action do I need to take to fix this problem? ===== | ===== What action do I need to take to fix this problem? ===== | ||
public/announcement/ahsay_upgrade_advisory_29475.1612235713.txt.gz · Last modified: 2021/02/02 11:15 by yuk.cheng