What’s NEW in Backup Exec 15 Feature Pack 5?
Backup exec introduces Instant Recovery for Virtual Machines which will help to reduce the restore time for a Virtual Machine (VM) to a great extent.
What would I achieve using this feature?
Achieve the best RTO with Backup Exec Instant Recovery; RTO in ‘SECONDS’…
What are the use-cases?
Do I need to purchase any additional Backup Exec license to use this new feature?
What are the additional system requirements for using this feature?
There are no new requirements for this feature.
How quick is the Recovery?
These job details are from one of the in-house IR job run.
What is this feature?
Instant Recovery (IR ) of a VM starts VM directly from the backup set located on Backup Exec storage.
This saves the time required to copy the data over the network to the hypervisor host.
What are the requirements for Instant Recovery?
“Host-based” VMware or Hyper-V backup sets
Backup sets must be stored on a disk device
How this feature works?
How the Backup sets are virtualized to the hypervisor host?
VxLatServer… a new process does the virtualization.
More about VxLatServer
About Virtualized Backup Sets
Are there any performance impacts of Instant Recovery?
Are there any considerations for Instant Recovery?
How can we backup the Instantly Recovered VMs?
IR VMs are excluded from backups run using the Agent for VMWare and Hyper-V unless:
How the Instant Recovery feature works in an upgrade scenario?
You can use this feature for VM backups after upgrading from Backup Exec 2014 or higher to Backup Exec 2015 Feature Pack 5.
If you are upgrading from earlier versions than Backup Exec 2014 RTM, you must run a full backup with FP5 to use this feature.
Questions asked by customers in external Demo
IR supports full, incremental, and differential virtual backups. It does not support agent based backups.
The initial release of IR in FP5 does not support Linux or other non-Windows OS VMs.
All sharing operations are controlled by the IR jobs. A Hypervisor appropriate share (NFS or SMB) will be created by the IR job and will be removed by the Remove IR job. The only manual step that need be taken by the user is to enable NFS server for Windows prior to running the first VMware IR job.
For running VMware VMs, storage vMotion is required. If storage vMotion is not licensed, the VM will have to be powered off prior to migration.
No, as long as VADP is enabled (in all but the free ESXi version).
Technically IR does not require an agent in the guest. However since the initial release requires GRT be enabled and since virtual AppGRT requires the agent to be installed to gather metadata and correctly handle VSS backups, in practice agents will already be installed for application support.
This is dependent on the specific IR VMs running and the quality and performance of the network and storage subsystem on the media server. An IR VM running an I/O intensive workload will have a larger impact on the media server than an IR VM that has a modest I/O workload.
Instant Recovery for VMware Virtual Machine
Instant Recovery for Hyper-V Virtual Machine
Instant Recovery Demo links
We hope you find this new Instant recovery feature of a great value and invite you to share your feedback once you’ve had an opportunity to use it.
We thank our customer and partners for providing valuable feedback during the development cycle. If you have any addition thoughts or constructive comments please let us know by commenting on this blog post.
Backup and Recovery Team
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.