Chat now with support
Chat with Support

Welcome, ApexSQL customers to Quest Support Portal click here for for frequently asked questions regarding servicing your supported assets.

Rapid Recovery 6.3 - User Guide

Introduction to Rapid Recovery The Core Console Repositories Core settings Managing privacy Encryption Protecting machines
About protecting machines with Rapid Recovery Understanding the Rapid Recovery Agent software installer Deploying Agent to multiple machines simultaneously from the Core Console Using the Deploy Agent Software Wizard to deploy to one or more machines Modifying deploy settings Understanding protection schedules Protecting a machine About protecting multiple machines Enabling application support Settings and functions for protected Exchange servers Settings and functions for protected SQL servers
Managing protected machines Credentials Vault Snapshots and recovery points Replication Events Reporting VM export Restoring data Bare metal restore
About bare metal restore BMR Windows and Linux Understanding boot CD creation for Windows machines Managing a Linux boot image Performing a bare metal restore using the Restore Machine Wizard Using the Universal Recovery Console for a BMR Performing a bare metal restore for Linux machines Verifying a bare metal restore
Managing aging data Archiving Cloud accounts Core Console references REST APIs Glossary

Enabling archive log mode and adding VSS writer for protected Oracle databases

Before performing this procedure, you must first add an Oracle database server to protection on your Core, and enter credentials for each database into the Core Console.

Database applications require the presence of a combination of specific files (such as configuration, log, and control files), each set to a specific state, to be able application-consistent. In Rapid Recovery Core release 6.2 and later, Oracle databases require archive log mode to be enabled. Until you perform this procedure, your snapshots of the database server will be crash-consistent, but not application-consistent.

Oracle VSS writer captures snapshots using Volume Snapshot Service. This writer must be enabled.

NOTE: These are one-time steps required for each new protected Oracle database.

Complete the steps in this procedure to verify if archive log mode is enabled; to enable that mode if required; and to add VSS writer to your Core.

  1. Navigate to the protected Oracle machine in the Rapid Recovery Core Console.
    The Summary page displays for the protected machine.
  2. On the Summary page, scroll down to the Oracle Server Information pane.
  3. In the Oracle Server Information pane, if you see a warning notification that archive log mode is disabled, click Enable archive log mode for these databases and then click to confirm restart of the database instances.

    NOTE: Enabling archive mode causes the relevant database instances to restart. This could take a few minutes.

  4. In the Oracle Server Information pane, if you see a warning notification that the Oracle VSS writer is excluded from snapshots, click Include Oracle VSS Writer and then click to confirm.
    The warning message closes, and the VSS writer is added to your Core.
  5. Optionally, you can track the progress towards enabling archive log mode or adding a VSS writer. For more information, see Viewing tasks.

About truncating Oracle logs

Currently, protection of Oracle 12c databases in Rapid Recovery Core release 6.2 and later is limited to using Volume Snapshot Service (VSS) in the ARCHIVELOG mode. In this mode, the database is configured to archive all online redo logs using the ARCH (archive) process. The Oracle VSS writer calls the Oracle service to archive the existing re-do logs to Oracle's fast_recovery_area folder, and creates a new archive log file.

ARCHIVELOG mode causes a substantial number of log files to accumulate on the database server, using valuable storage space. Each time a recovery point of the Oracle server is captured, the new Oracle logs generated since the last snapshot are included. This renders the local copies of the logs superfluous. For this reason, Rapid Recovery Core includes several methods for truncating Oracle logs.

  1. Enable Oracle log truncation on the Core as a nightly job. Rapid Recovery Core includes a nightly job setting called Log truncation for Oracle.This nightly job is disabled by default. If you enable this nightly job, Oracle ARCHIVELOGS are truncated according to the deletion policy specified in the settings for this job.
  2. Enable and customize Oracle log truncation as a nightly job. For each specific Oracle server protected on your Core, you can customize the Oracle log truncation nightly job configuration. As with the Core nightly job, you can select from any of the three deletion policies, described in the following section.
  3. Manually truncate logs on demand. Regardless of whether you set a log truncation schedule using nightly jobs, you can manually truncate Oracle ARCHIVELOGS on demand at any time.

Truncation of Oracle logs, by nightly job or on demand manually, occurs without requiring a transfer job.

When you specify truncation of Oracle logs by nightly jobs, truncation occurs according to the deletion policy at the time nightly jobs are scheduled to occur. Conversely, when you elect to manually truncate Oracle logs, a log truncation job queues. If the system is not busy, the job executes immediately and the logs are truncated.

