Backup Exec 23 Administrator's Guide
- Introducing Backup Exec
- Installation
- 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)
- About updates to Backup Exec using Veritas Update
- Backup Exec license contract information
- About upgrading to Backup Exec
- Getting Started
- Configuring the Home tab
- Backups
- Recommendations for when to use virtual-based backup and agent-based backup
- Backing up data
- Restores
- 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
- Cloud deduplication storage device
- Requirements for configuring a cloud deduplication storage device
- About the Backup Exec™ CloudConnect Optimizer
- Generic S3 Configurator
- OpenStorage devices
- Microsoft 365
- OneDrive plugin: Performance and throttling configuration
- Exchange plugin: Performance and throttling configuration
- SharePoint plugin: Performance and throttling configuration
- Teams plugin: Performance and throttling configuration
- 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
- Configuring role-based access settings
- Configuring parallel streams and job settings for Microsoft 365
- Changing network and security options for Backup Exec
- Using Backup Exec with firewalls
- Deleting DBA-initiated job templates
- Backup Exec logon accounts
- Reports
- 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
- 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
- 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
- About SQL Server Always On availability groups
- 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
- About retrieving migrated Enterprise Vault data
- About the Partition Recovery Utility
- Appendix J. Backup Exec Agent for Microsoft Active Directory
- 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 File Servers
- Appendix O. Backup Exec Agent for Linux and Unix
- About installing the Agent for Linux and Unix
- About establishing trust for a remote Linux and Unix computer in the Backup Exec list of servers
- Editing configuration options for Linux and Unix computers
- About backing up a Linux and Unix computer by using the Agent for Linux and Unix
- About restoring data to Linux and Unix computers
- Editing the default backup job options for Linux and Unix computers
- Uninstalling the Agent for Linux and Unix
Terms used by SQL Server Always On availability groups
The following table describes the terms used by Microsoft SQL Server Always On availability groups.
Table: Terms used by SQL Server Always On availability groups
Item | Description |
---|---|
Availability group | A container for a set of databases, availability databases, that fail over together. |
Availability database | A database that belongs to an availability group. For each availability database, the availability group maintains a single read-write copy (the primary database) and one to eight read-only copies (secondary databases). |
Primary database | The read-write copy of an availability database. |
Secondary database | A read-only copy of an availability database. Secondary databases are not backups. Continue to back up your databases and their transaction logs on a regular basis. |
Availability replica | An instantiation of an availability group that is hosted by a specific instance of SQL Server and maintains a local copy of each availability database that belongs to the availability group. Two types of availability replicas exist: a single primary replica and one to eight secondary replicas. |
Primary replica | The availability replica that makes the primary databases available for read-write connections from clients and, also, sends transaction log records for each primary database to every secondary replica. |
Secondary replica | An availability replica that maintains a secondary copy of each availability database and serves as a potential fail over target for the availability group. Optionally, a secondary replica that can support read-only access to secondary databases supports creating backups on secondary databases. |
Availability group listener | A server name to which clients can connect in order to access a database in a primary or secondary replica of an Always On availability group. Availability group listeners direct incoming connections to the primary replica or to a read-only secondary replica. This name is similar to cluster name and has associated IP address. |
Backup Preference | The Always On availability groups active secondary capabilities include support for taking backups on secondary replicas. Backup preference setting provides a way to specifies where backups should run.
Note: This setting is not enforced in Backup Exec. |
Replica backup priorities | This setting allows giving a priority to each replica from 1 (minimum) to 100 (maximum) to select the node for the backup. |
Exclude Replica | This setting allows to skip a node for performing backups. This is useful, for example, for a remote availability replica to which you never want backups to fail over. |