public:vmware
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
public:vmware [2019/08/16 15:43] ronnie.chan |
public:vmware [2019/08/16 15:51] ronnie.chan [Run Direct Requirements] |
||
|---|---|---|---|
| Line 265: | Line 265: | ||
| Run Direct is a feature that helps reduce disruption and downtime of your production VMs. To utilize the Run Direct feature, ensure that the following requirements are met: | Run Direct is a feature that helps reduce disruption and downtime of your production VMs. To utilize the Run Direct feature, ensure that the following requirements are met: | ||
| - | === VDDK Backup Mode Requirement === | + | === VDDK Backup Mode === |
| Run Direct restore is only supported for virtual machine that is backed up in VDDK mode (Virtual Disk Development Kit) for ESX/ESXi and vCenter setup. With VDDK mode, the backup speed is enhanced because the generation of the delta file of the VM are performed directly by the ESX/ESXi or vCenter itself. For being able to backup in VDDK mode, AhsayOBM must be installed on a supported Windows operating system platform. | Run Direct restore is only supported for virtual machine that is backed up in VDDK mode (Virtual Disk Development Kit) for ESX/ESXi and vCenter setup. With VDDK mode, the backup speed is enhanced because the generation of the delta file of the VM are performed directly by the ESX/ESXi or vCenter itself. For being able to backup in VDDK mode, AhsayOBM must be installed on a supported Windows operating system platform. | ||
| Line 306: | Line 306: | ||
| This is due to the percent-encoding specified in the URL standard is not supported for ESXi based HTTP(S) file access. To resolve the issue, please rename the corresponding file to avoid special characters. For instructions on renaming a virtual machine, please refer to the following knowledge base article from VMware: https://kb.vmware.com/s/article/2031763 | This is due to the percent-encoding specified in the URL standard is not supported for ESXi based HTTP(S) file access. To resolve the issue, please rename the corresponding file to avoid special characters. For instructions on renaming a virtual machine, please refer to the following knowledge base article from VMware: https://kb.vmware.com/s/article/2031763 | ||
| + | |||
| + | === Backup Destination === | ||
| + | When a Run Direct restore is performed, the backup destination containing the guest VM files is mounted on the VMware host as NFS datastore. | ||
| + | |||
| + | Ensure that the following requirements are met by the backup destination of the VMware VM backup set: | ||
| + | * Destination must be accessible to the VMware host. | ||
| + | * Destination must have sufficient disk space available for the Run Direct restore. There should be 1.5 x total provisioned size of all VMs selected for backup. | ||
| + | * For Run Direct restore of 1 VM with provisioned size of 100GB, there should be 150GB (e.g. 1.5 x 100GB) of free space available in the Destination. | ||
| + | |||
| + | No Compression and Encryption - Data backed up to a Run Direct enabled destination is not compressed or encrypted to optimize restore performance as Run Direct will make the VM restored by running the data directly form the backup files in the backup destination. | ||
| + | |||
| + | Operation System of the Backup Client Computer | ||
| + | * Run Direct restore is only supported by AhsayOBM installation on Windows. | ||
| + | * To utilize the Run Direct feature, make sure that AhsayOBM is installed on a supported Windows platform. | ||
| + | |||
| + | Restore to Alternate Location | ||
| + | * When performing a Run Direct restore to Alternate Location, only one VM can be selected per restore session. \\ {{public:ahsay_wiki_module_vmware_requirement_03.png?200}} \\ {{public:ahsay_wiki_module_vmware_requirement_04.png?640}} | ||
| + | |||
public/vmware.txt · Last modified: 2022/11/28 11:11 by kirk.lim