Backup Exec 20.2 Administrator's Guide
- Introducing Backup Exec
- Methods for installing the Agent for Windows
- Using a command prompt to install the Agent for Windows on a remote computer
- Using a command script to install the Agent for Windows
- Installing the Remote Administrator
- Installing Backup Exec using the command line (silent mode)
- Backup Exec license contract information
- About upgrading to Backup Exec
- Getting Started
- Backing up data
- How Backup Exec catalogs work
- Job management and monitoring
- About the Job Monitor
- About the Job History
- Viewing the job log
- Error-handling rules for failed or canceled jobs
- Alerts and notifications
- Enabling active alerts and alert history to display on the Home tab
- Adding a recipient group for alert notifications
- Sending a notification when a job completes
- SNMP traps for Backup Exec alerts
- Disk-based and network-based storage
- Configuring disk storage
- Configuring disk cartridge storage
- Backup sets
- Cloud-based storage devices
- Amazon S3 cloud-based storage
- Google cloud-based storage
- Microsoft Azure cloud-based storage
- Private cloud-based storage
- About S3-Compatible Cloud Storage
- About the Backup Exec™ CloudConnect Optimizer
- Legacy backup-to-disk folders
- Legacy backup-to-disk folders
- Legacy backup-to-disk folders
- Tape storage
- Robotic libraries in Backup Exec
- Creating robotic library partitions
- Managing tapes
- Creating media sets for tapes
- Labeling tape media
- Default media vaults
- Storage device pools
- Storage operations
- Conversion to virtual machines
- Configuration and settings
- Using Backup Exec with firewalls
- Deleting DBA-initiated job templates
- Backup Exec logon accounts
- Creating a custom report
- List of Backup Exec standard reports
- Instant Cloud Recovery
- Preconfigurations to be completed in the Azure portal
- Troubleshooting Backup Exec
- Troubleshooting failed components in the SAN
- Generating a diagnostic file for troubleshooting Backup Exec
- Using Backup Exec in cluster environments
- Configurations for Backup Exec and Microsoft Cluster Servers
- Disaster recovery of a cluster
- Simplified Disaster Recovery
- Setting or changing the alternate location for the disaster recovery information file
- Creating a Simplified Disaster Recovery disk image
- Preparing to recover from a disaster by using Simplified Disaster Recovery
- Recovering a computer with Simplified Disaster Recovery
- Performing manual disaster recovery
- Integration with Veritas™ Information Map
- Appendix A. Backup Exec Agent for Windows
- About the Backup Exec Agent Utility for Windows
- Appendix B. Backup Exec Deduplication Feature
- Creating or importing deduplication disk storage
- Selecting storage devices for direct access sharing
- Appendix C. Backup Exec Agent for VMware
- About establishing trust for a vCenter/ESX(i) server
- Backing up VMware virtual machines
- About instant recovery of a VMware virtual machine
- About Recovery Ready for VMware virtual machines
- Appendix D. Backup Exec Agent for Microsoft Hyper-V
- Backing up Microsoft Hyper-V virtual machines
- About instant recovery of a Hyper-V virtual machine
- About Recovery Ready for Hyper-V virtual machines
- Appendix E. Backup Exec Agent for Microsoft SQL Server
- Backing up SQL databases and transaction logs
- Restoring SQL databases and transaction logs
- Disaster recovery of a SQL Server
- Appendix F. Backup Exec Agent for Microsoft Exchange Server
- Backing up Exchange data
- Appendix G. Backup Exec Agent for Microsoft SharePoint
- Backing up Microsoft SharePoint data
- Appendix H. Backup Exec Agent for Oracle on Windows or Linux Servers
- Configuring the Oracle Agent on Windows computers and Linux servers
- Configuring an Oracle instance on Windows computers
- Viewing an Oracle instance on Windows computers
- About authentication credentials on the Backup Exec server
- About backing up Oracle databases
- About restoring Oracle resources
- Appendix I. Backup Exec Agent for Enterprise Vault
- About backup methods for Enterprise Vault backup jobs
- Restoring Enterprise Vault
- About the Backup Exec Migrator for Enterprise Vault
- Configuring the Backup Exec Migrator
- Configuring Enterprise Vault collections
- Configuring the Backup Exec Migrator to communicate with Enterprise Vault
- About retrieving migrated Enterprise Vault data
- About the Partition Recovery Utility
- Appendix J. Backup Exec Agent for Microsoft Active Directory
- About backing up Active Directory and ADAM/AD LDS
- Appendix K. Backup Exec Central Admin Server Feature
- About installing the Central Admin Server feature
- What happens when CAS communication thresholds are reached
- About job delegation in CAS
- How to use Backup Exec server pools in CAS
- How centralized restore works in CAS
- Appendix L. Backup Exec Advanced Disk-based Backup Feature
- Appendix M. Backup Exec NDMP Feature
- About restoring and redirecting restore data for NDMP servers
- Viewing the properties of an NDMP server
- Viewing storage properties for an NDMP server
- Appendix N. Backup Exec Agent for Linux
- About installing the Agent for Linux
- About establishing trust for a remote Linux computer in the Backup Exec list of servers
- Editing configuration options for Linux computers
- About backing up a Linux computer by using the Agent for Linux
- About restoring data to Linux computers
- Editing the default backup job options for Linux computers
- Uninstalling the Agent for Linux
- Appendix O. Backup Exec Remote Media Agent for Linux
- About installing the Remote Media Agent for Linux
- About establishing trust for a Remote Media Agent for Linux computer in the Backup Exec list of servers
- About the Backup Exec operators (beoper) group for the Remote Media Agent for Linux
- About adding a Linux server as a Remote Media Agent for Linux
- Editing properties for the Remote Media Agent for Linux
- Creating a simulated tape library
- Viewing simulated tape libraries properties
- Appendix P. Accessibility and Backup Exec
- About keyboard shortcuts in Backup Exec
- Backup and Restore tab keyboard shortcuts
- Storage tab keyboard shortcuts
About instant recovery of a Hyper-V virtual machine
Backup Exec lets you recover a virtual machine instantly from a backup set without waiting to transfer the virtual machine's data. Backup Exec starts the instantly recovered virtual machine directly from the backup set and users can access it on the Hyper-V host immediately. The startup time depends on the network speed and storage speed and not on the size of the virtual machine. You can use an instantly recovered virtual machine to perform the same operations as a virtual machine.
An instantly recovered virtual machine can be used to do the following:
Access and restore individual files and folders from a virtual machine.
Test a patch on an instantly recovered virtual machine before you apply the patch to production systems.
Verify the backup image of the virtual machine and the applications.
Verify an application within the instantly recovered virtual machine.
Recover the instantly recovered virtual machine permanently by using Hyper-V Live migration or Storage migration. In a disaster recovery scenario, you can instantly recover a virtual machine in minutes and then schedule a migration to move it to a permanent storage on a Hyper-V host. The instantly recovered virtual machine remains available even during the migration process, which decreases the amount of downtime.
You cannot back up instantly recovered virtual machines with the Agent for Hyper-V until you migrate the virtual machine from Backup Exec server storage and also remove from the virtual machine from Backup Exec server storage.
If you remove an instantly recovered virtual machine, any changes that you made are lost. Migrate the virtual machine from the Backup Exec server storage and remove it from Backup Exec to retain the changes or back up the instantly recovered virtual machine with the Agent for Hyper-V.
When you run an instant recovery job, the selected backup set is exposed to the Hyper-V host through an SMB share that is created on the Backup Exec server. The instantly recovered virtual machine disks are on the Backup Exec storage but they use the CPU of the Hyper-V host for their functions. All read operations are redirected to the Backup Exec server and the write operations are saved in a differencing disk at the location that is mentioned in the Destination for VM registration and checkpoint field when you create an instant recovery job. This path is on the Hyper-V host on which you want to recover the virtual machine.
Backup Exec alerts you every week about the number of instantly recovered virtual machines running on the server. By default, the alert is triggered every Friday at 2.00 PM.
The following table describes the instant recovery process for a virtual machine.
Table: Instant recovery process for a Hyper-V virtual machine
You run an instant recovery job from a backup of a Hyper-V virtual machine.
The Backup Exec server virtualizes the backup set.
Backup Exec creates an SMB share.
Backup Exec creates a virtual machine on the Hyper-V host.
Backup Exec creates a snapshot of the virtual machine so that the writes can be made to the local disk.
Backup Exec starts up the virtual machine automatically if you select the option to power on the virtual machine after it is recovered.
Step 7 (optional)
You use Live Migration or Storage Migration to migrate the virtual machine from Backup Exec server storage if you want to save any changes that were made to the virtual machine.
You run a job to do one of the following:
You cannot upgrade Backup Exec until you remove all of the instantly recovered virtual machines.
As Backup Exec has enhanced the resiliency for instantly recovered virtual machines, if you restart the Backup Exec server, restart the Hyper-V server, or if there is a network connectivity issue, any changes that you made to the virtual machine are no longer lost. After either of these servers restart, the Backup Exec services start up and the virtualization process continues.
There are four scenarios for resiliency when the instantly recovered virtual machine is running on the Hyper-V host:
Backup Exec server restarts and the Hyper-V server is running.
Hyper-V server restarts and the Backup Exec server is running.
Backup Exec and the Hyper-V servers restart.
Network connectivity issues result in connection loss between the Backup Exec server and Hyper-V host.
In all these scenarios, the virtual machine starts automatically when the server restart is complete or network connectivity is restored. If the virtual machine does not start, you may require to restart it on the Hyper-V host.
The virtual machine cannot be used until the server restart is complete or network connectivity is restored.
Instant Recovery Resiliency for Hyper-V uses the CORBA communication method. A configuration change may be required if you require to change the CORBA communication port on the Backup Exec server. The Backup Exec server and the Hyper-V server hosting the instantly recovered virtual machine must have the same CORBA port setting.
To change the CORBA port setting on the Backup Exec server
- Click the Backup Exec button, select Configuration and Settings, and then select Backup Exec Settings.
- In the left pane, select Network and Security.
- Under Custom port Number (Oracle only), select the Use a custom port to receive operation requests from the Oracle server check box and enter the same port number as entered on the Hyper-V server.
- Stop and restart all Backup Exec services and rerun the backup.
To change the CORBA port setting on the Hyper-V host
- On the computer on which the Agent for Windows is installed, on the taskbar, click Start > All Programs > Veritas Backup Exec > Backup Exec Agent Utility.
- Click the Database Access tab.
- Select the Use a custom port to connect to the Backup Exec server during Oracle operations check box.
- Enter a port number that is not in use and can be used by Backup Exec and then click OK.
This port number must match with what is configured on the Backup Exec server.
- Restart the Backup Exec Remote Agent Service on the Hyper-V server.
Instant recovery of a virtual machine is different from a virtual machine restore in some aspects.
Table: Differences between an instantly recovered virtual machine and a restored virtual machine
Instant recovery of a virtual machine
Restore of a virtual machine
Does not transfer the virtual machine data to the instantly recovered virtual machine.
Transfers all data from the backup set to the restored virtual machine.
Instant recovery job runs instantly and no backup data is transferred. Therefore, the job time depends on the time taken to share the backup set and register the virtual machine.
Restore time depends on the size of the virtual machine and the network speed and storage speed.
Uses the backup set image for all read operations. It uses a snapshot on the Hyper-V server for all write operations.
All data is already moved to the Hyper-V server. Therefore, there is no dependency on the Backup Exec server.
Uses the Backup Exec server storage until you migrate the instantly recovered virtual machine.
Already uses the Hyper-V server storage.
As the Instant Recovery resiliency is enhanced, if the Backup Exec server or the Hyper-V server restarts, the instantly recovered virtual machines remains accessible.
In case of network connectivity issues the instantly recovered virtual machines are accessible after the connectivity is restored.
If the virtual machine does not start, you may require to restart it on the Hyper-V host.
Restarting the Backup Exec server or the Hyper-V server has no effect on the restored virtual machine.
See Requirements for instant recovery of a Hyper-V virtual machine.
See Creating an instant recovery job for a Hyper-V virtual machine.
See About removing an instantly recovered Hyper-V virtual machine.
See Notes about instant recovery of a Hyper-V virtual machine .