NetBackup™ for VMware Administrator's Guide
- Introduction
- About NetBackup for VMware
- About the virtual machine backups that include database data
- About the NetBackup appliance as a VMware backup host
- NetBackup for VMware components
- Appliance as backup host: component overview
- Media servers as backup or discovery hosts
- Overview of the VMware backup process
- NetBackup for VMware terminology
- Required tasks: overview
- Notes and prerequisites
- NetBackup for VMware prerequisites
- NetBackup for VMware: notes and restrictions
- Notes on VMware Virtual Volumes (VVols)
- NetBackup IPv6 parameter required for backups in VMware IPv6 environments
- NetBackup for VMware: notes on Linux virtual machines
- Notes on the NetBackup appliance as a VMware backup host
- NetBackup for VMware support for SAN multi-pathing
- NetBackup for VMware support for fault tolerant VMs
- NetBackup character restrictions for the Primary VM identifier
- In the policy Query Builder, display names, resource pool names, and vApp names are case-sensitive
- Notes on the hotadd transport mode
- Notes and limitations for tag usage in VMware Intelligent Policy queries
- Notes and limitations for the backup and restore of VMware tag associations
- Configure NetBackup communication with VMware
- Adding the VMware backup host to NetBackup
- Adding NetBackup credentials for VMware
- Changing the host name of a VMware server in NetBackup
- Setting privileges for posting events to vCenter
- Authentication token for the NetBackup vSphere plug-ins
- Setting global limits on the use of VMware resources
- Validating VMware virtualization server certificates in NetBackup
- ECA_TRUST_STORE_PATH for NetBackup servers and clients
- ECA_CRL_PATH for NetBackup servers and clients
- ECA_CRL_PATH_SYNC_HOURS for NetBackup servers and clients
- ECA_CRL_CHECK for NetBackup servers and clients
- VIRTUALIZATION_HOSTS_CONNECT_TIMEOUT for servers and clients
- VIRTUALIZATION_HOSTS_SECURE_CONNECT_ENABLED for servers and clients
- VIRTUALIZATION_CRL_CHECK for NetBackup servers and clients
- VMWARE_TLS_MINIMUM_V1_2 for NetBackup servers and clients
- Configure NetBackup policies for VMware
- Configuring a VMware policy from the Policy Wizard
- Configuring a VMware policy from the Policies utility
- Limit jobs per policy on the Attributes tab (for VMware)
- VMware backup host
- Optimizations options (VMware)
- Primary VM identifier options (VMware)
- Existing snapshot handling options (VMware)
- Transport modes options (VMware)
- Application protection options (VMware)
- VMware - Advanced Attributes dialog
- About the Post vCenter events option (VMware Advanced Attributes)
- Exclude Disks tab
- Browse for VMware virtual machines
- Limiting the VMware servers that NetBackup searches when browsing for virtual machines
- Virtual machine host names and display names should be unique if VMs are selected manually in the policy
- Primary VM identifier option and manual selection of virtual machines
- About incremental backups of virtual machines
- Configuring incremental backups
- Storage Foundation Volume Manager volumes in the virtual machine
- Configure a VMware Intelligent Policy
- About automatic virtual machine selection for NetBackup for VMware
- Support and use of VMware tag associations
- The basics of a NetBackup query rule
- Important notes on automatic virtual machine selection
- NetBackup requirements for automatic virtual machine selection
- Automatic virtual machine selection: Task overview
- Options for selecting VMware virtual machines
- Configuring automatic virtual machine selection
- Editing an existing query in Basic Mode
- Using the Query Builder in Advanced Mode
- AND vs. OR in queries
- Examples for the NetBackup Query Builder
- The IsSet operator in queries
- About selecting virtual machines by means of multiple policies
- Order of operations in queries (precedence rules)
- Parentheses in compound queries
- Query rules for resource pools
- Query rules for datacenter folders (host folder)
- Query rules for duplicate names
- Query rules for tags
- Query Builder field reference
- Test Query screen for VMware
- Test Query: Failed virtual machines
- Effect of Primary VM identifier parameter on Selection column in Test Query results
- Effect of Primary VM identifier parameter on VM Name column in Test query results
- Refreshing the display of virtual environment changes in the Query Builder
- Reducing the time required for VM discovery in a large VMware environment
- Reduce the size of backups
- Back up virtual machines
- Use Accelerator to back up virtual machines
- About the NetBackup Accelerator for virtual machines
- Accelerator: full vs. incremental schedules
- How the NetBackup Accelerator works with virtual machines
- Accelerator notes and requirements for virtual machines
- Accelerator forced rescan for virtual machines (schedule attribute)
- Accelerator requires the OptimizedImage attribute
- Accelerator backups and the NetBackup catalog
- Accelerator messages in the backup job details log
- NetBackup logs for Accelerator with virtual machines
- About reporting the amount of Accelerator backup data that was transferred over the network
- Replacing the Accelerator image size with the network-transferred data in NetBackup command output
- Restore virtual machines
- Restore notes and restrictions
- Restore notes and restrictions on Linux
- Restoring the full VMware virtual machine
- Virtual Machine Recovery dialog boxes (restore to original location)
- Virtual Machine Recovery dialogs boxes (restore to alternate location)
- Recovery Destination dialog box (restore to alternate location)
- Recovery Options dialog box (restore to alternate location)
- Select ESX server dialog box (restore to alternate location)
- Select Folder dialog box (restore to alternate location)
- Select Datastore or Datastore Cluster dialog box (restore to alternate location)
- Storage Destination dialog box (restore to alternate location)
- Network Connections and Other Recovery Options dialog box (restore to alternate location)
- Perform Recovery dialog box (restore to alternate location)
- About VMware virtual machine disk restore
- Restoring VMware virtual machine disks by using Backup, Archive, and Restore
- Restoring VMware virtual machine disks by using NetBackup commands
- Determining the backup image ID from which to restore a VMware virtual machine disk
- Creating the VMware virtual machine disk restore file
- Modifying the virtual machine disk restore file
- Validating the virtual machine disk restore file
- Restoring the virtual machine disk or disks by using the nbrestorevm command
- VMware virtual machine disk restore file
- About restoring individual VMware files
- Restoring individual VMware virtual machine files
- How NetBackup handles VMware tag associations at restore
- Browse and search virtual machines for restore
- If the recovery host is not at the same NetBackup release level as the backup host
- Restore virtual machines with Instant Recovery
- About Instant Recovery for VMware
- Task overview for Instant Recovery for VMware
- Performance recommendations for Instant Recovery for VMware
- Requirements for Instant Recovery for VMware
- Notes on Instant Recovery for VMware
- Restarting the Client for NFS service on a Windows restore host
- Instant Recovery options on the nbrestorevm command
- Restoring a virtual machine with Instant Recovery for VMware
- Restoring a virtual machine to a different location with Instant Recovery for VMware
- Restoring individual files with Instant Recovery for VMware while the current virtual machine is running
- Job types for Instant Recovery for VMware
- Reactivating a restored virtual machine with Instant Recovery for VMware
- Use NetBackup for vCloud Director
- About NetBackup for vCloud Director
- Notes on creating a NetBackup policy for vCloud
- Notes on restoring virtual machines into vCloud Director
- Restoring virtual machines into vCloud Director
- Reducing the time required for VM discovery in a large vCloud environment
- Virtual machine recovery dialog boxes for vCloud Director
- Recovery Destination dialog box (vCloud Director)
- Recovery Options dialog box (vCloud Director)
- Recovery vApp Options for vCloud Director dialog box (restore to original location)
- Virtual Machine Options dialog box for vCloud Director
- Perform Recovery dialog box for vCloud Director
- Recovery Options dialog box for vCloud Director (restore to alternate location)
- Recovery vApp Options for vCloud Director dialog box (restore to alternate location)
- Select a vApp dialog box
- Recovery Destination Options for vCloud Director dialog box (restore to alternate location)
- Virtual Machine Options (restore to alternate location)
- Network connections (restore to alternate location)
- Perform Recovery dialog box for vCloud Director (restore to alternate location)
- Best practices and more information
- Troubleshooting
- Notes on troubleshooting NetBackup for VMware
- Unsupported backup hosts
- How to determine the ESX network that NetBackup used for the backup or restore
- NetBackup logging for VMware
- Configuring VxMS logging
- Format of the VxMS core.log and provider.log file names
- Configuring the VDDK logging level
- Preventing browsing delays caused by DNS problems
- Changing the browsing timeout for virtual machine discovery
- Changing timeout and logging values for vSphere
- Credentials for VMware server are not valid
- Snapshot error encountered (status code 156)
- The origin of the snapshot failure: NetBackup or VMware?
- Conflict between NetBackup and VMware Storage vMotion with vSphere 5.0 or later
- Incremental backups of the VM may fail if the NTFS file system in the guest OS is corrupted and the backup uses MSDP storage
- The restore fails when you restore individual files to a virtual machine that has NetBackup client software
- Backup or restore job hangs
- VMware SCSI requirements for application quiesce on Windows
- Mount point missing on a restored Windows virtual machine
- Mount points not available when restoring files from a Linux virtual machine
- Invalid client error when you restore files using NetBackup BAR interface installed on the virtual machine
- VMware virtual machine does not restart after restore
- A restored VM may not start or its file system(s) may not be accessible
- NetBackup job fails due to update tasks on the VMware server
- The vSphere interface reports that virtual machine consolidation is needed
- The Enable file recovery from VM backup option does not work if a volume disk set contains a mixture of disk types
- Linux VMs and persistent device naming
- For a VMware virtual machine with Windows dynamic disks, a restore from incremental backup fails with a Windows restore host and the hotadd transport mode
- Simultaneous hotadd backups (from the same VMware backup host) fail with status 13
- Troubleshooting VMware tag usage
- Ensuring that guest customizations can be restored in vCloud Director
- Troubleshooting vmdk restore to existing VM
- Errors for backups of virtual machines on Virtual Volumes (VVols)
- Issues with the CA certificate during installation of the NetBackup client on VMware Cloud (VMC)
- Appendix A. NetBackup commands to back up and restore virtual machines
- Using NetBackup commands to create a VMware policy
- Using the nbdiscover command to search the virtual environment
- Using the nbrestorevm command to restore virtual machines into vSphere
- Using the nbrestorevm command to restore virtual machines into vCloud Director
- Using the nbrestorevm command to restore virtual machine disks
- The nbrestorevm -R rename file for restoring virtual machines
- Logs for troubleshooting the nbrestorevm command
- Query format and examples for searching virtual machine backups
- Allowing other servers or clients to restore virtual machines
- Appendix B. Configuring services for NFS on Windows
- About installing and configuring Network File System (NFS) for Granular Recovery Technology (GRT)
- About configuring services for NFS on Windows 2012 or 2016 (NetBackup for VMware)
- Disabling the Server for NFS (NetBackup for VMware)
- Disabling the Client for NFS on the media server (NetBackup for VMware)
- Configuring a UNIX media server and Windows backup or restore host for Granular Recovery Technology (NetBackup for VMware)
- Configuring a different network port for NBFSD (NetBackup for VMware)
- Appendix C. The Reuse VM selection query results option
- Appendix D. Backup of VMware raw devices (RDM)
- Index
Recovery Options dialog box (restore to alternate location)
This topic applies to NetBackup for VMware. It describes how to restore a VMware virtual machine to an alternate location.
The Recovery Options dialog initially displays the original virtual machine settings that were recorded in the NetBackup catalog when the virtual machine was backed up. Before accepting any default values, you may have to verify that the original hosts or servers are still available.
The dialog contains the following fields:
NetBackup Recovery Host
The recovery host transfers the virtual machine files to the VMware destination that is specified in other fields on this dialog. The default for the recovery host is the backup host that backed up the virtual machine.
Consider the following when selecting a recovery host:
To use the original VMware backup host for the recovery, verify that the backup host still exists. The original backup host may have been removed or reconfigured after the backup occurred.
The current processing load on the host that you want to use may be a factor. The recovery host undergoes significant I/O activity when it restores a virtual machine.
The network connection between the recovery host and the destination datastore may limit the type and speed of data transmission. For example, to use the SAN transport mode, the recovery host must have access to the appropriate LUNs in the datastore.
Media Server
You can use this option to select a media server that has access to the storage unit that contains the backup image. An example of such an environment is a Media Server Deduplication Pool (MSDP) with multiple media servers.
Note:
If the storage unit that contains the backup image is not shared with multiple media servers, this option is grayed out.
Transport modes
Determines how the data is sent from the recovery host to the VMware datastore. The appropriate mode depends on the type of connection between the NetBackup recovery host and the VMware datastore.
More information is available about these options.
vCenter Server
Specifies the vCenter server for the restored virtual machine. To use the original vCenter Server (the default), verify that the original vCenter server still exists.
To use a different vCenter Server, consider whether it is compatible with the virtual machine you want to restore. If you attempt to restore to an earlier vSphere server that does not support the virtual machine's hardware version, note: The VMware Tools component converts the virtual machine to an earlier hardware version. But the restore may fail if the virtual machine uses devices that only the later hardware version supports.
In other cases, you can use the option on the Virtual Machine Options dialog.
The restore may finish faster if you use the SAN transport mode with a restore ESX server (bypassing any vCenter servers).
When choosing a target host for the restore, note the following:
If NetBackup has credentials to a vCenter server but does not have credentials to a restore ESX server, you can perform the restore. NetBackup uses the vCenter credentials to access the ESX server but does not send the virtual machine data through the vCenter.
Note:
If you use the SAN transport mode for the restore, the restore job may take longer than expected.
The credentials must give NetBackup full access privileges to the vCenter server.
If NetBackup has credentials to a vCenter server as well as to a VMware restore ESX server, the restore may complete faster. In this case, by default NetBackup communicates with the restore ESX server during data transfer. You can select a vCenter folder in which to place the restored virtual machine. The credentials must give NetBackup full access privileges to the restore ESXi server.
Select the vCenter Server, and click to select the VMware restore ESXi server.
Note:
NetBackup uses the selected vCenter to create the virtual machine. NetBackup then writes the .vmdk files directly to the ESX server using the Restore ESX Server credentials to that server.
If NetBackup has credentials to an ESX server, you can designate that server as the target for the restore. The credentials must give NetBackup full access privileges to the ESX server.
Select for the vCenter Server, and click to select the ESX server.
Note:
To restore to an ESX server, the ESX must be standalone, not managed by vCenter. To restore to an ESX under vCenter, NetBackup must have VMware restore ESX server credentials for the ESX. Select the vCenter, and click to select the VMware restore ESX server.
ESX Server/Cluster
Specifies the ESX server or cluster on which the restored virtual machine is to reside. To use the original ESX server or cluster (the default), verify that the original ESX server or cluster still exists.
Click to browse for a different ESX server or cluster.
See Select ESX server dialog box (restore to alternate location).
Datacenter
Shows the VMware data center containing the selected ESX server.
Folder
A folder is a logical entity within the vCenter that contains VMware objects, such as datastores, networks, and virtual machines.
By default, this field shows the VMware folder that contained the virtual machine when the virtual machine was backed up. If you select a different ESX server to which to restore the virtual machine, this field changes to None. You must then click to select a folder within the data center for the restored virtual machine.
See Select Folder dialog box (restore to alternate location).
Display Name
Specifies the VMware display name for the restored virtual machine. The default is the display name that the virtual machine had when it was backed up.
The display name must be unique for the vCenter Server where the virtual machine is restored.
Note:
If a virtual machine with this display name already exists at this location (or at the original location), you are prompted to click . You cannot restore the virtual machine if the result is two virtual machines with the same display name on the same vCenter server.
Resource Pool/vApp
Use this option to have the restored virtual machine assigned to either a VMware resource pool or to a vApp. Resource pools manage the host's CPU and memory. vApps are logical containers for virtual machines, and also share some functionality with virtual machines.
Specifies the VMware datastore or datastore cluster that contains the virtual machine configuration files. Click to make a selection.
This datastore (sometimes called the vmx directory) contains the configuration files that describe the virtual machine, such as
*.vmxfiles. Active snapshots of vmdk files are also stored on this datastore.Note:
The Datastore field shows the name of the datastore that contained the virtual machine data when the virtual machine was backed up. Even if the datastore was in a datastore cluster, the field shows the name of the datastore, not the datastore cluster. When the virtual machine is restored, NetBackup determines how the datastore is currently configured (in a cluster or not) and configures the virtual machine accordingly.
Use the same datastore/datastore cluster for all VMDKs
This option assigns all the restored virtual machines to the datastore or datastore cluster that is selected in the Datastore/Datastore Cluster field.
If this option is not selected, you assign the VMDKs to specific datastores or datastore clusters in a later dialog (the Storage Destination dialog).