Oracle Archived Log Settings

In this article

    The Oracle tab applies to VMs that run Oracle and if you have selected Process transaction logs with this job when configuring application-aware processing.

    To configure how Veeam Backup & Replication must process archive logs of an Oracle server:

    1. At the Guest Processing step of the wizard, click Applications.
    2. In the Application-Aware Processing Options list, select a VM that runs Oracle.
    3. Click Edit.
    4. In the Processing Settings window, switch to the Oracle tab.
    5. From the Specify Oracle account with SYSDBA privileges drop-down list, select a user account that Veeam Backup & Replication will use to connect to the Oracle databases. The account must have SYSDBA rights on the Oracle database.

    You can select Use guest credentials from the list of user accounts. In this case, Veeam Backup & Replication will use the account specified at the Guest Processing step of the wizard to access the VM guest OS and connect to the Oracle databases. Note that this account must be a member of specific groups or granted specific privileges. For more information, see Required Permissions.

    1. In the Archived logs section, specify how to process archived logs:
    • If you want to preserve archived logs on the VM guest OS, select Do not delete archived logs. When the replication job completes, the non-persistent runtime components or persistent components will not truncate transaction logs.

    It is recommended that you select this option for databases where the ARCHIVELOG mode is turned off. If the ARCHIVELOG mode is turned on, archived logs may grow large and consume all disk space.

    • If you want to delete archived logs older than <N> hours, select Delete logs older than <N> hours and specify the number of hours.
    • If you want to delete archived logs larger than <N> GB, select Delete logs over <N> GB and specify the size. The specified size refers to the log size of each database, not all databases on the selected Oracle server.

    The non-persistent runtime components or persistent components running on the VM guest OS will wait for the replication job to complete successfully and then trigger transaction logs truncation using Oracle Call Interface (OCI). If the job does not manage to replicate the Oracle VM, the logs will remain untouched on the VM guest OS until the next start of the non-persistent runtime components or persistent components.

    To configure archive log handling for multiple VMs at once, do the following:

    1. At the Guest Processing step of the wizard, click Applications.
    2. In the Application-Aware Processing Options list, select multiple VMs.
    3. Click Edit > Oracle.
    4. Configure options described in the previous list.

    Oracle Archived Log Settings