Page Comparison

Job Execution Overview

A job can be initiated using any of the following methods:

• Manually – by launching the job from the console and selecting to execute it immediately
• Scheduled – either an independent schedule or a schedule policy
• Save as a script – to be later executed by a user or by an external automated scheduler

Scheduling

Most data protection jobs use traditional backups or snapshots are scheduled. The frequency of scheduled jobs should be based on the RPO times. For a 24 hour RPO, jobs are scheduled to run daily. If a four hour RPO is required, then jobs should be scheduled to run every four hours.

Different types of jobs can be scheduled to run on different days. The traditional weekly full and daily incremental is the most common schedule, but not always the best. Consider scheduling jobs based on RTO, RPO and how frequently data should be sent off-site.

For example, if data is being backed up to disk and DASH copied to disk at a DR location, jobs can be scheduled to run more frequently throughout the day to shrink RPOs and send data off-site faster. If the disk data needs to be consolidated to tape on a monthly basis, a schedule of monthly full and daily incremental with the monthly full being Aux copied to tape may be an adequate solution. Another example is when performing a backup directly to tape. A schedule of nightly full backups or weekly full and nightly differential can be implemented. Both methods may shrink RTO times.

Auxiliary copies are as important to properly schedule as data protection jobs. If the corporate requirement is a four hour RPO for critical databases, and the database backup running every four hours is DASH copied only once a day, it can lead to an SLA not being met in case of a disaster, where the primary disk library is lost.

Commvault^® software uses a standard scheduler for scheduling all operations within the CommCell^® environment. The following is a list of operations that can be scheduled:

• Data protection operations
• Data recovery operations
• CommServe DR backup
• Reports
• Data Aging

Schedule Frequency

Jobs can be configured to run once or repeat based on setting the following frequencies:

• Daily – jobs are set to start and end at a certain time each day. A repeat interval can be configured to have the job run multiple times per day with an hour and minute recurrence interval.
• Weekly – jobs are configured to run on specific days of the week or set to repeat every fixed number of weeks. Exceptions can also be added, for example if a job is to be scheduled to run every Friday except for the last Friday of the month, set the weekly schedule to run on Friday, repeat every week, and set an exception for the last Friday of the month.
• Monthly – jobs are configured to run based on the following criteria:
  • On the first, second, third, fourth or last day of a month.
  • The day of the month specified can be a day of the week, specific day, weekday or weekend day.
• Yearly – jobs are configured to run based on the following:
  • Specific day of a specific month.
  • On the first, second, third, fourth or last day of a specific month.
  • The day of the month specified can be a day of the week, day, weekday or weekend day.
• Automatic – schedules are used for protecting end user workstations or automatically scheduling specific database application log backups, such as SQL or Oracle.
• Continuous – is a schedule in which an interval between job is defined.
  • The first job is executed
  • Starting from that point on, as soon as it completes, it waits for the time interval to elapse and launches the job again.

Independent Schedules

Right-click the subclient | Click Backup | Job Initiation section

Jobs can be scheduled to run independently. An independent schedule is created at the client level, and is used only by that client. It is initiated from the Job Initiation section of a job. All backup or auxiliary copy options can be defined for the job.

There are several schedule patterns that are used, but one frequently used for independent jobs is the One-Time pattern. It executes an on-demand job later, without having to manually launch it.

Create a Schedule Policy - Demo

Schedule Policies

Expand Policies | Right-click Schedule Policies | Click New Schedule Policy

Jobs can be scheduled to run by using schedule policies. A schedule policy is a set of rules containing one or many schedules. This set of schedules is deployed to multiple systems or storage policies requiring a similar schedule pattern for backups or auxiliary copies. This helps in managing and controlling the schedules in bulk.

At any time, subclients or storage policies can be added or removed from a schedule policy. It is also possible to manually execute a schedule from the schedule policy, which simultaneously launches backups on all systems associated with it.

To effectively manage your jobs, use schedule policies whenever possible.

Schedule and Schedule Policy Settings

The following table displays the schedule and schedule policy settings:

Automatic Schedule

Commvault^® software provides the ability to control the execution of jobs using an automatic schedule. The automatic schedule uses criteria which, when met, triggers the execution of the task automatically. Automatic schedules are used for three specific examples:

• Laptop backups
• Database backups
• Auxiliary Copy

Tip: How to Ensure the Data is Sent Off-site
Most jobs run once during the day while normal schedules can be used for auxiliary copies. The automatic copy allows you to set a check interval for source data to be copied. This is an advantage when jobs are run multiple times per day, or if you are unsure when the source data will become available for copy.

