-
Title
Oracle Database 12c Application Support -
Description
Rapid Recovery release 6.2 expands application support to include Agent-based protection of Oracle 12c relational database servers. You can protect an Oracle database server and all of its databases, and perform related tasks.
Once you install the Agent, protect the machine in your Core, and configure settings properly, you can do the following:
- View metadata: From the protected machine Summary page, you can view metadata about each database on your Oracle server, including connection and status for each child log and transaction file.
- Check database integrity: You can perform integrity checks from the Core Console using the DBVERIFY utility.
- Truncate archive logs, using one of three deletion policies.
- Restore databases: Restore entire volumes, all databases or select databases. Once you enable Archive log mode, snapshots of the Oracle database are crash-consistent from the point of view of the Oracle service.
Perform virtual export: You can make a one-time export, or set up a virtual standby VM that continually updates a VM with new information as backups on your protected database are captured
Note: If you boot up a VM of an Oracle database, you may have to manually start the database services.
-
Resolution
There are certain considerations to be made when protecting a Windows server with an Oracle Database.
- Oracle 12c is the ONLY tested and supported version for protection on the Rapid Recovery Core. Use of any other Oracle version is at your own risk.
- Windows Server 2012 R2 x64 and Windows Server 2016 are the only supported operating systems for protected Oracle database servers with Rapid Recovery. Linux OS support is planned for a future release.
- The Rapid Recovery Agent software (version 6.2 or later) is necessary. Agentless support is planned for a future release.
- Protection of Oracle 12c databases is limited to using Volume Snapshot Service (VSS) in the ARCHIVELOG mode. Support for NOARCHIVELOG (the default Oracle database log mode) is planned for a future release.
- Oracle databases with ARCHIVELOG mode enabled must also be set to archive all online redo logs using the ARCH (archive) process. A database administrator (DBA) can change the mode and set archiving of redo logs using Oracle SQL*Plus or Oracle Enterprise Manager. For more information about enabling ARCHIVELOG mode and archiving, see Oracle documentation or consult a qualified Oracle 12c DBA.
To fully protect Oracle servers, perform the following tasks:
- Install the Rapid Recovery Agent software (release 6.2 or later) on your Oracle server and begin protection. Use the Protect Machine Wizard to locate the Oracle server on your network, deploy the Agent software, and establish a protection schedule. (For more information, see About protecting machines with Rapid Recovery.)
- Enter credentials for each database in the Rapid Recovery Core Console. The Core securely caches your credentials and lets you access the metadata from the UI. Before you enter credentials, you cannot view details for databases on your protected Oracle server. (For more information, see Entering or editing credentials for Oracle databases.)
- Enable Archive log mode for the protected Oracle server, and verify the Oracle VSS writer, from the Core Console. (For more information, see Enabling archive log mode and adding VSS writer for protected Oracle databases.)
- Review log truncation policy and configure as necessary. When an Oracle database is set to archive log mode, the logs accumulate quickly and consume substantial disk space. For this reason, a nightly job is set by default to automatically truncate Oracle logs. You can configure three deletion options for this nightly job, or you can disable the nightly job. (For more information, see About truncating Oracle logs.) You can also truncate Oracle database logs manually on demand. (For more information about this procedure, see Manually truncating Oracle database logs.)