Veritas Backup Exec 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 Veritas 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
- 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
- Integration with Veritas™ Information Map
- Appendix A. Veritas Backup Exec Agent for Windows
- About the Backup Exec Agent Utility for Windows
- Appendix B. Veritas Backup Exec Deduplication Option
- Creating or importing deduplication disk storage
- Selecting storage devices for direct access sharing
- Appendix C. Veritas Backup Exec Agent for VMware
- Backing up VMware virtual machines
- About instant recovery of a VMware virtual machine
- About Recovery Ready for VMware virtual machines
- Appendix D. Veritas 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. Veritas 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. Veritas Backup Exec Agent for Microsoft Exchange Server
- Backing up Exchange data
- Appendix G. Veritas Backup Exec Agent for Microsoft SharePoint
- Backing up Microsoft SharePoint data
- Appendix H. Veritas 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. Veritas 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. Veritas Backup Exec Agent for Microsoft Active Directory
- About backing up Active Directory and ADAM/AD LDS
- Appendix K. Veritas Backup Exec Central Admin Server Option
- 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. Veritas Backup Exec Advanced Disk-based Backup Option
- Appendix M. Veritas Backup Exec NDMP Option
- 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. Veritas 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. Veritas 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
Creating an instant recovery job for a VMware virtual machine
You can create an instant recovery job for a VMware virtual machine, and then recover the virtual machine to the original location or to an alternate location.
If you want to move the instantly recovered virtual machine from Backup Exec server storage to VMware storage, you can migrate the virtual machine data files or the required disks from the instantly recovered virtual machine to VMware storage using Storage vMotion. During the migration, the virtual machine data files are transferred to VMware storage while the virtual machine is still running.
For applications such as SharePoint and Exchange, recover all of the virtual machines that the applications need to use to function properly. For example, to create a Microsoft Exchange environment, recover the virtual machines that run the Exchange client and the Active Directory, and then establish a connection between these two virtual machines.
Complete the following steps to create an instant recovery job for a VMware virtual machine.
To create an instant recovery job for a VMware virtual machine
- On the Backup and Restore tab, select the virtual machine that you want to instantly recover.
- In the Instant Recovery group, click Instantly Recover a VM.
- On the Instantly Recover a VM dialog box, in the Job name field, type a name for the instant recovery job.
- In the Backup set selection group box, in the Show backup sets from field, select the beginning and ending dates for the backup sets that you want to include in the backup set selection.
By default, only the backup sets for jobs that ran in the past 30 days are displayed.
- In the Disk-based backup set field, select the backup set that you want to use for the instant recovery job.
Only backup sets that meet the requirements for instant recovery are included in the list.
- In the left pane, select Destination, and then set the following options for the job:
Virtual machine name
Indicates the instantly recovered virtual machine name.
vCenter server or ESX host name
Indicates the name of the vCenter server or ESX host.
Server logon account
Uses the default logon account that appears. You can select another logon account to use for the vCenter server or ESX host.
Indicates the name of the ESX host that will run the instantly recovered virtual machine.
Virtual machine folder
Indicates the name of the existing vSphere folder to which you want to instantly recover the virtual machine.
The folder default is the root of the datacenter.
Indicates the name of the resource pool to which you want to instantly recover the virtual machine.
The resource pool is optional.
Indicates the name of the network that the instantly recovered virtual machine should use after the job completes.
Ensure that you select a network that is isolated from the source virtual machine. Otherwise, it may cause network conflicts between the source virtual machine and the instantly recovered virtual machine.
Datastore or datastore cluster for storing virtual machine writes
Indicates the name of the datastore where you want to store any temporary changes that are made to the instantly recovered virtual machine.
Power on the virtual machine after it is recovered
Enables Backup Exec to start the virtual machine automatically after it is instantly recovered.
- On the Instantly Recover a VM dialog box, in the left pane, select Schedule, and then select the schedule for this job.
- (Optional) On the Instantly Recover a VM dialog box, in the left pane, select Notification, and then select recipients to notify when the job completes.
- Click OK.