Restoring an Oracle database is crucial for recovering data after an incident, ensuring the continuity and integrity of business operations. Catalogic DPX offers a flexible and efficient approach to Oracle database restores, supporting various recovery options to meet your specific needs.
In the main web interface view, go to Job Manager in the sidebar. Then select the New Restore Job button.
Select Application Restore and Click Next.
The Object to Restore view shows all Application nodes that you backed up. The available objects to restore can be sorted by Name, Type, associated Job Name, or the backup Date/Time. Locate and select the node containing the Oracle DB you want to restore and click Next.
Tip. Restoring an Oracle DB object will include all local volumes referenced by the object, potentially increasing the restore size.
Choose the appropriate recovery point from the available backups of the selected node.
In the File Browsing step, choose the specific databases you wish to restore. DPX allows for granular selection, enabling you to restore individual databases. Select all databases you want to restore and click Next.
When browsing the file tree of a block backup for Oracle DB, you will see two separate directories: Physical View and Logical View. The physical view represents the actual physical implementation of the database on the storage system, while the logical view provides a structured representation of the database objects and their relationships.
In the Options step, specify the Job Name. The name may be up to 64 characters long and may only contain letters, digits and -
_
characters.
Specify job options. You can use the following options:
When performing Oracle logical view restores, you can choose from the following modes:
Specify a complete directory path to be used as the root directory for all mappings during a Quick Restore for Oracle. If this value is not set, it defaults to:
For Windows: product-directory/mount/BEXrmancat_jobid/nodename/dbname
For UNIX: /tmp/BEXrmancat_jobid/nodename/dbname
This option is used when cloning Oracle databases. Specify the Oracle_Home
on the target node where the cloned database will reside.
When cloning Oracle databases on a UNIX target node, supply the user name of the owner of the Oracle installation on the restore destination node. If this field is not populated, the default value oracle
will be used.
For cloning Oracle databases on a Windows target node, provide a password to create an Oracle instance on the target node. If this field is not populated, the default value sysadmin
is used.
Note. The Oracle Instance Password may appear in clear text in certain files and modules. Once cloning is complete, the password must be changed by the user.
This option is used with the cloning of Oracle databases. It allows you to control whether the cloned Oracle database should be opened and in what mode. The available options are:
See also. To learn more about other available options, see Advanced Job Options.
Click Next. Review the summary of your job and click Save. You will see the Run Job prompt.
Click Yes to run the job immediately, or No if you want to run it later from the Job Manager.
Toggle on
The restore job defined in this process will be deleted upon successful completion. If the job fails, it will not be deleted.
Toggle off
The restore job will be saved and will be accessible later in Job Manager.
Toggle on
The notification is sent as specified below the toggle (additional fields will appear – see below).
Toggle off
The notification is sent to the default e-mail address configured in the Administrator E-mail Settings section.
Regular
This is the default mode. It performs a standard logical view restore.
Clone Database
This mode performs a cloning operation, recovering your backed-up data on an alternate node using Instant Access.
Quick Restore
This mode performs an Instant Access mapping to your backed-up data, allowing for rapid access and recovery.
Open Reset Logs
This is the default setting. Opens the Oracle database with the resetlogs
option.
Open Read Only
Opens the Oracle database in read-only mode.
Do Not Open
Does not open the Oracle database, which can be useful if further recovery is needed.