You can use the Oracle Agent restore for any of the following data and files:
- Database restore - a restore of the database files, the control file and the server parameter file.
- Database subset - a restore of a combination of any of the following files:
- Archive logs
- The Oracle control file
- The Oracle server parameter file
- Individual datafiles and tablespaces
- The Oracle Flash Recovery Area
- Oracle tables
Note: Table browse is not supported for Oracle Container Databases (CDB).
- Database archived redo logs - a restore of archived redo logs, which are vital for Full System Recovery (Disaster Recovery).
Oracle Standby and Duplicate Databases
In addition to database and file restores, you can use the Oracle Agent restore operation to create a standby or duplicate database. A standby database is a copy of the primary database you create for hardware failures. A duplicate database is an independent copy of the primary database you can use for testing and demonstrations.
You can perform restores through the CommCell Console. The Commvault software creates and runs RMAN scripts, by using the configured options.
You can save your restore options as an RMAN restore script. If the Commvault interface does not support the RMAN commands, or options, you can modify the script. You can run the script through the CommCell console, or use the Oracle recovery manager.
Note: If you are using Oracle Standard Edition database, set the number of restore streams (number of channels specified in the RMAN script) to 1. By default, the Commvault software sets the number of restore streams to 2. Because Oracle Standard Edition only supports one stream, the restore will fail if the number of restore streams is set to 2 or more.
Last modified: 6/6/2020 12:06:34 AM