Table of ContentsView in Frames

Scheduling recurring backups

You can schedule backup operations so that the backups are initiated automatically at regular intervals. SnapManager allows you to schedule backups on an hourly, daily, weekly, monthly, or one-time basis.

About this task

You can assign multiple backup schedules for a single database. However, when scheduling multiple backups for the same database, you must ensure that the backups are not scheduled at the same time.

These steps show how to create a backup schedule for your database using the SnapManager user interface (UI). You can also use the command-line interface (CLI) if you prefer. For information about how to schedule backups using the CLI, see the SnapManager for Oracle Administration Guide for UNIX.

Steps

  1. From the Repositories tree, right-click the profile containing the database for which you want to create a backup schedule, and select Schedule Backup.
  2. In Label, enter a custom name for the backup.
    You must not include spaces or special characters in the name. If you do not specify a name, SnapManager automatically creates a backup label.

    From SnapManager 3.4, you can modify the backup label created automatically by SnapManager. You can edit the override.default.backup.pattern and new.default.backup.pattern configuration variables to create your own default backup label pattern.

  3. Optional: In SnapVault Label, you must enter the SnapMirror label that you specified in the rules of the SnapMirror policy while setting up the SnapVault relationship.
    Note: The SnapVault Label field appears only if you have selected SnapManager_cDOT_Vault as the protection policy while creating the profile.
  4. Select Allow startup or shutdown of database, if necessary to modify the state of the database, if required.
    This option ensures that if the database is not in the required state to create a backup, SnapManager automatically brings the database to the desired state to complete the operation.
  5. On the Database, Tablespaces or Datafiles to Backup page, perform the following:
    1. Select Backup Datafiles to back up either the full database, selected data files, or selected tablespaces.
    2. Select Backup Archivelogs to back up the archive log files separately.
    3. Select Prune Archivelogs if you want to delete the archive log files from the active file system that is already backed up.
      Note: If Flash Recovery Area (FRA) is enabled for archive log files, then SnapManager fails to prune the archive log files.
    4. Select Protect the backup if you want to enable backup protection.
      This option is enabled only if the protection policy was selected while creating the profile.
    5. From the Type drop-down list, select the type of backup (offline or online) you want to create.
      If you select Auto, SnapManager creates a backup based on the current state of the database.
    6. From the Retention Class drop-down list, select the retention class.
    7. Select the Verify backup using the Oracle DBVERIFY utility check box if you want to ensure that the backed-up files are not corrupted.
  6. In the Schedule Name field, enter a custom name of the schedule.
    You must not include spaces in the name.
  7. On the Configure Backup Schedule page, perform the following:
    1. From the Perform this operation drop-down list, select the frequency of the backup schedule.
    2. In the Start Date field, specify the date when you want to initiate the backup schedule.
    3. In the Start Time field, specify the time when you want to initiate the backup schedule.
    4. Specify the interval in which backups will be created.
      For example, if you have selected the frequency as hourly and specify the interval as 2, then backups will be scheduled every 2 hours.
  8. On the Task Enabling page, specify whether you want to perform tasks before and after backup operations are completed.
  9. On the Perform Backup Schedule Operation page, verify the information and click Schedule.
  10. Click Finish to close the wizard.
    If the operation fails, click Operation Details to view what caused the operation to fail.