Version: DPX 4.9

Considerations for Catalogic DPX Block Data Protection

The following are considerations for Oracle with the Catalogic DPX Block Data Protection:

Block backups and restores for Oracle are executed from the management console.
Oracle must be running in ARCHIVELOG mode during backup and restore.
Do not install Oracle on %SystemRoot% (which is usually the C: drive). Doing so may interfere with Block restore and Instant Access.
The Oracle archive destination variable must be set to a specific location, not the default. The following example shows a setting for a specific location on UNIX or Linux:

SQL> alter system set log_archive_dest_1='location=/db/DB1_arc';

SQL> archive log list;

SQL> alter system switch logfile;

On each Oracle node, after Catalogic DPX has been installed, OracleConfig must be run from the command prompt. See Prerequisites for Protecting Oracle Databases.
TNS Listener process must be running for all operations.
iSCSI Initiator must be installed for all operations that require Instant Access, including RMAN cataloging. See Installation Components and Considerations in the Reference Guide.
The Catalogic DPX Block Data Protection for Oracle requires the installation of the JDBC Driver. For more information, read knowledge base article 43585.
If you expect to do database cloning, the source database must use server parameter file during backup.
Oracle raw volumes, RAC (Real Application Clusters) and ASM (Automated Storage Management) configurations are not supported.
Clusters are not supported for Oracle with the Catalogic DPX Block Data Protection.
The Catalogic DPX Block Data Protection for Oracle is not supported for client nodes running Windows Server 2012 with ReFS enabled. See Microsoft ReFS Support.

Related Topics: