Schedule a backup

After creating a backup job, you can add one or more schedules for running the job on specific days of the week or month. You can create complex schedules for a job by creating multiple schedules. For example, you can schedule a backup job to run at midnight every Friday, and schedule the job to run at 8 PM on the first day of every month.

Note: When Windows Agent 8.90 or later, Linux Agent 8.90 or later, AIX Agent 9.00 or vSphere Recovery Agent 9.11 is backing up data to a Director version 8.60 or later vault, you can also schedule a backup job to run multiple times per day, as often as hourly. See Schedule a backup to run multiple times per day.

Note: Beginning with Portal 9.30 and Windows Agent 9.30, Image and Local System backups can also be triggered by system events on supported Windows desktop operating systems. See Trigger backups when events occur on Windows desktop computers.

When scheduling multiple SQL Server database jobs in the same instance, it is good practice to schedule the jobs so that their running times do not overlap. Simultaneous backups are supported, but are not recommended.

If a job is scheduled to start at exactly the same time by multiple schedules, the job only runs once at the scheduled time, and the retention type of the schedule that is higher in the schedule list is applied to the resulting safeset. For example, in the following screenshot, a job is scheduled to run at 12 AM on Saturdays by two schedules. On Saturdays, the job runs only once at 12 AM. Because the schedule with the Weekly retention type is higher in the list than the schedule with the Daily retention type, the Weekly retention type is applied to the resulting safeset.

Note: If a job is scheduled to run at slightly different times, the agent attempts to run the job according to each schedule. For example, if a job is scheduled to run at 11 PM by one schedule and 11:01 PM by another schedule, the agent will attempt to run the job twice. Try to avoid overlapping schedules; problems can occur if a job is scheduled to run twice in a short period of time. In particular, avoid overlapping schedules for SQL Server database jobs in the same instance. Simultaneous backups in the same SQL Server instance are supported but are not recommended.

View/Add Schedule box

When you schedule a backup, the View/Add Schedule dialog box shows the maximum number of restore points that could result from the job's current schedules and retention types. You can then change your schedules, if required. See Maximum number of restore points for a job.

To schedule a Hyper-V job, see Add or edit a schedule for a Hyper-V backup job.

To schedule a backup job to run at a specific time on specific days of the week or month:

  1. Do one of the following:

    • On the navigation bar, click Computers. Find the computer with the backup job that you want to schedule, and click the row to expand its view. On the Jobs tab, find the job that you want to schedule. In its Select Action menu, click View/Add Schedule.

    • Create a new backup job. The View/Add Schedule dialog box appears when you save the job.

  2. In the View/Add Schedule dialog box, click Add Schedule.

    A new row appears in the dialog box.

  3. In the new schedule row, in the Retention list, click a retention type.

    The retention type specifies the number of days a backup is kept on the vault, how many copies of a backup are stored online, and how long backup data is stored offline. See Add retention types.

    The 24-Hours and 48-Hours retention types are only available for intra-daily schedules. See Schedule a backup to run multiple times per day.

  4. If the schedule is for a SQL Server Plug-in database backup job, do one of the following in the Backup Type list:

    • To back up each database from the point in time when the backup starts, click Full.

    • To back up each database and its transaction logs from the point in time when the backup starts, click Full with transaction logs.

    • To back up the database transaction logs only from the point in time when the backup starts, click Transaction logs only. When Transaction Logs only is selected, the entire database and its transaction logs will be backed up when the job first runs. In subsequent backups, only the transaction logs will be backed up.

      Note: After a transaction log backup, logs are marked for truncation. If you also back up databases using another tool (e.g., native SQL Server backup), be sure that only one tool is being used for truncating logs.

      Note: Transaction logs can only be backed up for databases that use the full or bulk-logged recovery model.

  1. If the schedule is for an Image Plug-in job that backs up volumes with SQL Server database files, do one of the following in the SQL Application Settings list:

    • To truncate database transaction logs after the backup, select Truncate transaction logs.
    • To run the backup without truncating logs, clear Truncate transaction logs.

      Note: If you also back up databases using another tool (e.g., native SQL Server backup), use only one tool for truncating logs.

  2. If the schedule is for an Exchange database backup job, do the following:

    • In the Backup Type list, do one of the following:

      • To only back up transaction logs and the checkpoint file after the first “seed” backup, click Incremental.

      • To back up the database files, checkpoint file and transaction logs, click Full.

      For more information, see Plan Full and Incremental Exchange backups.

    • To validate Exchange data during the backup, select Validate Exchange database.

  3. In the Schedule box, click the arrow.

    The Configure Job Schedule dialog box opens.

  4. In the Configure Job Schedule dialog box, do one of the following:

    • To run the backup on specific days each week, select Days of Week in the Schedule View list. Select the days when you want to run the job. Then use the At field to specify the time when you want to run the job.

      Days of Week schedule

    • To run the backup on specific dates each month, select Days of Month in the Schedule View list. On the calendar, select the dates when you want to run the job. Then use the At field to specify the time when you want to run the job.

      Days of Month schedule

    • To create a custom schedule, select Custom in the Schedule View list. In the Custom Cycle dialog box, enter a custom schedule. Be sure to follow the format and notation as described.

      Custom schedule

    • Note: If Intra-daily appears in the Schedule View list, you can also schedule the backup to run multiple times each day. See Schedule a backup to run multiple times per day.

  5. Click Okay.

    The new schedule appears in the Schedule box.

  6. In the Compression list, click a compression level for the backup data. Compression levels optimize Compression levels optimize the amount of data stored vs. the backup speed.

    For descriptions of compression level options, see Policy compression and log settings.

  7. Do one of the following:

    • To allow the backup job to run without a time limit, click None in the Deferring list.

    • To specify a maximum amount of time that the backup job can run, click Minutes or Hours in the Deferring list. In the adjacent box, type the maximum number of minutes or hours that the job can run.

      Note: When deferring is used, the backup job does not back up any new data after the specified amount of time, even if some data is not backed up. Changes to data that was previously backed up will be backed up, regardless of the amount of time specified.

      Note: Incremental backups for Exchange cannot be deferred, even if deferring is enabled. Deferring can be applied to full backups for Exchange.

  8. To run the job on the specified schedule, select the Enable check box near the end of the row.

  9. If there is more than one schedule row, you can use the Priority arrows to change the order of the schedule rows. Schedules higher in the list have a higher priority than schedules lower in the list.

    If a job is scheduled to run at the same time by multiple schedules, the job only runs once at the scheduled time. If the schedules have different retention types, the job only runs with the retention type of the schedule that is highest in the list.

  10. Check the number of restore points that could result from the job's schedules and retention policies. If you want to increase or decrease the number of restore points, change the schedules or retention types.

    The maximum number of restore points appears below the schedules in the View/Add Schedule dialog box. For more information, see Maximum number of restore points for a job.

  11. If an Automatic Retry for Scheduled Backups section appears in the View / Add Schedule dialog box, you can specify whether scheduled backups should retry after a failed backup. See Specify whether scheduled backups retry after a failure.

  12. If a Windows Event Backup Triggers section is available in the View / Add Schedule dialog box, you might be able to create a Windows event backup trigger. When a backup job has a trigger, the job runs automatically when a user logs on to the computer or the computer starts to shut down. See Trigger backups when events occur on Windows desktop computers.

  13. Click Save.