Backup Exec 21 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)
- Updating Backup Exec with Veritas Update
- 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
- Changing network and security options for Backup Exec
- 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
- GDPR Guard
- 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
- Integration with Veritas SaaS Backup
- Forever Incremental Backup
- 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
Upgrading an existing CAS installation
In an existing CAS environment, upgrade the central administration server, and then upgrade the managed Backup Exec servers. You can upgrade from Backup Exec 2014 or later.
If necessary, you can perform rolling upgrades in the CAS environment. A rolling upgrade lets you upgrade the central administration server from the previous version to the current version first, and then upgrade the managed Backup Exec servers from the previous version to the current version over a period of time. Note that a rolling upgrade can be performed only from Backup Exec 16 Feature Pack 2 or later. Rolling upgrades are not supported from any versions before Backup Exec 15. You must have the most recent Backup Exec feature pack to perform rolling upgrades.
Forward compatibility is not supported in rolling upgrades. Therefore, any system that runs the previous version cannot protect a system that runs the current version.
It is recommended that you do not keep a mix of versions in the CAS installation for an extended time. Key functionality for administering managed Backup Exec servers is missing in a mixed-version environment, which decreases your ability to properly administer the CAS environment.
Do not rename any managed Backup Exec servers or the central administration server during the upgrade process. Although you can rename the servers before you upgrade, it is recommended that you rename them after the upgrade process has completed.
After you upgrade the central administration server to the current version, the following operations are supported on managed Backup Exec servers that run the previous version:
To upgrade an existing CAS installation
- Verify that the latest feature pack for Backup Exec is installed.
- Place all scheduled jobs on hold on the central administration server and the managed Backup Exec servers.
See Holding jobs.
- Allow all active jobs to complete.
- Run a database maintenance job to delete job histories and catalogs that you no longer need in order to shorten the upgrade window.
- Stop all Backup Exec services on each managed Backup Exec server
- From the installation media browser, select the option to install Backup Exec.
- On the Welcome panel, click Next.
- Select I accept the terms of the license agreement, and then click Next.
- Check Local Install, and then click Install Backup Exec software and features.
- Click Next.
- Follow the prompts in the wizard.
- On the Back Up Existing Catalog and Data page, enter or browse to a directory to which all existing catalogs and data will be backed up. The default location is:
C:<Backup Exec install path>\Backup Exec\Data
If you do not want to keep previous catalogs and data, click Do not back up previous data and catalogs.
- Click Next to continue.
An upgrade summary is displayed. When the upgrade is complete, communication with the managed Backup Exec servers is automatically enabled.
- Release the hold on all the jobs.
- Upgrade some or all of the managed Backup Exec servers.
If you are upgrading the central administration server from Backup Exec 16 Feature Pack 2 to Backup Exec and some of the managed Backup Exec servers were not backed up before the upgrade, those managed Backup Exec servers do not appear on the Backup and Restore tab until you upgrade the managed Backup Exec servers to Backup Exec 16 Feature Pack 2 or manually add them using the Add Server wizard.
You should enable the Allow only Kerberos authentication from the Remote Administration Console check box only after all the Managed Backup Exec Server (MBES) and CAS servers are upgraded to the same version.