Enabling Block Backup for Oracle Databases

Take the following steps to enable Catalogic DPX block backups to run with nodes with Oracle Database.

1. Ensure all current software updates are installed.
2. Install and configure the DPX Client on the node with Oracle Database. Follow the relevant installation instructions in the DPX Client section.
3. Run OracleConfig: to open the Catalogic DPX Oracle Configuration dialog.
   • For Windows, open the Catalogic DPX command prompt, selecting Start > Programs > DPX > DPX Command Prompt. Then type OracleConfig.
   • For Linux, navigate to opt/DPX/bin and run OracleConfig.

Note.

Ensure the TNS Listener service is running.

For Linux, the environment variable DISPLAY must be properly set.

The left pane lists Oracle databases detected on the node.
Specify the database configuration in the right pane.

Restrictions.

When specifying passwords, do not use @, as this symbol is restricted in the Oracle Database.

Important.

Configure all databases from the left pane separately. Databases not configured will not be included during backups.

4. If you specify the Optional Recovery Catalog Database information, the database specified will be used during RMAN cataloging.
5. Click Test to check the connection.
6. Click Save.

Oracle Database Backup Workflow

Following is a step-by-step overview of how Catalogic DPX performs Oracle Database backups:

1. Depending on the backup definition, Catalogic Software agents automatically find the file systems hosting the following:
   • data files, ORACLE_HOME, and ORACLE_BASE
   • local archive log locations, redo log locations.
   • the following parameters
     • background_dump_dest
     • core_dump_dest
     • user_dump_dest
     • audit_file_dest
     • db_create_file_dest
     • db_create_online_log_dest_n where n = 1, 5
     • db_recovery_file_dest
     • log_archive_dest
     • log_archive_duplex_dest
     • plsql_native_library_dir
     • spfile
     • standby_archive_dest
     • oracle_trace_collection_path (only 9)
     • oracle_trace_facility_path (only 9)
2. The agent places all the tablespaces selected in backup mode, then Snapshots the file systems. The Snapshots are backed up.
3. The tablespaces are taken out of backup mode.
4. The archive logs generated during the time the database was in backup mode are discovered and backed up.
5. Before tablespaces are put in backup mode, the agent performs the following operations:

   1. Archive all unarchived logs, including the current log.

      ALTER SYSTEM ARCHIVE LOG CURRENT

   2. Query V$LOG to determine the log sequence number of the current redo log, seq1.

      SELECT SEQUENCE# FROM V$LOG WHERE STATUS = 'CURRENT'

      After taking the tablespaces out of backup mode, the agent performs the following operations:

   3. Archive all unarchived logs, including the current log.

      ALTER SYSTEM ARCHIVE LOG CURRENT

   4. Query V$LOG to determine the log sequence number of the current redo log, seq2.

      SELECT SEQUENCE# FROM V$LOG WHERE STATUS = 'CURRENT'

6. The archive logs ranging from seq1 up to but not including seq2 are backed up. In addition to the archive logs, the following files are explicitly backed up:
   • Control file (binary) generated after taking tablespaces out of backup mode
   • Text control file
   • Text parameter file is included in the backup if the database instance is using a server parameter file
7. The file systems containing all Oracle information are backed up, including Oracle configuration files, such as network configuration files and password files, and all archive logs are protected.