public:features:cbt-bug-identification-check:home
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
public:features:cbt-bug-identification-check:home [2020/10/08 14:12] ronnie.chan |
public:features:cbt-bug-identification-check:home [2020/10/08 14:46] ronnie.chan |
||
|---|---|---|---|
| Line 10: | Line 10: | ||
| * VMware vCenter/ESXi v6.0 | * VMware vCenter/ESXi v6.0 | ||
| - | This known VMware CBT bug can sometimes return incorrect changed sectors on a guest virtual machine during a VMware backup. As the CBT is used by the AhsayOBM for VDDK backup modes, it affects the integrity of both incremental and differential backups. | + | This known VMware CBT bug can sometimes return incorrect changed sectors on a guest virtual machine during a VMware backup. As the CBT is used by the CloudBacko Pro for VDDK backup modes, it affects the integrity of both incremental and differential backups. |
| <WRAP info> | <WRAP info> | ||
| Line 21: | Line 21: | ||
| As part of the backup job, CloudBacko Pro v4.1.4 (or above) will check the current VMware version to identify if it is affected by the CBT bug. If the VMware version detected is related to the affected version (i.e. v5.0, v5.1, v5.5 and v6.0), then CloudBacko Pro will show a warning in the Backup Report indicating that the VMware host is affected by the CBT bug. | As part of the backup job, CloudBacko Pro v4.1.4 (or above) will check the current VMware version to identify if it is affected by the CBT bug. If the VMware version detected is related to the affected version (i.e. v5.0, v5.1, v5.5 and v6.0), then CloudBacko Pro will show a warning in the Backup Report indicating that the VMware host is affected by the CBT bug. | ||
| - | ===== Backup Report Sample for a VMware ESXi 5.1.0 host with the affected version ===== | + | ===== Backup Report Sample ===== |
| + | |||
| + | Below is a sample of backup report for a VMware ESXi 5.1.0 host with the affected version: | ||
| {{public:features:cbt-bug-identification-check:cbt-bug-01a.png}} | {{public:features:cbt-bug-identification-check:cbt-bug-01a.png}} | ||
| Line 39: | Line 41: | ||
| <WRAP info> | <WRAP info> | ||
| - | Although CloudBacko v4 (or above) no longer supports the creation of new VMware backup set for VMware vCenter/ESXi v5.0 and v5.1, however, backup sets which are upgraded from the previous versions are still supported with the following workaround: | + | ==== Workaround for vCenter/ESXi v5.0 and v5.1 ==== |
| - | - Download the VDDK v6 API files from here: [https://download.ahsay.com/support/vddk6.zip] | + | Although CloudBacko v4 (or above) no longer supports the creation of new VMware backup set for VMware vCenter/ESXi v5.0 and v5.1, backup sets which are upgraded from the previous versions are still supported with the following workaround: |
| - | + | ||
| - | Stop the AhsayOBM services. | + | |
| - | + | ||
| - | Stop the AhsayOBM NFS service. | + | |
| - | + | ||
| - | Make a copy of the current folder %OBM_INSTALL%\bin\x64. | + | |
| - | + | ||
| - | Using Windows Explorer open folder %OBM_INSTALL%\bin\x64. | + | |
| - | + | ||
| - | Delete the following 13 .dll files from the %OBM_INSTALL%\bin\x64 folder. | + | |
| - | diskLibPlugin.dll | + | |
| - | libexpat.dll | + | |
| - | lookup-types.dll | + | |
| - | msvcp120.dll | + | |
| - | msvcr120.dll | + | |
| - | pcre.dll | + | |
| - | sqlite3.dll | + | |
| - | ssoclient.dll | + | |
| - | vddkVimAccess.dll | + | |
| - | vim-types.dll | + | |
| - | vmacore.dll | + | |
| - | vmomi.dll | + | |
| - | zlib1.dll | + | |
| - | Unzip the downloaded vddk.zip file and copy the contents %OBM_INSTALL%\bin\x64 folder. | + | |
| - | + | ||
| - | Start the AhsayOBM services. | + | |
| - | + | ||
| - | Start the AhsayOBM NFS service. | + | |
| + | - Download the VDDK v6 API files from here: https://download.ahsay.com/support/vddk6.zip | ||
| + | - Stop the AhsayOBM services. | ||
| + | - Stop the AhsayOBM NFS service. | ||
| + | - Make a copy of the current folder %OBM_INSTALL%\bin\x64. | ||
| + | - Using Windows Explorer open folder %OBM_INSTALL%\bin\x64. | ||
| + | - Delete the following 13 .dll files from the %OBM_INSTALL%\bin\x64 folder. | ||
| + | * diskLibPlugin.dll | ||
| + | * libexpat.dll | ||
| + | * lookup-types.dll | ||
| + | * msvcp120.dll | ||
| + | * msvcr120.dll | ||
| + | * pcre.dll | ||
| + | * sqlite3.dll | ||
| + | * ssoclient.dll | ||
| + | * vddkVimAccess.dll | ||
| + | * vim-types.dll | ||
| + | * vmacore.dll | ||
| + | * vmomi.dll | ||
| + | * zlib1.dll | ||
| + | - Unzip the downloaded vddk.zip file and copy the contents %OBM_INSTALL%\bin\x64 folder. | ||
| + | - Start the AhsayOBM services. | ||
| + | - Start the AhsayOBM NFS service. | ||
| + | </WRAP> | ||
| + | <WRAP info> | ||
| + | ==== List of VDDK 6 API files ==== | ||
| + | * glib-2.0.dll | ||
| + | * gobject-2.0.dll | ||
| + | * gthread-2.0.dll | ||
| + | * gvmomi.dll | ||
| + | * iconv.dll | ||
| + | * intl.dll | ||
| + | * libcurl.dll | ||
| + | * libeay32.dll | ||
| + | * liblber.dll | ||
| + | * libldap.dll | ||
| + | * libldap_r.dll | ||
| + | * libxml2.dll | ||
| + | * ssleay32.dll | ||
| + | * VddkJNI.dll | ||
| + | * vixDiskLib.dll | ||
| + | * vixDiskLibVim.dll | ||
| + | * vixMntapi.dll | ||
| </WRAP> | </WRAP> | ||
public/features/cbt-bug-identification-check/home.txt · Last modified: 2020/10/08 14:55 by ronnie.chan
Page Tools
