Protect the database or instance and its logs

After the backup plan is configured as detailed inManage backup templates, you can configure a backup methodfor the database or instance.

Microsoft SQL Server,Oracle, andSAP HANA databaseseach have their own documentation. These other supported database types sharemany procedures.

The following are the other supported database types:

Note: With one exception, protection is set for the entire instance.You can include or exclude specific databases during the process usinga database inclusion rule from theManage Backup Plan page. The exception isthat virtual databases can be protected separately from the instance whencreated.

Protect a database or a database instance

Db2 database instance protection can be done from either the primarynode or from HADR nodes. To protect from a Db2 HADR node, the node mustbe read-enabled. Ensure that the parameterDB2_HADR_ROS=ON is set.

When an SAP ASE database is protected with Full+Incremental based backup,the source and target databases must use the same character set or sort orderfor a successful restore. For details refer toSAP Note: 1860413 - How to change character set or sort order of SAP ASE.

To protect the database or database instance, complete the following:

  1. ClickApp Manager>Applications, right-click the instanceand selectManage Backup Plan.

  2. On theManage Backup Plan page, select a template and a resource profile,then clickApply Backup Plan.

    If you back up a workload to a backup/recovery appliance that would exceed itsrecommended storage capacity or snapshot limit, you will see a notificationwith a recommendation to back up the data to a different backup/recovery appliance.

    Caution: Exceeding the capacity of a backup/recovery appliance can lead to failedjobs and unprotected data and failed restore operations.

  3. ClickDetails & Settings and ensure that the backup capture method matches the type of backup set inManage backup templates.ClickApply backup plan orSave Changes. The instance appears intheApp Manager with a shield icon.

    The instance is protected when the snapshot job succeeds according to theschedule in the template.

  4. If you are protecting an instance, then you can include or excludespecific databases during backup. From theApp Manager, select theinstance. Use the checkboxes to filter the list.SelectManage backup plan.

  5. UnderDatabase Inclusion Rule, clickEdit. If you do notsee theDatabase Inclusion settings, you have selected a database,not an instance.

  6. Select anInclusion Rule—Include All,Include Selected,orExclude Selected—and then select the databases to includeor exclude, then clickSave.

Protect database logs

To enable and set up database log backup, follow these steps:

  1. From theBackup Plans Templates page, right-click the templatethat will be used for protecting the instance and clickEdit.

  2. Click the arrow beside the snapshot policy to open up the details,then clickEdit Policy.

  3. Near the bottom, selectAdvanced Policy Settings.

  4. Set the log policy options—you have to scroll to see them all:

    • EnableTruncate/Purge log after backup.

    • SetEnable Database Log Backup toYes.

    • ForRPO (Minutes), whenEnable Database Log Backup is set toYes, RPO defines the frequency for database log backup. Frequency is setin minutes and must not exceed the database backup interval. The smallestvalue that can be set is 15 minutes.

    • SetLog Backup Retention Period (in Days) for point in time recovery.

    • SetReplicate Logs (Uses StreamSnap Technology) toYes ifyou want to enable StreamSnap replication of log backup to a DR site.

    • SetSend Logs to OnVault Pool toYes if you want the databaselogs to be sent to an OnVault pool, enabling for point-in-timerecoveries from OnVault on another site.

  5. ClickSave Changes.

  6. From theApp Manager Applications list, select the instance.You can use checkboxes on the left to filter the list.Right-click it and selectManage Backup Plans.

  7. At the top of the screen, selectDetails & Settings.

  8. Set theRetention of Production DB Logs in hours. This value isused to purge the logs from the production destination. Based on this setting,the logs are purged if they are older then the number of hours specified.If the default value is not specified, then the default value is 24 hours.

  9. ClickSave.

Note: (SAP ASE only) Only user database transaction logs are backed up; System database transaction logs (including master database transaction logs)are not backed up and so they are not truncated. This means that the system database archive log can get full and cause production user databasebackup jobs to fail. To prevent this, manually clear the systemdatabase logs by running the commanddump tran master with no_log.

What's next

Your databases and instances back up on the schedules set in their backupplans. To review and report on Backup and DR activity, you can view themanagement console dashboardand examine the reports in the report manager.

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2026-02-19 UTC.