Backup Exec 20.2 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
- Instant Cloud Recovery
- Preconfigurations to be completed in the Azure portal
- 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
- 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
About restoring Oracle resources
The Oracle Agent lets you restore Oracle databases, tablespaces, or datafiles. You can restore items to their original location or you can redirect the restore to a new location. The restore selections that you choose in Backup Exec are converted to a script. RMAN uses the script to determine what to restore from the Backup Exec backup set. After the data has been restored to the Oracle server, RMAN completes any requested recovery and restore operations. The options you select determine the recovery and restore operations.
Some recovery operations may not require media from the Backup Exec server. For example, the redo logs may still be on the Oracle server. During a restore operation, the amount of data that is restored may not be equal to the amount of data that is backed up. In some cases, the amount of data that is restored is listed as 0 bytes. This behavior is normal because Oracle might skip the datafiles that are already up-to-date on the disk.
Backup Exec Agent for Oracle does not support the restore of a resource if you back up the resource on a different storage media. For example, you cannot restore an Oracle database if you have done a full backup of the Oracle database using the Backup-to-disk option on a device that is attached to the Backup Exec server and an incremental backup of an Oracle database on a Remote Media Agent device.
If you perform a complete recovery on the whole database, or on a tablespace or datafile, you must restore a backup of the database or files that you want to recover. Then you must apply online or archived redo logs, or both. For the jobs that are initiated both from the Backup Exec server and from a DBA, RMAN determines the specific data that it requires from Backup Exec to complete the restore and the recovery that you request.
Backup Exec does not support Oracle tablespace point-in-time restore (TSPITR) through server-initiated operations.
Backup Exec does not support restore from storage device media and from backup sets for the Oracle Agent because during restore, RMAN determines which backup sets are needed for the job.
For Oracle 12c and later databases, Backup Exec supports Oracle pluggable database point-in-time restore (DBPITR) through server-initiated and DBA-initiated operations.
The point-in-time (PIT) restore job of the root fails with an error message: "Specifying CDB$ROOT database is not supported". This feature is not supported by Oracle.
For Oracle 12c and later, root is displayed as a Tablespaces node in the backup browse and restore view. To restore the root, select the Tablespaces node under the control file node in the Details File view.
You can recover only the root if a data corruption or user error occurs that affects only the root. However, Oracle recommends that you recover all PDBs after recovering the root to prevent metadata inconsistencies among the root and the PDBs. In such a case, it is preferable to perform a complete recovery of the whole CDB.
The Oracle agent retains the state of the pluggable databases (PDBs) as they were before the restore job. After the restore, the agent brings the PDBs to the same state as they were before the restore job.
All states such as OPEN, MOUNTED, READ-ONLY, and READ/WRITE are retained except MIGRATE. If any PDB was in the MIGRATE state before the restore job, then after the restore that state of the PDB changes to MOUNTED.
You can only choose Oracle restore selections from the Resource View in the Restore Wizard. The Details View displays backup sets, but you cannot browse or select the contents.
On the Resource View, you can make restore selections from the online database or from control files.
Table: Restore selections for Oracle resources
View restore data in
Provides a view of the live database (if available). You can select an entire database or select individual tablespaces and datafiles.
For an Oracle 12c database, this view displays the pluggable databases, the Tablespaces node, and the archived logs at the same level. In this view, you can select the whole tablespace and individual data files for restore, but you cannot select the pluggable databases and the archived logs nodes for restore.
For Oracle 12c, Backup Exec supports restore and recovery of one or more tablespaces and data files of a PDB. Redirect restore of a PDB on the same host to a different path is supported. However, point-in-time restore of tablepsaces and redirected restore of a PDB to a new host are not supported.
For Oracle RAC, the Oracle database is listed under its fully qualified domain name. It is in the form RAC-<database name>-<database ID>.
Provides a list of all backed up control files. Each control file lists the date it was backed up and the control file's piece ID.
You cannot select individual tablespaces or datafiles for restore.
For an Oracle 12 database, in this view, you can select only the control file node and the pluggable database nodes for restore. If you select the control file node for restore, the entire CDB is restored. This restore data includes all data that is related to the CDB and all PDBs. This data is restored and recovered to the PIT specified in the restore job. This feature is the same as the control file restore of a non-CDB database.
If you select an individual pluggable database, only the selected PDB is restored.
When you recover to a point in time by using a control file, ensure that the date of the control file backup is before the specified recovery point in time. There should not be any database structure changes between the two times. Additionally, when you restore a control file, the entire database reverts to the point in time of the restored control file.