Backup Exec 20.1 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)
- Backup Exec license contract information
- About upgrading to Backup Exec
- Getting Started
- Backups
- Backing up data
- Restores
- How Backup Exec catalogs work
- Job management and monitoring
- 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
- Reports
- 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
- 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
- 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
- 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 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
Performing a redirect restore of an Oracle 12c database using Backup Exec
Database using an OMF (Oracle Managed File)
Restoring the database to the same path on a new host
Before running the restore job, ensure that the folder structure on the new Oracle server is same as the original database. In case of an OMF database, PDB folders are created as GUIDs; therefore, you have to manually create the same folder structure as the original database.
Restoring the database to a different path on a new host
You can specify the redirect restore path in the Backup Exec UI. Oracle Agent creates the folder structure using PDB names in the redirect restore path you specified and restores the data in the appropriate folders.
For example, the redirect restore path you specified in Backup Exec is
C:\Redirect
. The CDB that you want to restore has two PDBs namely, PDB1 and PDB2. These PDBs have GUID-based folders in the original database. After the restore, data is restored to the following locations:PDB1 data is restored in
C:\Redirect\PDB1
PDB2 data is restored in
C:\Redirect\PDB2
PDB$SEED data is restored in
C:\Redirect\PDB$SEED
ROOT data is restored in
C:\Redirect\ROOT
Note:
If the Oracle agent fails to create the directory structure, the restore job fails with an error asking the user to create the structure manually.
Database not using an OMF
Restoring the database to the same path on a new host
Before running the restore job, ensure that the folder structure on the new Oracle server is same as the original database.
Restoring the database to a different path on a new host
You can specify the redirect restore path in the Backup Exec UI. Oracle Agent creates the folder structure using the PDB names in the redirect restore path you specified and restores the data in the appropriate folders.
For example, the redirect restore path you specified in Backup Exec is
C:\Redirect
. The CDB that you want to restore has two PDBs namely, PDB1 and PDB2. These PDBs have name-based folders in the original database. After restore data is restored to the following locations:PDB1 data is restored in
C:\Redirect\PDB1
PDB2 data is restored in
C:\Redirect\PDB2
PDB$SEED data is restored in
C:\Redirect\PDB$SEED
ROOT data is restored in
C:\Redirect\ROOT
Note:
If the Oracle agent fails to create the directory structure, the restore job fails with an error asking the user to create the structure manually.
Note:
Backup Exec does not support redirect restore of a PDB to a new host. However, Backup Exec supports redirect restore of a PDB on the same host to a different path.
By default, RMAN restores the datafiles in the same location from which it was backed up.
The database directories and paths are not created from RMAN, but they must pre-exist.
Delete the redo logs before starting the restore job because on-disk redo log are not useful. If you do not delete the redo logs, restore job might fail with the following error:
ORA-19698: C:\APP\ORAUSER\ORADATA\STRING\REDO01.LOG is from different database: id=nnnnnn, db_name=STRING
If you want to restore the database to the same path on a new host, make sure that the directory structure is same as the original database. However, if the redirect restore is to a different path on a new host, the Oracle Agent creates the directories on the new path.
Follow the procedure to use a new Oracle server to recover the complete Oracle instance or database after it has been lost, deleted, or destroyed.
Performing a redirect restore of an Oracle 12c database using Backup Exec
- Recreate the Oracle database using the same name of the original database that is no longer available.
- Locate and rename the
pwd<SID>.ora
file. Make note of the path to this file for use in Step 3b. - Create a new
pwd<SID>.ora
file using the following steps:Open a command prompt.
Type the following command
orapwd file="path from Step 2"\pwd<sid>.ora password=<password>
For example, C:\> orapwd file=c:\oracle\product\12.1.0\db_1 \database\pwdORCL1.ora password=NEWpassword
Note:
Backup Exec Remote Agent must be installed and configured for Oracle database access.
- In the command prompt, type the following command
SQLplus / as SYSDBA
- Type SHUTDOWN IMMEDIATE;
- Type STARTUP NOMOUNT;
- Exit Sqlplus and launch RMAN from the command prompt.
- Type SET DBID=dbid ID;
Note:
This dbid must be identical to the dbid from the original Oracle instance. When complete, type EXIT.
- On the Backup Exec server, on the navigation bar, click the arrow next to Restore, and then click New Restore Job.
- In the Properties pane, under Source, click Selections.
- Select the appropriate control file to restore.
- In the Restore job properties pane, under Destination, click Oracle Redirection.
- Select the Restore Oracle instance to server check box. Enter account credentials to access the new or the alternate Oracle server.
If the Oracle datafiles and archive logs are stored on a different location on the target server, enable the Redirect Oracle files to path option, and specify the valid paths for the datafiles and archive logs. Click Run Now to run the restore job.
Note:
The restore job fails because the recovery portion encounters inconsistent archive logs. This is a normal occurrence during a disaster recovery.
- On the Oracle server, start SQLplus / as SYSDBA from the command prompt.
- Type alter database open resetlogs;
If an error is encountered while Oracle tries to open the database, document the online redo log path, and then update the path using these steps:
On the Oracle server, open the command prompt and type the following command:SQLPLUS /nolog
Type connect<sys/password@SID>;
Type the following SQLPlus command:
SQLPLUS ALTER DATABASE RENAME FILE <old path from backup to any redolog file name> to <path to expected restored redolog file name>;
For example, ALTER DATABASE RENAME FILE 'D:\ORACLE\ORADATA\JACOB\REDO01.LOG' to 'C:\ORACLE\ORADATA\JACOB\REDO01.LOG';
In the command prompt, type RMAN, and then type the following command in the RMAN prompt:
alter database open resetlogs;
Close the command prompt.
The recovery is complete.