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)
Create an instant access VM
You can create an instant access VM from a NetBackup backup image. The VM is available almost instantaneously, achieving a near-zero recovery time objective. NetBackup mounts the VM's snapshot directly on the backup storage device to allow your ESXi host or cluster to treat the snapshot as a normal VM.
The mounted VM snapshot can be used for a variety of purposes. For example:
Recovering files from the VM, or copying a vmdk file.
Running tests on the VM, such as testing a patch.
Troubleshooting or disaster recovery.
Verifying an application.
Note:
This feature is supported for NetBackup Appliance, NetBackup Virtual Appliance, Flex Appliance, and Build Your Own (BYO) server. This feature requires that the NetBackup backup image is stored on a Media Server Deduplication Pool (MSDP) storage device. More information on using instance access VMs is available:
See Things to consider before you use the instant access feature.
To create an instant access VM
- On the left, click VMware.
- Locate the VM and click on it.
- Click the Recovery points tab, then click the date on which the backup occurred.
The available images appear in rows with the backup timestamp for each image.
- Select the Allow the selection of recovery of points that are malware-affected to be able to recover malware affected images. This option is only available for the recovery points which contains malware-affected images.
Note:
This options is enabled only for users with required permissions.
- On the image or the copy of the image that has the option to recover using instant access, click Recover > Create instant access virtual machine.
- Review the recovery settings and make changes if needed.
Note the Recovery options:
Allow overwrite of existing virtual machine
If a VM with the same display name exists at the destination, that VM must be deleted before the recovery begins. Otherwise, the recovery fails.
Power on after provisioning
Automatically powers on the VM when the recovery is complete.
Enable vMotion
Starts the migration of the VM after it is created and then displays progress of the VM migration.
Note:
For a NetBackup 8.1.2 storage server, the vMotion option is not used even if it is enabled.
- Click Create.
NetBackup makes a snapshot of the VM backup image and creates an instant access mount point. The snapshot of the image appears on the Instant access virtual machines tab. You can now use the VM like any other VM on the ESXi server.
- For details on the restored VM, click on the VM under the Instant access virtual machines tab and click View details.
- When you are finished with the VM, you can click Delete to remove the mounted VM snapshot. The VM is removed from the ESXi server.
Note:
If vMotion is enabled and completed successfully, deleting a VM only removes the mounted share. The VM is still available on the ESXi server as this VM is migrated to another datastore.