public:module:vmware:best_practices
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision Last revision Both sides next revision | ||
|
public:module:vmware:best_practices [2019/09/17 15:45] ronnie.chan created |
public:module:vmware:best_practices [2019/09/19 15:50] ronnie.chan |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| Please consider the following recommendations. | Please consider the following recommendations. | ||
| - | ---- | + | {{INLINETOC}} \\ |
| ===== Use the latest version of CloudBacko Pro ===== | ===== Use the latest version of CloudBacko Pro ===== | ||
| - | Install the latest version of CloudBacko Pro on the staging machine or Backup Client Computer for backup of VM hosted on a VMware ESX/ESXi server, or on the vCenter server. | ||
| - | Always stay up-to-date when newer version of AhsayOBM is released. To get our latest product and company news through email, please subscribe to our newsletter: https://www.ahsay.com/jsp/en/contact/ahsay-contact.jsp | + | ---- |
| + | |||
| + | Install the latest version of CloudBacko Pro on the staging machine or Backup Client Computer for backup of VM hosted on a VMware ESX/ESXi server, or on the vCenter server. | ||
| ===== Install CloudBacko Pro on a physical staging machine ===== | ===== Install CloudBacko Pro on a physical staging machine ===== | ||
| - | For best backup and restore performance, it is highly recommended that AhsayOBM is installed on a server grade staging machine or backup client computer with sufficient memory and processing power. As guest VM can be very large, during backups and restore this may involve the compression & encryption of large amounts of data, which can be very resource intensive. | + | For best backup and restore performance, it is highly recommended that CloudBacko Pro is installed on a server grade staging machine or backup client computer with sufficient memory and processing power. As guest VM can be very large, during backups and restore this may involve the compression & encryption of large amounts of data, which can be very resource intensive. |
| ===== VMware Tools ===== | ===== VMware Tools ===== | ||
| Line 18: | Line 20: | ||
| ===== Do not use a guest VM as a staging machine ===== | ===== Do not use a guest VM as a staging machine ===== | ||
| - | Although installing AhsayOBM on a guest VM as a staging machine is possible, the backup and restore will work as on a physical staging machine. This setup is actually inefficient and can lead to possible performance bottlenecks on the VMware host server, as in a VMware host the virtualization layer separates guest VM OS layer and the VMware host physical hardware layer. | + | Although installing CloudBacko Pro on a guest VM as a staging machine is possible, the backup and restore will work as on a physical staging machine. This setup is actually inefficient and can lead to possible performance bottlenecks on the VMware host server, as in a VMware host the virtualization layer separates guest VM OS layer and the VMware host physical hardware layer. |
| As the guest VM operating system does not have direct access to physical hardware where the data resides, a backup agent installed inside the guest VM must go through the virtualization layer to access the guest virtual machine data. | As the guest VM operating system does not have direct access to physical hardware where the data resides, a backup agent installed inside the guest VM must go through the virtualization layer to access the guest virtual machine data. | ||
| Line 41: | Line 43: | ||
| ===== Increase Java memory ===== | ===== Increase Java memory ===== | ||
| - | Consider to increase the Java memory allocation setting for AhsayOBM (Java heap space) if you are using non-VDDK backup mode. | + | Consider to increase the Java memory allocation setting for CloudBacko Pro (Java heap space) if you are using non-VDDK backup mode. |
| If you are using non-VDDK mode and or Granular restore, it is recommended to increase the Java heap size space to at least 2GB or above for optimal performance. | If you are using non-VDDK mode and or Granular restore, it is recommended to increase the Java heap size space to at least 2GB or above for optimal performance. | ||
public/module/vmware/best_practices.txt · Last modified: 2019/09/19 16:07 by ronnie.chan
Page Tools
