NetBackup™ Web UI VMware Administrator's Guide
- Introducing the NetBackup web user interface
- Monitoring NetBackup
- Managing VMware servers
- Add VMware servers
- Validate and update VMware server credentials
- Browse VMware servers
- Remove VMware servers
- Create an intelligent VM group
- Remove an intelligent VM group
- Add a VMware access host
- Remove a VMware access host
- Change resource limits for VMware resource types
- Change the autodiscovery frequency of VMware assets
- Discover VMware server assets manually
- Protecting VMs
- Instant access
- Instant rollback
- Continuous data protection
- CDP terminology
- CDP Architecture
- About continuous data protection
- Prerequisites
- Capacity-based licensing for CDP
- Configuring CDP
- Defining the CDP gateway
- Sizing considerations
- Limiting concurrent CDP backup jobs
- Controlling full sync
- Monitoring CDP jobs
- Using accelerators with CDP
- Recovering CDP protected VMs
- Some limitations of CDP
- Troubleshooting for CDP
- VM recovery
- Troubleshooting VMware operations
- Errors when adding VMware servers
- Errors when browsing VMware servers
- Errors for the Status for a newly discovered VM
- Error when downloading files from an instant access VM
- Troubleshooting backups and restores of excluded virtual disks
- Restore fails for a virtual machine with multiple datastores
- Errors when you change the recovery destination
Using accelerators with CDP
CDP for VMware exclusively supports accelerator-based backup. So, CDP needs accelerator-compliant storage units based on MSDP or OST-based storage.
Force rescan enhances safety, and establishes a baseline for the next accelerator backup. This feature protects against any potential damage like failure of checksum verification on the data in the staging area.
When you use accelerator-based forced rescan, it clears the data on CDP gateway staging area. So, any corrupted data is replaced with fresh data synced from the ESXi server. Note that the first backup job triggered by forced rescan may not have all data needed for a recoverable image. As data becomes available, the subsequent backups are triggered automatically making the images recoverable.
Recommendations for using forced rescan:
Do not trigger force rescan for the VMs which are turned off.
If the staging location memory is full, you can see a notification in the UI. Initiate the force rescan only when sufficient memory is available at the staging location.
To manually trigger the backup with force rescan execute the following command in the command prompt or the Linux terminal:
bpbackup -i -p policyname -s <schedulename>
NetBackup creates a schedule named ForcedRescan for every protected VM.