mksched

Purpose

Use the mksched command to create a new backup schedule, which describes what Oracle Secure Backup should back up. The backup schedule contains the name of each dataset and its associated media family.

A backup schedule contains 0 or more triggers. A trigger is a user-defined set of days (--day) and times (--time) when the scheduled backup should run. At the beginning of the day, Oracle Secure Backup inspects the triggers in each schedule. For each trigger that fires on this day, Oracle Secure Backup creates one new job for each dataset listed in the schedule. Unlike on-demand (one-time-only) backups created by means of the backup command, the scheduler creates jobs directly and does not first create backup requests.

You can use the chsched command to add, change, or remove triggers in an existing schedule.

Prerequisites

You must have the modify administrative domain's configuration right to use the mksched command.

Syntax

mksched::=

mksc•hed [ --dataset/-D dataset-name[,dataset-name]... ]
[ --comment/-c comment | --inputcomment/-i ]
[ --priority/-p schedule-priority ]
[ --restrict/-r restriction[,restriction]... ]
[ [ --day/-d day-date ] [ --time/-t time ]
  [ --level/-l backup-level ] [ --family/-f media-family-name ]
  [ --expires/-x duration ] ]...
schedulename ...

Semantics

--dataset/-D dataset-name ...

Specifies the dataset that you want to include in the backup job.

If no datasets are specified in the schedule, then Oracle Secure Backup will not initiate backups based on the schedule. You can add a dataset to an existing schedule by using the chsched command.

--comment/-c comment

Adds a comment to the schedule.

--inputcomment/-i

Prompts for a comment.

--priority/-p schedule-priority

Assigns a schedule priority to a backup. Refer to "schedule-priority" for a description of the schedule-priority placeholder.

--restrict/-r restriction ...

Restricts the backup to specific devices within an administrative domain. You can select media server hosts or specific devices on these hosts. If you do not specify a restriction (default), then the current schedule has no device restrictions and can use any available device on any media server at the discretion of the Oracle Secure Backup scheduling system. Refer to "restriction" for a description of the restriction placeholder.

--day/-d day-date

Specifies the day on which Oracle Secure Backup will trigger the scheduled backup. If you do not specify a day or time, then Oracle Secure Backup will not run backup jobs based on the schedule. If you specify a day but no time, then the time defaults to 00:00. Refer to "day-date" for a description of the day-date placeholder.

--time/-t time

Specifies the time at which Oracle Secure Backup will trigger the scheduled backup. You cannot specify a time without a day. Refer to "time" for a description of the time placeholder.

--level/-l backup-level

Identifies a backup level. The default is full. Refer to "backup-level" for a description of the backup-level placeholder.

--family/-f media-family-name

Specifies the name of the media family to which the data of this scheduled backup should be assigned. The default is the null media family.

--expires/-x duration ...

Specifies an expiration time period. Refer to "duration" for a description of the duration placeholder. Specifying this option expires the backup if it is not executed by duration after the trigger time.

schedulename ...

Specifies the name of the schedule to create. Schedule names are case-sensitive and must start with an alphanumeric character. They can contain only letters, numerals, dashes, underscores, and periods (no spaces). They may contain at most 127 characters.

Example

Example 2-92 schedules a backup every Thursday at 9:00 p.m.

ob> lssched
ob> mksched --priority 5 --dataset datadir.ds --day thursday --time 21:00 datadir
ob> lssched
datadir             thursdays                      datadir.ds
ob> lsjob --pending
Job ID           Sched time  Contents                       State
---------------- ----------- ------------------------------ ----------------------
3                10/06.21:00 dataset datadir.ds             future work