NetBackup™ for VMware Administrator's Guide
- Introduction
- Required tasks: overview
- Configuring RBAC roles for VMware administrators
- Notes and prerequisites
- VMware vSphere privileges
- Managing VMware servers
- About VMware discovery
- Add VMware servers
- Change resource limits for VMware resource types
- Configuring backup policies for VMware
- Backup options on the VMware tab
- Exclude disks tab
- Configuring a VMware Intelligent Policy
- About the Reuse VM selection query results option
- Use Accelerator to back up virtual machines
- Configuring protection plans for VMware
- Malware scan
- Instant access
- Instant rollback
- Continuous data protection
- Backing up virtual machines
- VM recovery
- VMware agentless restore
- Restoring Individual files and folders from VMware backups
- Using NetBackup to back up Cloud Director environments
- Recover VMware Cloud Director virtual machines
- Restore virtual machines with Instant Recovery
- Protecting VMs using hardware snapshots and replication
- Best practices and more information
- Troubleshooting VMware operations
- NetBackup logging for VMware
- Snapshot error encountered (status code 156)
- Appendix A. Configuring services for NFS on Windows
- About configuring services for NFS on Windows 2012 or 2016 (NetBackup for VMware)
- Appendix B. Backups of VMware raw devices (RDM)
Sizing considerations
This section describes the CDP gateway's sizing requirements, based on your environment's workload.
Note:
If you plan to support a large number of VMs using the CDP gateway, deploy the CDP gateway and the MSDP or media server hosting the storage unit, on different hosts.
Note:
If the CDP gateway and MSDP are co-located on the same media server, then the CDP service consumes 20% of available memory (RAM) for its internal use. If the CDP gateway is standalone on the media server, it consumes 50% of the available memory for the same. From NetBackup version 10.0 onwards, you can configure this value in the UI.
You need to size the CDP based on the number of VMs that you want to protect. Consider the requirements described in this section, while calculating the requirements for the gateway.
CDP enables you to continuously tap the I/Os done by the VMs. NetBackup, by default, uses 10-GB storage space on the staging area per VM. When IO tapping starts, the CDP service starts writing the data into this 10-GB storage. Once this storage limit is reached, the CDP service (nbcctd) initiates a backup job to move this data from the gateway to the backup storage.
Out of the total available space on the CDP staging path, by default, NetBackup reserves 25% for usage beyond the allocated storage per VM. This storage is common for the subscribed VMs to the gateway. See Defining the CDP gateway . , for how to do it on version 10.0 onwards. You can reconfigure this value in the nbcct.conf
file in NetBackup 9.1.
To configure reserved storage in NetBackup 9.1
- Log on to the CDP gateway.
- Navigate to the
<staginglocation>/nbcct/
directory, and open thenbcct.conf
file in a text editor. - Enter the required values against the parameters CCT_VM_QUOTA_SIZE_IN_MB and CCT_VM_QUOTA_RESERVE_PERCENT
- Restart the nbcctd service.
Storage requirement for the gateway
When NetBackup receives the data from the ESXi IO daemon, it stores the data in the in-memory cache. Recommended is a minimum of 160 MB of data for each VM.
For example, you protect 40 VMs in a gateway. So, you need 40*160 MB = 6400-MB RAM. Allocating more RAM increases the in-memory cache size when the CDP service starts, ultimately increasing the IO performance of the service.
Similarly, to stage 40 * 10-GB = 400-GB (75%) + 134GB (25%) reserved, that is approximately 540-GB space you need to have in the staging area.
Increasing per-VM storage allows to NetBackup to back up more data per backup job. Increasing the reserved storage for the CDP gateway lets you receive more data without any interruption to the protection. Note that even when the staging path is fully occupied, it does not affect the applications inside the VM. NetBackup catches up the data produced by applications during that time, and moves it to the backup storage in the subsequent backup jobs.
Note:
If NFS is used for the staging area, the minimum required throughput is 100 MB/sec.
When you start using the CDP feature, it is important to observe the system and tune it according to your business demands. Add any required hardware configurations to maximize protection and performance. First, you can use default values and start subscribing the VMs according to the requirements mentioned in this section. You should check the following:
Number of immediate backup jobs that the CDP service initiates due to the staging storage in full condition.
You can check the CDP backup engine notifications on NetBackup web UI.
Underlying provisioned storage performance. Like the NetBackup installation disk, CDP staging area, and MSDP storage disks.
Network utilization and available bandwidth.
CPU and memory consumption when receiving data from the ESXi, and when the backup jobs are running.
Note:
If you observe slow I/Os from the I/O daemon, check network bandwidth and system RAM. See Defining the CDP gateway . , for how to increase the in-memory cache size in NetBackup 10.0 onwards. For NetBackup 9.1, you can do it using the CCT_POOL_SIZE_QUOTA_PERCENTAGE parameter in the nbcct.conf
file.