public:vmware
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:vmware [2019/08/21 15:21] ronnie.chan |
public:vmware [2019/08/21 15:35] ronnie.chan [Backup Client Computer Requirements] |
||
|---|---|---|---|
| Line 64: | Line 64: | ||
| The NFS datastore is dismounted. | The NFS datastore is dismounted. | ||
| - | <WRAP prewrap> | + | <WRAP info> |
| - | <code> | + | |
| - | NOTE | + | |
| For vCenter VM backup set, provided that the vMotion feature of the vCenter set is working properly, the VM will not be suspended during the data consolidation. | For vCenter VM backup set, provided that the vMotion feature of the vCenter set is working properly, the VM will not be suspended during the data consolidation. | ||
| - | </code> | ||
| </WRAP> | </WRAP> | ||
| Line 148: | Line 145: | ||
| [[https://kb.vmware.com/s/article/2131180]] | [[https://kb.vmware.com/s/article/2131180]] | ||
| - | <WRAP prewrap> | + | <WRAP info> |
| - | <code> | + | |
| - | NOTE | + | |
| Ports 443 and 902 are default ports for VMware. | Ports 443 and 902 are default ports for VMware. | ||
| If these have been changed from the default in your VMware environment, the firewall requirements will change accordingly. | If these have been changed from the default in your VMware environment, the firewall requirements will change accordingly. | ||
| - | </code> | ||
| </WRAP> | </WRAP> | ||
| Line 165: | Line 159: | ||
| VMware Tools are used to quiesce VMs prior to backing them up. To create consistent backup for your VMs on Windows platforms, ensure that VMware Tools are installed, and up-to-date on all VMs to be backup. | VMware Tools are used to quiesce VMs prior to backing them up. To create consistent backup for your VMs on Windows platforms, ensure that VMware Tools are installed, and up-to-date on all VMs to be backup. | ||
| - | <WRAP prewrap> | + | <WRAP info> |
| - | <code> | + | |
| - | NOTE | + | |
| Quiescing is a process that ensures that the disk data is in a state suitable for backups to reduce the possibility of data corruption upon restore. This is especially important for transactional-based applications running on VMs like MS SQL Server. | Quiescing is a process that ensures that the disk data is in a state suitable for backups to reduce the possibility of data corruption upon restore. This is especially important for transactional-based applications running on VMs like MS SQL Server. | ||
| There are different types of quiescing mechanisms, according to the guest operating systems (e.g. Crash-consistent, File-system-consistent and Application-consist quiescing). | There are different types of quiescing mechanisms, according to the guest operating systems (e.g. Crash-consistent, File-system-consistent and Application-consist quiescing). | ||
| - | </code> | ||
| </WRAP> | </WRAP> | ||
| Line 206: | Line 197: | ||
| * To optimize performance of AhsayOBM on Windows, and to avoid conflict with your antivirus software, refer to [[public:8014_faq:suggestion_on_antivirus_exclusions|this article]] for the list of processes and directory paths that should be added to all antivirus software white-list / exclusion list. | * To optimize performance of AhsayOBM on Windows, and to avoid conflict with your antivirus software, refer to [[public:8014_faq:suggestion_on_antivirus_exclusions|this article]] for the list of processes and directory paths that should be added to all antivirus software white-list / exclusion list. | ||
| - | <WRAP prewrap> | + | <WRAP info> |
| - | <code> | + | |
| - | NOTE | + | |
| For AhsayOBM version 8.1 or above, the bJW.exe process is automatically added to Windows Defender exclusion list for Windows 10 and 2016, during installation / upgrade via installer or upgrade via AUA. | For AhsayOBM version 8.1 or above, the bJW.exe process is automatically added to Windows Defender exclusion list for Windows 10 and 2016, during installation / upgrade via installer or upgrade via AUA. | ||
| - | </code> | ||
| </WRAP> | </WRAP> | ||
| Line 222: | Line 210: | ||
| [[https://kb.vmware.com/s/article/2131180]] | [[https://kb.vmware.com/s/article/2131180]] | ||
| - | <WRAP prewrap> | + | <WRAP info> |
| - | <code> | + | |
| - | NOTE | + | |
| Ports 443 and 902 are default ports for VMware. | Ports 443 and 902 are default ports for VMware. | ||
| If these have been changed from the default in your VMware environment, the firewall requirements will change accordingly. | If these have been changed from the default in your VMware environment, the firewall requirements will change accordingly. | ||
| - | </code> | ||
| </WRAP> | </WRAP> | ||
| Line 233: | Line 218: | ||
| For Backup Client Computer running on Linux operating system platform, Graphical User Interface (GUI) environment (e.g. GOME or KDE) must be installed. | For Backup Client Computer running on Linux operating system platform, Graphical User Interface (GUI) environment (e.g. GOME or KDE) must be installed. | ||
| - | <WRAP prewrap> | + | <WRAP important> |
| - | <code> | + | |
| - | IMPORTANT | + | |
| Run Direct restore, VDDK backup mode and Granular Restore is not supported for Backup Client Computer on Linux / Mac OS X platforms. | Run Direct restore, VDDK backup mode and Granular Restore is not supported for Backup Client Computer on Linux / Mac OS X platforms. | ||
| - | </code> | ||
| </WRAP> | </WRAP> | ||
| Line 245: | Line 227: | ||
| **(Total File Size * Delta Ratio) * number of backup destinations = Maximum Free Space Required** | **(Total File Size * Delta Ratio) * number of backup destinations = Maximum Free Space Required** | ||
| - | <WRAP prewrap> | + | <WRAP info> |
| - | <code> | + | |
| - | NOTE | + | |
| The calculation is based on the current guest VM size, and it does not take into account guest VM growth over time. It is recommended for fast growing guest VM the maximum free space required should be reviewed on a regular basis to avoid potential backup problems. | The calculation is based on the current guest VM size, and it does not take into account guest VM growth over time. It is recommended for fast growing guest VM the maximum free space required should be reviewed on a regular basis to avoid potential backup problems. | ||
| - | </code> | ||
| </WRAP> | </WRAP> | ||
| Line 403: | Line 382: | ||
| ===== Granular Restore Technology ===== | ===== Granular Restore Technology ===== | ||
| - | AhsayOBM granular restore technology enables the recovery of individual files from a guest VM without booting up or restoring the whole guest VM first. See [[public:granular_restore#what_is_granular_restore_technology|here]] for details. | + | AhsayOBM [[public:granular_restore|granular restore technology]] enables the recovery of individual files from a guest VM without booting up or restoring the whole guest VM first. [[public:granular_restore|Click here]] to read the details. |
| - | <WRAP prewrap> | + | <WRAP important> |
| - | <code> | + | |
| - | IMPORTANT | + | |
| Granular Restore requires an additional OpenDirect / Granular Restore add-on module license to work. Contact your backup service provider for further details. | Granular Restore requires an additional OpenDirect / Granular Restore add-on module license to work. Contact your backup service provider for further details. | ||
| - | </code> | ||
| </WRAP> | </WRAP> | ||
public/vmware.txt · Last modified: 2022/11/28 11:11 by kirk.lim