Veritas NetBackup™ 8.0 for VMware Administrator's Guide
- Introduction
- About NetBackup for VMware
- Updates to this guide for NetBackup 8.0
- 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 license requirement
- NetBackup for VMware terminology
- Select Client wizard panel
- 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 virtual machine display names and other vSphere objects
- 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
- 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 options
- 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)
- About the Exclude disk options for Virtual disk selection
- Virtual disk selection options: an example to avoid
- Restoring data from the backups that excluded the boot disk or data disks
- 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
- About older NetBackup policies and pre-7.x backup hosts
- 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
- 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
- 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
- VMware virtual machine disk restore file
- About restore of individual files
- Restoring individual 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
- 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
- Beware of unsupported backup host
- 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
- The restore fails when you restore individual files to a virtual machine that has NetBackup client software
- Backup or restore job hangs
- VMware SCSI requirement for application quiesce on Windows 2008 or later
- Mount point missing on a restored Windows virtual machine
- Mount points not available when restoring files from a Linux virtual machine
- Remove the Consolidate Helper snapshot
- Invalid client error when you restore files using NetBackup BAR interface installed on the virtual machine
- VMware virtual machine does not restart after restore
- 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
- 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 (NetBackup for VMware)
- About configuring services for NFS on Windows 2008 and 2008 R2 (NetBackup for VMware)
- Disabling the Server for NFS (NetBackup for VMware)
- Disabling the Client for NFS on the media server (NetBackup for VMware)
- About configuring Services for Network File System (NFS) on the Windows 2003 R2 SP2 NetBackup media server and NetBackup clients (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)
- Appendix E. SYMCquiesce utility for Linux virtual machines
The nbrestorevm -R rename file for restoring virtual machines
The -R option on the nbrestorevm command is for restoring a VM to a different location. It identifies a text file that is called the rename file. This file describes the restore location by means of change directives. Each change directive provides information about a VMware attribute or object that defines the VM when it is restored. For example: the change directives can set the display name for the restored VM, the name of the datastore, and the name of the ESX server.
Note the following about the -R rename file:
The -R option must specify the absolute path to the rename file.
The -R option and rename file are not required when you restore the VM to its original location with all its original settings.
Each change directive in the -R rename file must end with a carriage return. If the file contains only one change directive, that line must end with a carriage return.
The change directives to include in the rename file depend on the VMware environment.
Unlike the Backup, Archive, and Restore interface, the nbrestorevm command does not have its own validation checks. When you use the nbrestorevm -R option, you must include all the change entries that the VMware environment requires. Otherwise, the restore does not succeed or the VM does not function correctly.
The change directives can be placed in any order in the file.
The change directive should be entered exactly as shown in Table: -R rename file change directives, except for the variable at the end (such as new_display_name). Replace that variable with the new name.
If a vSphere object does not apply to the restore destination, enter None as its value. For example: For restore to a standalone ESX, enter change datacenter to None.
The rename file overrides the nbrestorevm -vmsn and -vmvmxd options:
If the rename file includes a change directive for a .vmdk path and nbrestorevm includes the - vmvmxd option, the - vmvmxd option is ignored. The change directive determines the .vmdk path of the restored VM.
If the rename file includes a change directive to designate a network for the restored VM and nbrestorevm includes the - vmsn option, - vmsn is ignored.
Table: -R rename file change directives
-R rename file directives | Description and notes |
|---|---|
change vmname to new_display_name | Sets the display name for the restored VM. If this entry is omitted, the original display name is used. |
change esxhost to new_ESX_host | Designates the ESX server to restore to. This entry is required when you restore to a different ESX server. |
change datacenter to /new_datacenter | Designates the datacenter in which to restore the VM. If the destination does not have a datacenter, enter None as the value: change datacenter to None |
change folder to /new_datacenter/new_folder | Designates the folder in which to restore the VM. If the destination does not have a folder, enter None as the value: change folder to None |
change resourcepool to /new_datacenter/host/new_ESX_host/resources /new_resource_pool | For restore to a different ESX server, specify a different resource pool. (The original resource pool cannot be used to create a VM on a different ESX server.) You must specify a resource pool by including the following line in the rename file: For restore to a standalone ESX server, the change resourcepool entry must include the literal string ha-datacenter in the path: change resourcepool to /ha_datacenter//host/new_ESX_host/resources |
change datastore to new_vmx_datastore | Designates the vmx datastore (configuration datastore) of the restored VM. The vmx datastore contains the configuration files that describe the virtual machine. This change entry is required when you use the - vmvmxd option on the nbrestorevm command. The -vmvmxd option allows the vmdk files to be restored to the same datastore where the vmx file is specified. Note: See the change /original_vmdk_path to /new_vmdk_path directive in this table. |
change /original_vmdk_path to /new_vmdk_path | Designates the original path to the .vmdk file, and the new path to the .vmdk file of the restored VM. As a rule, this change entry is required when you restore to a different datastore. Depending on your VMware environment, this change entry may take the following form: change /original_datastore/original_VM_folder/original_vmdk.vmdk to /new_datastore/new_VM_folder/new_vmdk.vmdk Note: If you use the -vmvmxd option on nbrestorevm to restore the .vmdk files to the vmx datastore, do not use this change directive. By specifying the datastore for the vmdk files, this change directive overrides the -vmvmxd option. Note: If the change vmdk directive specifies a different path for some of the VM's vmdk files, the other vmdk files are restored to their original datastore. To restore more than one vmdk file to a specified datastore: change /first_vmdk_path to /new_first_vmdk_path change /second_vmdk_path to /new_second_vmdk_path change /nth_vmdk_path to /new_nth_vmdk_path |
change network to new_network | Designates the new network for the restored VM. To designate multiple networks, enter the following: change network to new_network, new_network(n) |
change organization to new_organization | Designates the vCloud Director organization to restore to. |
change orgvdc to new_organization_virtual_datacenter | Designates the virtual datacenter in the vCloud Director organization to restore to. |
change vcdserver to new_vcdserver | Designates the vCloud Director server to restore to. |
change vcdvapp to new_vcdvapp | Designates the vCloud Director vApp to restore to. |
change vcdvapptemplate to new_vcdvapptemplate | Designates the vCloud Director vApp template to restore to. |
change vcdvmname to new_vcdvmname | Sets the display name for the restored VM in vCloud Director. |
change vcdcatalog to new_vcdcatalog | Designates the vCloud Director catalog to restore to. |