Skip Headers
Oracle® Secure Backup Reference
Release 10.1

Part Number B14236-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

chsched

Purpose

Use the chsched command to change an existing backup schedule.

See Also:

"Schedule Commands" for related commands

Prerequisites

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

Syntax

chsched::=

chsc•hed [ --dataset/-D dataset-name[,dataset-name]... ]
[ --adddataset/-A dataset-name[,dataset-name]... ]
[ --rmdataset/-R dataset-name[,dataset-name]... ]
[ --comment/-c comment | --inputcomment/-i ]
[ --priority/-p schedule-priority ]
[ --restrict/-r restriction[,restriction]... ]
[ --addrestrict/-E restriction[,restriction]... ]
[ --rmrestrict/-T restriction[,restriction]... ]
[ [ --addtrigger/-a ] |
[ --chtrigger/-h trigger-number[,trigger-number]... ] |
[ --rmtrigger/-m trigger-number[,trigger-number]... ] ]
[ [ --day/-d day-date ] [ --time/-t time ]
[ --level/-l backup-level ] [ --family/-f media-family-name ]
[ --expires/-x duration ] ]...
schedulename...

Semantics

Refer to the "mksched" command for option descriptions not included in this section.

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

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

--adddataset/-A dataset-name ...

Adds a dataset to the current schedule.

--rmdataset/-R dataset-name ...

Removes a dataset from the current schedule.

--addrestrict/-E restriction ...

Adds another drive to be used by the backup. Refer to "restriction" for a description of the restriction placeholder.

--rmrestrict/-T restriction ...

Removes a restriction from a schedule. Refer to "restriction" for a description of the restriction placeholder.

--addtrigger/-a

Adds a trigger to the schedule. A trigger is a user-defined period in time or sets of times that causes a scheduled backup to run. You must specify the --day option when adding a trigger. If you specify --day but do not specify a time, then the time defaults to 00:00.

--chtrigger/-h trigger-number ...

Edits the specified trigger in the schedule. Specify the --long option on the lssched command to obtain trigger numbers.

--rmtrigger/-m trigger-number ...

Removes a trigger from the schedule. Specify the --long option on the lssched command to obtain trigger numbers.

schedulename ...

Specifies the name of the backup schedule.

Example

Example 2-25 adds a weekday trigger to a full backup scheduled to run every Sunday. The example then changes the Sunday trigger to run at noon instead of 8 a.m.

Example 2-25 Changing a Backup Schedule

ob> lssched --long
full_backup:
    Dataset:                fullbackup.ds
    Priority:               5
    Trigger 1:
        Day/date:           sundays
        At:                 08:00
        Backup level:       full
        Media family:       (null)
ob> chsched --addtrigger --day "mon tue wed thu fri" --family full --expires
30days --time 04:00 full_backup
ob> lssched --long
full_backup:
    Dataset:                fullbackup.ds
    Priority:               5
    Trigger 1:
        Day/date:           sundays
        At:                 08:00
        Backup level:       full
        Media family:       (null)
    Trigger 2:
        Day/date:           weekdays
        At:                 04:00
        Backup level:       full
        Media family:       full
        Expires after:      30 days
ob> chsched --chtrigger 1 --time 12:00 full_backup
ob> lssched --long
full_backup:
    Dataset:                fullbackup.ds
    Priority:               5
    Trigger 1:
        Day/date:           sundays
        At:                 12:00
        Backup level:       full
        Media family:       (null)
    Trigger 2:
        Day/date:           weekdays
        At:                 04:00
        Backup level:       full
        Media family:       full
        Expires after:      30 days