public:module:vmware:requirements
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
public:module:vmware:requirements [2019/09/19 15:07] ronnie.chan |
public:module:vmware:requirements [2022/05/12 13:33] (current) klim [Granular Restore] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Requirements ======= | ====== Requirements ======= | ||
| Below are the requirements that you need to consider for properly backing up your VMware's virtual machines with CloudBacko Pro backup software. | Below are the requirements that you need to consider for properly backing up your VMware's virtual machines with CloudBacko Pro backup software. | ||
| + | ---- | ||
| - | ===== 1). Antivirus Exclusion ===== | + | ===== Antivirus Exclusion ===== |
| ---- | ---- | ||
| To optimize performance of CloudBacko Pro on Windows, and to avoid conflict with your antivirus software, refer to the following article the list of processes and directory paths that should be added to all antivirus software white-list / exclusion list. | To optimize performance of CloudBacko Pro on Windows, and to avoid conflict with your antivirus software, refer to the following article the list of processes and directory paths that should be added to all antivirus software white-list / exclusion list. | ||
| - | ===== 2). VMware vCenter / ESXi Server ===== | + | \\ |
| + | ===== VMware vCenter / ESXi Server ===== | ||
| ---- | ---- | ||
| Line 16: | Line 16: | ||
| <WRAP indent> | <WRAP indent> | ||
| ==== ESXi / vCenter Patch Release ==== | ==== ESXi / vCenter Patch Release ==== | ||
| - | |||
| ---- | ---- | ||
| Line 22: | Line 21: | ||
| ==== ESXi Shell Access ==== | ==== ESXi Shell Access ==== | ||
| - | |||
| ---- | ---- | ||
| Line 29: | Line 27: | ||
| ==== SSH ==== | ==== SSH ==== | ||
| - | |||
| ---- | ---- | ||
| Line 35: | Line 32: | ||
| ==== Root Account ==== | ==== Root Account ==== | ||
| - | |||
| ---- | ---- | ||
| Line 41: | Line 37: | ||
| ==== Port Requirement ==== | ==== Port Requirement ==== | ||
| - | |||
| ---- | ---- | ||
| * For environment with firewall, the vCenter, ESXi servers and Backup Client Computer must be able to communicate with each other. | * For environment with firewall, the vCenter, ESXi servers and Backup Client Computer must be able to communicate with each other. | ||
| - | * Ensure that ports 22, 80, 111, 443 and 902 allow outbound communication on the vCenter and ESXi servers. Refer to the link below for details on port usage: \\ [[https://kb.vmware.com/s/article/2012773]] \\ [[https://kb.vmware.com/s/article/2106283]] \\ [[https://kb.vmware.com/s/article/2039095]] \\ [[https://kb.vmware.com/s/article/2131180 | + | * Ensure that ports 22, 80, 111, 443 and 902 allow outbound communication on the vCenter and ESXi servers. Refer to the link below for details on port usage: \\ [[https://kb.vmware.com/s/article/2012773]] \\ [[https://kb.vmware.com/s/article/2106283]] \\ [[https://kb.vmware.com/s/article/2039095]] \\ [[https://kb.vmware.com/s/article/2131180]] |
| - | <WRAP info> | + | <WRAP info> 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. |
| - | 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. | + | |
| </WRAP> | </WRAP> | ||
| + | |||
| ==== Disk Space Available on Datastore ==== | ==== Disk Space Available on Datastore ==== | ||
| - | |||
| ---- | ---- | ||
| Line 58: | Line 51: | ||
| ==== Maximum Virtual Disk Size ==== | ==== Maximum Virtual Disk Size ==== | ||
| - | |||
| ---- | ---- | ||
| Line 65: | Line 57: | ||
| ==== VMware Tools ==== | ==== VMware Tools ==== | ||
| - | |||
| ---- | ---- | ||
| Line 75: | Line 66: | ||
| ==== ESXi/ESX Hosts and Virtual Machine Hardware Versions Compatibility ==== | ==== ESXi/ESX Hosts and Virtual Machine Hardware Versions Compatibility ==== | ||
| - | |||
| ---- | ---- | ||
| Line 81: | Line 71: | ||
| </WRAP> | </WRAP> | ||
| - | \\ \\ | + | \\ |
| - | + | ===== Backup Client Computer ===== | |
| - | ===== 3). Backup Client Computer ===== | + | |
| ---- | ---- | ||
| Line 102: | Line 91: | ||
| <WRAP indent> | <WRAP indent> | ||
| ==== Hardware and Software Requirement ==== | ==== Hardware and Software Requirement ==== | ||
| - | |||
| ---- | ---- | ||
| Line 108: | Line 96: | ||
| ==== Add-on Module Requirement ==== | ==== Add-on Module Requirement ==== | ||
| - | |||
| ---- | ---- | ||
| Line 114: | Line 101: | ||
| ==== Port Requirement ==== | ==== Port Requirement ==== | ||
| - | |||
| ---- | ---- | ||
| * For environment with firewall, the vCenter, ESXi hosts and Backup Client Computer must be able to communicate with each other. | * For environment with firewall, the vCenter, ESXi hosts and Backup Client Computer must be able to communicate with each other. | ||
| * Make sure that ports 22, 80, 111, 443 and 902 allow outbound communication on the Backup Client Computer. Refer to the link below for details on port usage: \\ [[https://kb.vmware.com/s/article/2012773]] \\ [[https://kb.vmware.com/s/article/2106283]] \\ [[https://kb.vmware.com/s/article/2039095]] \\ [[https://kb.vmware.com/s/article/2131180]] | * Make sure that ports 22, 80, 111, 443 and 902 allow outbound communication on the Backup Client Computer. Refer to the link below for details on port usage: \\ [[https://kb.vmware.com/s/article/2012773]] \\ [[https://kb.vmware.com/s/article/2106283]] \\ [[https://kb.vmware.com/s/article/2039095]] \\ [[https://kb.vmware.com/s/article/2131180]] | ||
| + | |||
| <WRAP info> | <WRAP info> | ||
| 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. | 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. | ||
| Line 124: | Line 111: | ||
| ==== Backup Client Computer on Linux ==== | ==== Backup Client Computer on Linux ==== | ||
| - | |||
| ---- | ---- | ||
| Line 131: | Line 117: | ||
| ==== Disk Space Available on Backup Client Computer (or the vCenter computer) ==== | ==== Disk Space Available on Backup Client Computer (or the vCenter computer) ==== | ||
| - | |||
| ---- | ---- | ||
| Line 139: | Line 124: | ||
| </code> | </code> | ||
| </WRAP> | </WRAP> | ||
| + | |||
| <WRAP info>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.</WRAP> | <WRAP info>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.</WRAP> | ||
| ==== Windows OS Requirement for VDDK and Non-VDDK Modes Backup ==== | ==== Windows OS Requirement for VDDK and Non-VDDK Modes Backup ==== | ||
| - | |||
| ---- | ---- | ||
| Line 151: | Line 136: | ||
| </WRAP> | </WRAP> | ||
| - | \\ \\ | + | \\ |
| - | + | ===== Run Direct ===== | |
| - | ===== 4). Run Direct ===== | + | |
| ---- | ---- | ||
| Line 161: | Line 144: | ||
| <WRAP indent> | <WRAP indent> | ||
| ==== VDDK Backup Mode ==== | ==== VDDK Backup Mode ==== | ||
| - | |||
| ---- | ---- | ||
| Line 168: | Line 150: | ||
| <WRAP indent> | <WRAP indent> | ||
| === VDDK Backup Mode Requirements === | === VDDK Backup Mode Requirements === | ||
| - | |||
| ---- | ---- | ||
| Line 183: | Line 164: | ||
| == License Requirement == | == License Requirement == | ||
| - | |||
| ---- | ---- | ||
| Line 189: | Line 169: | ||
| * Ensure that the license requirement is met. | * Ensure that the license requirement is met. | ||
| + | |||
| <WRAP info> | <WRAP info> | ||
| For VM on free version of ESXi without a Run Direct backup destination, backup will be performed in non-VDDK mode. \\ For VM on free version of ESXi with a Run Direct backup destination, the following error message would be returned during a backup: \\ | For VM on free version of ESXi without a Run Direct backup destination, backup will be performed in non-VDDK mode. \\ For VM on free version of ESXi with a Run Direct backup destination, the following error message would be returned during a backup: \\ | ||
| Line 204: | Line 185: | ||
| * The virtual disk must be located on a VMFS volume backed by SAN, iSCSI, local disk, or a NFS volume. | * The virtual disk must be located on a VMFS volume backed by SAN, iSCSI, local disk, or a NFS volume. | ||
| + | |||
| <WRAP info> | <WRAP info> | ||
| For virtual disk on VMFS, the initial backup (e.g. full file backup) will be of size similar to used size; while for virtual disk on NFS, the initial backup will be of the provisioned size. | For virtual disk on VMFS, the initial backup (e.g. full file backup) will be of size similar to used size; while for virtual disk on NFS, the initial backup will be of the provisioned size. | ||
| </WRAP> | </WRAP> | ||
| + | |||
| * RDM (Raw Device Mapping) in physical compatibility mode is not supported. | * RDM (Raw Device Mapping) in physical compatibility mode is not supported. | ||
| * The virtual disk must not be in Independent Mode (Persistent or Nonpersistent). | * The virtual disk must not be in Independent Mode (Persistent or Nonpersistent). | ||
| + | |||
| <WRAP info> | <WRAP info> | ||
| Once the backup job executed on a VM with change block tracking option enabled by the VDDK, please do not turn off this option in the VM for consequent backup jobs. If you need to disable this option, you are suggested to create a new backup set with this option disabled. | Once the backup job executed on a VM with change block tracking option enabled by the VDDK, please do not turn off this option in the VM for consequent backup jobs. If you need to disable this option, you are suggested to create a new backup set with this option disabled. | ||
| Line 215: | Line 199: | ||
| == VMware Snapshot == | == VMware Snapshot == | ||
| - | |||
| ---- | ---- | ||
| Line 223: | Line 206: | ||
| == Virtual Machine State == | == Virtual Machine State == | ||
| - | |||
| ---- | ---- | ||
| Line 229: | Line 211: | ||
| == File Name Requirement == | == File Name Requirement == | ||
| - | |||
| ---- | ---- | ||
| Line 242: | Line 223: | ||
| ==== Backup Destination ==== | ==== Backup Destination ==== | ||
| - | |||
| ---- | ---- | ||
| Line 263: | Line 243: | ||
| * **Dedicated NFS Service** - A dedicated CloudBacko Pro NFS Windows service is introduced to allow Run Direct session to continue even if the CloudBacko Pro user interface is closed. \\ \\ By default, the CloudBacko Pro NFS service is started as Local System, which does not have sufficient permission to access any network resources (e.g. the CloudBacko Pro NFS service does not have sufficient permission to access the VM backup files on network drive). \\ \\ Make sure that the Log on setting of the CloudBacko Pro NFS Service is configured with an account with sufficient permission to access the network backup destination where the backed up VM data are stored. | * **Dedicated NFS Service** - A dedicated CloudBacko Pro NFS Windows service is introduced to allow Run Direct session to continue even if the CloudBacko Pro user interface is closed. \\ \\ By default, the CloudBacko Pro NFS service is started as Local System, which does not have sufficient permission to access any network resources (e.g. the CloudBacko Pro NFS service does not have sufficient permission to access the VM backup files on network drive). \\ \\ Make sure that the Log on setting of the CloudBacko Pro NFS Service is configured with an account with sufficient permission to access the network backup destination where the backed up VM data are stored. | ||
| + | |||
| <WRAP indent><WRAP indent> | <WRAP indent><WRAP indent> | ||
| - Under Control Panel, open Administrative Tools then Services. | - Under Control Panel, open Administrative Tools then Services. | ||
| Line 269: | Line 250: | ||
| - Enter the login credentials of an account with sufficient permission. | - Enter the login credentials of an account with sufficient permission. | ||
| - Restart the service afterward. | - Restart the service afterward. | ||
| - | </WRAP></WRAP> | + | </WRAP> |
| - | + | </WRAP> | |
| - | ===== 5). Non-VDDK Backup Mode ==== | + | </WRAP> |
| + | </WRAP> | ||
| + | \\ | ||
| + | ===== Non-VDDK Backup Mode ==== | ||
| ---- | ---- | ||
| + | No longer supported in CloudBacko v5 | ||
| + | |||
| + | <HTML> | ||
| + | <BR> | ||
| + | <!-- | ||
| For VM that cannot be backed up in VDDK mode, non-VDDK backup mode will be used instead. | For VM that cannot be backed up in VDDK mode, non-VDDK backup mode will be used instead. | ||
| Line 281: | Line 270: | ||
| * Independent disk can only be backed up if the VM is shutdown during a backup. If the VM is started up during the backup, all independent disks selected for backup cannot be backed up. | * Independent disk can only be backed up if the VM is shutdown during a backup. If the VM is started up during the backup, all independent disks selected for backup cannot be backed up. | ||
| - | + | \\ | |
| - | ===== 6). Granular Restore ===== | + | --> |
| + | </HTML> | ||
| + | ===== Granular Restore ===== | ||
| ---- | ---- | ||
| <WRAP indent> | <WRAP indent> | ||
| ==== Supported Backup Modules ==== | ==== Supported Backup Modules ==== | ||
| - | |||
| ---- | ---- | ||
| Line 294: | Line 283: | ||
| ==== Backup Quota Storage ==== | ==== Backup Quota Storage ==== | ||
| - | |||
| ---- | ---- | ||
| Line 300: | Line 288: | ||
| ==== Operating System ==== | ==== Operating System ==== | ||
| - | |||
| ---- | ---- | ||
| CloudBacko Pro must be installed on a 64 bit Windows machine as libraries for Granular only supports 64 bit Windows operating system for VMware ESXi/vCenter. CloudBacko Pro must be installed on the following Windows Operating Systems: | CloudBacko Pro must be installed on a 64 bit Windows machine as libraries for Granular only supports 64 bit Windows operating system for VMware ESXi/vCenter. CloudBacko Pro must be installed on the following Windows Operating Systems: | ||
| + | | Windows 7 SP1 or higher OS | | ||
| + | | Windows 2008 R2 SP1 or higher Windows Server OS | | ||
| + | |||
| + | <HTML><!-- | ||
| | Windows 2008 R2 SP1 or above | Windows 2012 | Windows 2012 R2 | | | Windows 2008 R2 SP1 or above | Windows 2012 | Windows 2012 R2 | | ||
| | Windows 2016 | Windows 7 SP1 or above | Windows 8 | | | Windows 2016 | Windows 7 SP1 or above | Windows 8 | | ||
| | Windows 8.1 | Windows 10 | | | | Windows 8.1 | Windows 10 | | | ||
| + | --></HTML> | ||
| ==== Temporary Directory Requirement ==== | ==== Temporary Directory Requirement ==== | ||
| - | |||
| ---- | ---- | ||
| Line 315: | Line 306: | ||
| ==== Available Spare Drive Letter ==== | ==== Available Spare Drive Letter ==== | ||
| - | |||
| ---- | ---- | ||
| Line 323: | Line 313: | ||
| ==== Network Requirements ==== | ==== Network Requirements ==== | ||
| - | |||
| ---- | ---- | ||
| Line 331: | Line 320: | ||
| You can use an online network speed test website (e.g. [[http://www.speedtest.net]]) to get an idea of the actual bandwidth of the machine. | You can use an online network speed test website (e.g. [[http://www.speedtest.net]]) to get an idea of the actual bandwidth of the machine. | ||
| - | |||
| ==== Other Dependencies ==== | ==== Other Dependencies ==== | ||
| Line 344: | Line 332: | ||
| ==== Permissions ==== | ==== Permissions ==== | ||
| - | |||
| ---- | ---- | ||
public/module/vmware/requirements.1568876824.txt.gz · Last modified: 2019/09/19 15:07 by ronnie.chan
Page Tools
