Backup Exec 20.1 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
- 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
- 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
Requirements for using the Agent for Microsoft Hyper-V
You can find a list of compatible devices, operating systems, platforms, and applications in the Backup Exec Hardware and Software Compatibility Lists.
The following items are required:
Table: Requirements for the Agent for Microsoft Hyper-V
A supported version of Microsoft Hyper-V
Microsoft Hyper-V host
Backup Exec server
It is recommended that the Backup Exec server should run a version of Windows that is equal to or greater than the highest version of Windows that the virtual machines in your environment run. For example, if your virtual machines run Microsoft Windows Server 2012, the Backup Exec server should also run Microsoft Windows Server 2012.
Agent for VMware and Hyper-V
Microsoft Hyper-V host
If you use Hyper-V in a cluster environment, you must install the Agent for VMware and Hyper-V on each node in the cluster. If you do not, you may not be able to see all of the clustered backup sources that are available for backup.
Backup Exec server (if the Backup Exec server is not the virtual server).
VHDMount is required only if the Backup Exec server runs Microsoft Windows 2008 without the Hyper-V role installed. You can install the VHDMount component from Microsoft Virtual Server 2005 R2 SP1. In addition, VHDMount is required for Granular Recovery Technology (GRT)-enabled backups. If you do not plan to use GRT, then VHDMount is not required.
To run an online backup, the following requirements must be met:
Check the Microsoft website for a Hyper-V Server version and its supported Windows server guest operating systems.
Hyper-V Integration Services with Backup (Volume snapshot) is installed.
Using an incorrect version of Hyper-V Integration Services may lead to a virtual machine being backed up offline instead of online. For example, if you copy a virtual machine from a Windows 2012 Hyper-V host to a Windows 2012 R2 Hyper-V host, the Hyper-V Integration Services are not updated automatically.
The virtual machine is in a running state.
If these conditions are not met, the virtual machine is placed in a saved state if it is running. If the virtual machine is turned off, then that virtual machine is backed up only if you select the option Back up virtual machines that are powered off on the Virtual Machines options dialog box.
To enable Backup Exec to collect catalog data for Microsoft Exchange, SharePoint, Active Directory, and SQL on the virtual machine, the following items are required on the virtual machine:
A licensed version of the Backup Exec agent for the application.
The Agent for Windows.
The Agent for Microsoft Hyper-V includes a license for the Agent for Windows. The agents for Microsoft Exchange, Active Directory, and SQL also include a license for the Agent for Windows. No separate license is required for the Agent for Windows.
The virtual machine must be capable of being backed up online.
The credentials that you use to access the virtual machine must also have access to the application.
The following items are required for virtual machines:
Virtual machines must have unique names. Backup Exec does not support virtual machines that have duplicate names.
You must assign shadow storage to each NTFS volume that exists on a virtual machine if the virtual machine uses the Windows 2008 operating system. Otherwise, the backup jobs fail for that virtual machine.
The Agent for Windows must be installed on the virtual machine to enable individual files and folders to be restored back to the original virtual machine.
The Agent for Windows must be installed on the virtual machine to enable individual SQL databases, Exchange items, SharePoint items, and Active Directory objects to be restored back to the original virtual machine.
Do not use special characters, such as the percent sign (%) or a forward slash (/) in Hyper-V virtual machine names. Special characters may cause redirected restores to fail.