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
Configuring an Oracle instance on Linux servers
You can use the Backup Exec Agent Utility to configure information about the Oracle instances for the Oracle Agent on Linux servers.
To configure an Oracle instance on Linux servers
- On the Linux server on which the Oracle instances are installed, open a Terminal window.
If the Oracle instance you want to protect is part of an Oracle RAC setup with version 12c, switch to the Oracle user using the su - <oracleuser> command.
- Change to the following directory:
- Start the Backup Exec Agent Utility:
- Type 2 to select Configure Oracle instance information, and then press Enter.
- Type 1 to select the Add a new Oracle Instance option, and then press Enter.
- Enter the name of the Oracle instance in upper case characters.
For example, ORACLENAME.
- Enter the user name for the Oracle instance.
When you use the Backup Exec Agent Utility to enter the Oracle credentials for an instance, the credentials cannot be verified if the user account with which you are logged on is a member of the Oracle DBA group. If the credentials are incorrect, the error "Unable to attach to a resource..." may appear when you run a backup job.
For Oracle 12c, the user should have SYSBACKUP privileges.
- For Oracle 12c and later versions, when prompted, enter the auxiliary instance path for PDB restores.
If the database that you are restoring does not use a Fast Recovery Area, RMAN creates the auxiliary database data files in the location you specify.
Agent Utility cannot validate a path specified on the ASM disk and accepts the path as specified. Therefore, you must ensure that the path you entered is correct and accessible.
The database instance is configured with the Oracle user; therefore, the Oracle user must have access rights on the directory specified in the auxiliary instance path. Else, the Agent Utility fails to create the auxiliary directory and you have to manually create the directory and assign read/write access to the Oracle user.
- To display the Oracle database in a Backup Exec server's list of servers on the Backup and Restore tab, type the Backup Exec server name or IP address to which you want the remote computer to publish to.
- When prompted, specify if you want to use a recovery catalog.
The Oracle Agent supports the use of the RMAN recovery catalog to manage the backup, restore, and recovery of Oracle databases. If you choose not to use a recovery catalog, RMAN uses the source database control file as the sole repository of metadata.
The target for RMAN connection is either a target database (control file) or a recovery catalog. In Oracle 12c, RMAN connects to the container database if a recovery catalog is not configured.
If you specify a recovery catalog, any database that you want to back up must be registered in the recovery catalog before you can run backup jobs from the Backup Exec server.
- To use a recovery catalog, type the recovery catalog name and a user name and password for the recovery catalog.
- To use a customized DBA-initiated job settings template, type the name of the template.
- To commit the new entry to the configuration file, type Y, and then press Enter.