Example: A critical database is running transaction log backups every four hours. You want to run an auxiliary copy of the source transaction logs to a secondary location, in this case a disk library off-site.

Solution: Schedule the transaction logs to back up every four hours. Then set the automatic auxiliary copy option to check for source data in much shorter intervals. If source data is present, the auxiliary copy runs creating an additional copy of the data.

Automatic Laptop Backup

Right-click a schedule policy | Click the General tab | Add | Schedule Pattern tab | Automatic | Laptop subtab

The protection of mobile users' laptops is controlled through an automatic schedule that uses criteria, such as available bandwidth, AC power, or if the laptop is idle. This ensures that backups are executed when the computer is under ideal condition.

When setting up the criteria for laptop backups, two values must be set for intervals between jobs, which are as follows:

• Detect file or log activity every – This is the minimal time between two consecutive backup jobs. The default value is 15 minutes. If the laptop has been protected more than 15 minutes ago, and if it meets all requirements, such as available bandwidth, AC power, etc., it is then protected.
• Run the backup every – This is the maximum acceptable time between backup jobs. The default value is 4 hours. This means that if a laptop has been protected more than 4 hours ago, even if it does not meet the requirements, such as available bandwidth, AC power, etc., the system attempts to back it up. This prevents a laptop to function for a long period without being protected. An example is when the laptop's battery is used frequently or the bandwidth is limited.

Automatic database log backups

Right-click a schedule policy | Click the General tab | Add | Schedule Pattern tab | Automatic | Databases subtab

The automatic backup schedule for databases allows to set a space usage threshold for the volume where the database log files reside. If the space usage is reached, a backup is triggered, which implies truncating the logs at the end of the backup. It will therefore free up space on the volume. This is a useful tool to prevent database log volumes to fill up if backups are not scheduled to run frequently enough.

When setting up the criteria for database backups, two values must be set for interval between backup jobs, which are as follows:

• Detect file or log activity every – This is the minimal time between two consecutive backup jobs. The default value is 15 minutes. If the database has been protected more than 15 minutes ago, and its log volume space usage reaches the defined usage threshold, it gets protected.
• Run the backup every – This is the maximum acceptable time between backup jobs. The default value is 4 hours. This means that if a database has been protected more than 4 hours ago, even if log volume space usage has not reached the defined threshold, the system protects it.

Commvault software supports the following applications for database backups:

• Microsoft^® SQL server
• Oracle
• Oracle RAC
• SAP for Oracle
• Notes database traditional log backups
• MongoDB

For the most current list of applications, refer to the Commvault^® Online Documentation.

Automatic Auxiliary Copy Schedule

Expand Policies | Schedule Policies | Right-click System Created Autocopy schedule | Click Edit

An automatic schedule is used to run an auxiliary copy. You can create the automatic schedule if you want to perform the auxiliary copy at a specific frequency to ensure that an additional copy of data is automatically created. If you define a frequency of 30 minutes, this means that every 30 minutes the system checks if there are completed jobs in a storage policy primary copy that have not yet been copied to a secondary copy. If this is the case, the auxiliary copy job starts copying these jobs.

An automatic schedule has a significant advantage over a traditional auxiliary copy schedule that runs after the backups. Since it executes every 30 minutes, if jobs have completed, they are copied even if other backup jobs are still running. This provides the shortest auxiliary copy window possible.

When Commvault^® software is installed, a schedule policy named System Created Autocopy schedule is implemented by default. When a storage policy secondary copy is created, it automatically becomes associated with that schedule policy that executes auxiliary copies every 30 minutes.

Scripting

When jobs are configured in the CommCell^® console they can be saved as scripts. Saving a job as a script lets the user execute jobs on demand. For example, if the DBA dumps database files each night, there is a risk that the dump process will finish at different times and a scheduled backup may run before the dump operations are complete. If the backup of the dump location is saved as a script, the DBA can call the script once the dump operations complete ensuring the data is properly protected.

Scripts can also be used by third party schedule manager software, such as BMC Control-M^®, Windows^® NT Scheduler or Linux Crontab.

Save As Script Screen Options

Right-click the subclient | Click Backup | Save As Script button

The following table displays several options that are required to configure when creating the script:

To create a script, simply choose all the options as if you were to execute the job, but instead of running it immediately, click the Save As Script button.

Script Files

When a Save As Script operation is conducted, two files are created:

• The first file is the script itself, using the file name that was provided in the Save As Script window.
• The second file is an XML formatted file. It contains all the backup options selected when the script was created. It is used as an input by the script.

Both files can be copied and modified to create additional tasks. For instance, the XML file can be copied and modified to replace the Incremental backup type with Full; creating the full backup input file without having to go through all the Save As Script screens again.