Preparing Application-Consistent Backup

To provide for recoverability of Oracle database, make sure you have an application-consistent backup of your Oracle server machine created successfully. For more information on an application-consistent backup, see Application-Aware Processing. Also, if you plan to restore the database to its state as of the certain point in time (not necessarily the restore point, that is, backup or replica), then log processing should be configured, as described below.

To configure job settings:

  1. Go to the Jobs tab and select your Oracle server backup job.
  2. Click Job on the toolbar and select Edit to start the job wizard.
  3. Proceed to the Guest Processing step of the wizard and make sure the Enable application-aware processing check box is selected.
  4. Click the Customize Application link. In the displayed window, select the Oracle server machine from the list and click Edit.
  5. On the General tab, make sure the Require successful processing option is selected in the Applications section.
  6. To be able to specify transaction log handling options, make sure the Process transaction logs with this job option is selected. Otherwise, if you select the Perform copy only option, Veeam Backup & Replication will create a copy-only backup, and Oracle archived logs will not be deleted — that is why the Oracle tab with log handling settings will be deactivated in this case. For more information, see the Oracle Archived Log Settings section of the Veeam Backup & Replication User Guide.


If both Microsoft SQL Server and Oracle are installed on one machine, and this machine is processed by a job with log backup enabled for both applications, Veeam Backup & Replication will back up only Oracle transaction logs. Microsoft SQL Server transaction logs will not be processed.

Application-Aware Processing Settings

  1. Open the Oracle tab and specify how archived logs will be handled:
  1. Specify a user account that will connect to Oracle system and perform Oracle archived logs backup and\or deletion. You can select Use guest credentials — then Veeam will use the account specified for guest processing in the job configuration for both guest OS access and for connection to the Oracle system. You can also specify another account. To do this, select the necessary account from the drop-down list or click Add and add a new account. In any case, make sure the account you specify has sufficient rights. For details, see the Required Permissions section of the Veeam Explorer for Oracle guide.
  2. Specify whether archived logs should be deleted on the Oracle server machine, and whether Veeam should back them up them to repository. Veeam Backup & Replication supports the following options:
  • Do not delete archived logs — this option instructs Veeam to preserve archived redo logs (if any) on the original Oracle server. With this option selected, your database administrator will have to take care of database logs. Applicable restore scenario — database restore to the state as of the currently selected machine restore point, to the selected point in time and to the selected transaction.
  • Delete logs older than <N> hours / Delete logs over <N> GB — with this option selected, Veeam will wait for the image-level machine backup to complete, and then it will trigger archived log deletion from guest, using the specified condition (log age or size). If archived logs cannot be deleted for some reason, these logs will remain untouched in the guest machine until the next start of the Veeam runtime process.
  • With any of these options, you can also use the Backup logs every <N> minutes check box. If you select this check box, Veeam Backup & Replication will periodically ship archived logs to the backup repository and store them next to the Oracle server machine backup. Make sure that Oracle ARCHIVELOG mode is turned on (contact your database administrator, if necessary). This option will support any database restore scenario: to the state as of in currently selected machine restore point, to any point in time or to the state before particular transaction.


If you plan to use this option together with archived logs deletion from Oracle machine guest, make sure that these settings are consistent: logs should be deleted after they are backed up to repository, not vice versa. Thus, you need to set up backup schedule and log removal conditions appropriately. Default log backup interval is 15 minutes, maximum interval is 480 minutes.

Handling Archived Logs

  1. If you selected to back up archived logs, specify how long they should be kept using the Retain log backups options.

Select the Until the corresponding image-level backup is deleted option, so that you do not have to manually check and ensure that your database and log backup retention policies are consistent, providing all the machine restore points and log backups required for database restore.

  1. Click OK to save the settings and close the window.
  2. At the Job Schedule step of the wizard, make sure the schedule is enabled for the job. Otherwise, log backup will not be activated.
  3. Click Finish.