Application software prerequisites

Before Protector can interact with an Oracle Database to protect its data, ensure that your setup meets the following prerequisites:

• Oracle binaries must use separate disks from the database files and log files.
  • They can use any storage including local storage.
• Database files, redo logs and archive logs must use a single supported block storage array per database.
• Database files and redo logs must be in separate ASM disk groups or filesystems
• Database files and archive logs must be in separate ASM disk groups or filesystems
• Redo logs and archive logs can be on the same ASM disk group or filesystem
• ASM disks must be partitioned. The ASM Data must be on the only partition of this disk. This is in accordance to the requirements of Oracle
• When using different filesystems to separate database files, redo/archive logs and binaries they need to use separate disks (LDEVs)

Multiple databases must not share ASM disk groups or filesystems

Block-based backups will only protect a single database per backup. If multiple databases share an ASM disk group or filesystem only the selected database is consistent on the backup and considered during restore and revert. Reverting a configuration with multiple databases on the same disks will lead to corruption of the databases which are not explicitly protected, as their data is reverted together with the selected database.

Special Files

Database credentials

Protector will automatically determine which user to use in order to backup or restore the database. You can however specify custom users for Oracle and ASM related operations.