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
Requirements for using Simplified Disaster Recovery
The following items are required for Simplified Disaster Recovery (SDR):
Backup Exec or the Backup Exec Agent for Windows must be installed on any computers that you want to protect with SDR.
The Create Simplified Disaster Recovery Wizard is not supported on any 32-bit operating system.
Encryption key files must exist for all volumes that you encrypt with Windows BitLocker Drive Encryption.
A third-party ISO 9660-compliant CD or DVD burning application must be available to burn the SDR-created bootable image to a CD or DVD.
A writable or rewritable CD or DVD device must be available.
An Internet connection so that you can download the Microsoft Assessment and Deployment Kit.
The optionmust be enabled. If you disable this option, the backup sets that you create for use with SDR cannot be restored during an SDR recovery operation. As a result, SDR cannot recover the failed computer. To ensure that this option is enabled, click the Backup Exec button, click > > .
If you use deduplication disk storage devices, be aware that there are limitations in their use with SDR.
Additional requirements exist when you create a Simplified Disaster Recovery disk image and when you run the Recover This Computer Wizard, as described in the following sections.
The following items are required to create the Simplified Disaster Recovery disk image:
The Simplified Disaster Recovery disk image must be the same version of Backup Exec as the Backup Exec server. You cannot use SDR to restore the backups that were created with previous versions of Backup Exec.
The Microsoft WIndows Assessment and Deployment Kit (ADK) 8.1, and ADK 8.1 Update 1 is supported only on Windows Server 2008 SP2. On Windows 2008 R2 and later, you can create an SDR disk only using ADK 10. If the Backup Exec server does not run on Windows Server 2008 SP2 or later, or if the server does not have an Internet connection, methods are provided to let you create the Simplified Recovery Disk.
The recovery disk created with Windows ADK 8.1 does not detect the Backup Exec storage folder (\BEData) if this folder is configured on the storage pools and storage spaces on the Backup Exec Server. This problem happens only when the Backup Exec server installed on Windows 2016 operating system is not available and you want to perform an SDR local recovery from the BEData folder.
If you create the storage pools and spaces using the recovery disk created with Windows ADK 10, then after system restore, the Windows 2012 and windows 2012 R2 operating systems does not detect the storage pools and spaces.
5 GB of disk space to download and install ADK.
1 GB of disk space to store the required files and folders to create the ISO image.
The following items are required to run the Recover This Computer Wizard:
The Simplified Disaster Recovery disk image must be the same version of Backup Exec as the Backup Exec server.
If the computer that you want to recover was backed up to a tape device, deduplication storage, or to a virtual disk, then SDR cannot store the disaster recovery information file with the backup sets. Instead, you must provide the path to the default location or to the alternate location when the Recover This Computer Wizard prompts you. The default location is
C:\Program Files\Veritas\Backup Exec\sdr\Data. If the file is unavailable, you cannot recover the computer with SDR.
The backup set that contains all of the critical system components for the computer that you want to restore.
The boot drive on the computer that you want to recover must have from 3-GB to 5-GB of free space depending on the operating system and configuration.
If a blank screen appears and the computer does not restart after you use the SDR disk, ensure that the boot drive has the necessary amount of free space. Then, restart the computer again.
The target computer that you want to recover to must have an amount of RAM that is equal to or greater than the minimum that the restored operating system requires.
The target computer that you want to recover to must have disks with enough free space to contain the data that you restore from the backup of critical volumes. A volume is considered critical if it is required for the computer to start successfully.
If you recover a Windows computer that has BitLocker encryption enabled, you must turn on BitLocker encryption after the restore. See your Microsoft documentation for more information on BitLocker drive encryption.
If the computer you recover contains a RAID setup, you may be required to configure the RAID before you start it with the SDR disk. Use the computer manufacturer's RAID software to configure the RAID system.
If you restore Windows 8, Windows 8.1, Windows Server 2012, Windows Server 2012 R2, or Windows Server 2016 storage spaces and storage pools, you should be aware of the possible restore scenarios.