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)
Accelerator forced rescan for virtual machines (schedule attribute)
The accelerator for virtual machines uses Changed Block Tracking (CBT) technology from VMware to identify changed blocks. NetBackup requires the changed blocks when it creates a full virtual machine (synthesized) image. NetBackup is therefore dependent on VMware CBT for correctly identifying changed blocks. To protect against any potential omissions by underlying VMware CBT using timestamps, the
option conducts the backup by collecting all in-use blocks as reported by VMware CBT.When Accelerator forced rescan is used, all the data on the virtual machine is backed up. This backup is similar to the first Accelerator backup for a policy. For the forced rescan job, the optimization percentage for Accelerator is 0. The duration of the backup is similar to a non-Accelerator full backup.
Note:
Under normal operations, an Accelerator forced rescan schedule is not necessary for VMware backups. It can be used to enforce a new baseline backup in case VMware CBT issues are discovered. Engaging with Veritas Support is recommended in such situations.
Accelerator forced rescan is unavailable if the option on the Attributes tab is not selected.