Deletion policies for Oracle log truncation

When configuring log truncation for Oracle database servers, you can choose from one of three deletion policies:

  • The Automatic deletion policy truncates all Oracle ARCHIVELOGS stored in the fast_recovery_area folder one time daily when nightly jobs run.
  • The Keep newest deletion policy lets you specify the duration of time (n days, weeks, months, or years) to retain the Oracle logs before truncating. When the time period expires, log files past the threshold are then truncated one time daily when nightly jobs run.
  • The Keep specified number deletion policy lets you specify a specific number of log files to retain. After that threshold is reached, newer logs are retained, and the older logs are then truncated one time daily when nightly jobs run.

If you need a truncated ARCHIVELOG file, you can obtain it from the latest recovery point captured prior to truncating the logs.

For more information about truncating jobs as a nightly job, see the topic Understanding nightly jobs.

For more information about manually truncating Oracle logs on demand, see Manually truncating Oracle database logs.

Manually truncating Oracle database logs

This procedure is only appropriate for Oracle database severs protected on your Core.

When protecting an Oracle database in ARCHIVELOG mode, substantial log files accumulate on the local database server. To support the protection of Oracle databases in Rapid Recovery, you can enable a nightly job to truncate Oracle logs.

NOTE: Log truncation for Oracle is disabled by default.

For any protected Oracle server, you can also manually truncate Oracle database logs on demand at any time, as described in this topic. Truncating will delete the logs from the local server. In each recovery point saved to your repository, the database logs persist to reflect the state of the database at the time the backup snapshot was captured.

Complete the steps in this procedure to manually truncate Oracle log files.

  1. Navigate to the protected Oracle machine in the Rapid Recovery Core Console.
    The Summary page displays for the protected machine.
  2. On the Summary page, scroll down to the Oracle Server Information pane.
  3. In the table row representing the Oracle database instance for which you want to truncate logs, click the [More options] (More options) drop-down list and select Force Log Truncation.
    The Force Log Truncation dialog box displays.
  4. If you want to delete all of the Oracle logs from the local database server, from the Deletion policy drop-down menu, select Automatic, and then click Force.
    A log truncation job queues. If the system is not busy, the job executes immediately and the logs are truncated.
  5. If you want to delete all of the locally stored logs from the Oracle server (copies of which are stored in the most recent recovery point), do the following:
    1. From the Deletion policy drop-down menu, select Keep newest.
    2. In the Keep logs for text field, enter a number, and then from the time period drop-down menu, select the relevant a period of time (days, weeks, months, or years).
    3. Click Force.
      A log truncation job queues. If the system is not busy, the job executes immediately and the logs are truncated.
  6. If you want to keep a specific number of Oracle log files, and truncate the remaining logs, then do the following:
    1. From the Deletion policy drop-down menu, select Keep specified number.
    2. In the Number of archive files text field, enter a number representing the amount of the newest database logs to retain.
    3. Click Force.
    A log truncation job queues. If the system is not busy, the job executes immediately and the logs are truncated.
  7. If you want to truncate logs for other database instances on this server, repeat step 3 through step 6 for each relevant database listed in the Oracle Server Information pane.

About managing Exchange and SQL servers in Rapid Recovery Core

Options specific to Exchange Server and SQL Server appear in the Rapid Recovery Core Console only when an instance of the software and related files are detected on protected servers. In those cases, additional options are available when you select the protected machine in the Core Console.

For example, if you select a protected Exchange server in the left navigation menu, then the menu options that appear for that protected machine include an Exchange drop-down menu option.

If you select a protected SQL server in the left navigation menu, then the menu options that appear for that protected machine include a SQL drop-down menu.

While these options may work differently, there is some commonality. Functions you can accomplish for protected Exchange and SQL servers (and for no other protected machines) include:

  • Forcing server log truncation. Both SQL servers and Exchange servers include server logs. The process of truncating SQL logs identifies available space on the server. When you truncate logs for an Exchange server, in addition to identifying the available space, the process frees up more space on the server.
  • Setting credentials for the relevant server. Exchange servers allow you to set credentials for the protected machine on the Summary page for the protected server. SQL servers allow you to set credentials for a single protected SQL Server machine, or to set default credentials for all protected SQL servers.
  • Viewing status for checks on recovery points from Exchange Server or SQL Server. Recovery points captured from a protected SQL or Exchange server have corresponding color status indicators. These colors indicate the success or failure of various checks relevant for SQL servers or Exchange servers.

This section includes the following topics specific to managing protected machines that use Exchange Server or SQL Server:

Related Documents