Adding an Automatic Database Log Backup Schedule to a Schedule Policy

Applies to: Informix, Microsoft SQL Server, MongoDB, MySQL, Notes Database (traditional log backups), Oracle, Oracle RAC, PostgreSQL, SAP for Oracle, SAP HANA, Sybase, DB2, DB2 MultiNode

You can automatically run a database log backup by adding an automatic schedule to a schedule policy. The database log backup is automatically run when specific criteria are met, for example, run a backup when the archive log destination fills up to a specified capacity. Automatic backups of database log files use the data protection resources more efficiently because they only run backup jobs when there is enough data to back up. A non-automatic schedule runs the backup at the specified date and time, even if there is not enough data to back up.

Take the following into consideration when planning your log backup schedule:

• The number of transactions that the database generates

• The disk size for the log file destination

The Back up on file activity every parameter ensures that the software does not run the job too frequently. The software does not check the database threshold options during this interval.

The Force a backup every parameter ensures that the software backs up the logs even when the database threshold options have not been met. For example, if the parameter is set to 24 hours and the software has not run an automatic log backup in that time, the software will start a backup without checking the database options.

When the Back up on file activity every interval expires, the software checks to see if the database qualifies for a backup based on the log disk usage.

When the Force a backup every interval expires, the software checks to see if the database has been backed up. The software checks the finish time and if it occurred during the Back up on file activity every interval.

If you assign this schedule type to a subclient that has no backups prior to the assignment, the first backup runs irrespective of the database threshold options.

The following best practices apply to all the supported agents:

• Set a low Back up on file activity every interval. For example, set a minimum interval of 15 minutes.

• Set the Force a backup every interval that is less than the time interval between running two backups.

• Set the option to perform a back up when the log destination fills up to 50%-80%. The actual value depends on your storage size.

You can also configure a schedule when you perform a backup on a subclient. For information on how to configure a schedule, see Creating an Automatic Schedule for Database Log Backups.

For the Oracle agent, if an ArchiveLog subclient exists and an automatic database log backup schedule is associated with a client group, client, or agent, an archive log backup is run for the ArchiveLog subclient only. If an ArchiveLog subclient does not exist, a log phase backup is run for the Default subclient.

Best Practice: For some agents, such as Oracle, the Commvault software creates a default archive log subclient. Do not modify the properties of the default archive log subclient.

Before You Begin

Create a data protection schedule policy for your database agents.

Procedure

1. Open your schedule policy:

   1. From the CommCell Browser, expand Policies > Schedule Policies.

   2. From the Schedule Policies pane on the right, right-click the schedule_policy, and then click Edit.

2. On the Association tab, click the Edit tab.

3. To associate entities with the schedule policy, select the check box for the entity.

   For the Informix agent, you must associate the instance to the schedule policy. For other database agents, you can associate at the instance, backup set, or the subclient level.

4. Under Tasks, click Add.

   The Backup Task Options dialog box appears.

5. On the Schedule Pattern tab, select Automatic.

6. In the Back up on file activity every box, enter the interval when the software detects if the database qualifies for a backup. When this time expires, the Commvault software checks the criteria and automatically starts a backup if any of the criteria are met.

7. In the Force a backup every box, enter the interval when the software checks to see if the database has been backed up. If this value is met, the job starts regardless of whether the database criteria are met.

8. On the Databases sub-tab, select the criteria for running log backup jobs:

9. Database	Option
   Informix, Microsoft SQL Server on Windows, Oracle, Oracle RAC, SAP HANA, MySQL, DB2, and DB2 MultiNode	To activate the disk caching of logs feature, select the Use disk cache for log backups and commit every check box and enter the interval of time between each log commit operation to the CommServe server. For more information on the feature, see Disk Caching for Frequent Log Backups.
   MongoDB Oracle Oracle RAC SAP for Oracle MySQL Notes	To run backup jobs when the number of log files on the disk use a specified amount of the storage space, select the Start backup when disk at log destination is option. To run backup jobs when the number of log files on the disk reach a specified number, select the Number of Archived Logs in Log destination option.
   SQL	To run backup jobs when a specified percentage of the log file's storage space is used, select the Start the backup when the log file is option. Note Only databases that use the full recovery model are eligible for the automatic log backups.

10. Click OK.

What to Do Next

To view the jobs associated with this schedule policy, see Viewing Jobs Associated with a Schedule Policy.