HP Archive Backup System for OpenVMS Guide to Operations
HP Archive Backup System for OpenVMS Guide to Operations HP Archive Backup System for OpenVMS Guide to Operations
Saving and Restoring Data 3.7 Schedules 3.7 Schedules 3.7.1 After Schedule ABS supports very flexible options for scheduling save and restore requests, both using the internal MDMS scheduling options and using a third part scheduler. The scheduling options can be divided into three main categories: • Standard - ABS provides a list of standard options that you can specify, and the scheduling information is applied to the schedule object automatically. Standard options are supported by both internal MDMS scheduling and an external scheduler product. Standard options are all those that are neither custom or explicit. • Custom - This option allows you to customize the schedule for the request if the standard options are not sufficient. For example, if you want to run the request every second Sunday in January, April, July and October, then the custom option can do this. You specify CUS- TOM as the frequency, then modify the schedule object for the request directly. This option is applicable to internal MDMS scheduling only. • Explicit - This option also allows you to customize your schedule, but this time with an external scheduler product. You specify EXPLICIT as a frequency, then enter a string into the EXPLICIT INTERVAL attribute. This attribute is a string that can be understood by the external scheduler product specifying the desired frequency. Alternatively, you can use the user interface of the external scheduler product to specify the frequency of the request. This option is applicable only to external scheduling options. This section discusses the second option, custom schedules, which are only applicable to internal MDMS scheduling. To use a custom schedule, specify CUSTOM as the frequency on the save and restore request, then modify the attributes of the associated schedule object. The schedule object always has the name of the save and restore request, followed by “_SAVE_SCHED” or “REST_SCHED” respectively. With ABS custom scheduling, you can actually define one schedule to execute after another schedule has completed. For example, if you want SAVE2 to execute immediately after SAVE1 completes, you can modify SAVE2’s schedule object and setting its AFTER SCHEDULE attribute to SAVE1’s schedule object. In this case: SAVE2_SAVE_SCHED: After Schedule: SAVE1_SAVE_SCHED If you specify an after schedule and only want the associated request to execute after the after schedule (and not at any other time), then do not specify any other date or time attributes in the schedule. If on the other hand you want the associated request to execute at regular times AND after the specified after schedule, then you can associate date and time attributes to the schedule. With after schedule, you can also define conditions upon which the schedule will run after the other schedule. The conditions are stored in an attribute called after schedule when. Select from one of the following: • ALL - Always run the schedule after the dependent schedule completion • SUCCESS - Run the schedule if the dependent save or restore completed with a successful status • WARNING - Run the schedule if the dependent save or restore completed with a Warning, Error or Fatal status • ERROR - Run the schedule if the dependent save or restore completed with an Error or Fatal Status 3-32 Saving and Restoring Data
3.7.2 Command 3.7.3 Restriction Saving and Restoring Data 3.7 Schedules • FATAL - Run the schedule if the dependent save or restore completed with a fatal status • NONE - Never run the schedule (can be used as a temporary placeholder) If an after schedule name is defined, but no conditions are specified, the default condition is ALL. To remove the after schedule dependency, specify no after schedule. For ABS save and restore commands, the command to run a schedule and execute the associated save and restore request is: MDMS RUN SCHEDULE schedule_name You should not modify this command line, unless you know how to activate an ABS request in some other way. For non-ABS save or restore requests, this command line can be any command that can be submitted to the OpenVMS CLI. There is a restriction with using the /AFTER_SCHEDULE qualifier. Only those schedules (created automatically by MDMS) that have an associated save can be assigned to the /AFTER_SCHEDULE qualifier. Schedules that do NOT have an associated save cannot be assigned to the /AFTER_SCHEDULE qualifier. Hence, any schedule (one with an associated save, or one which executes DCL commands) can have a dependency on a schedule with an associated save, but not on a schedule which executes DCL commands. This is a current MDMS design limitation. 3.7.4 Dates, Days and Months ABS supplies three attributes in the schedule object by which you can specify on what days you want the schedule to be regularly executed. These are: • Dates - The dates of the month you want the schedule to execute • Days - The days of the week you want the schedule to execute • Months - The months of the year you want the schedule to execute You can specify the actual dates in the month that you want the schedule to run by number. Here are some examples: If you don’t specify a date attribute, the default is every day of the month. Table 3–6 Date Specifications Dates Explanation 1 First day of month 1-7 First week of month 1-7, 15-21 First and third week of month 1-31 Every day of month (default) Saving and Restoring Data 3–33
- Page 13: Tables Table 3-1 Logical Names Avai
- Page 17 and 18: Preface Intended Audience This docu
- Page 19 and 20: 1 Introduction The Archive Backup S
- Page 21 and 22: 2 Overview This chapter provides an
- Page 23 and 24: Overview 2.2 ABS Objects Figure 2-1
- Page 25 and 26: 2.2.6 Schedules 2.3 ABS Catalogs Ov
- Page 27 and 28: Overview 2.5 Media, Device and Mana
- Page 29 and 30: 2.8.3 Groups 2.8.4 Jukeboxes Overvi
- Page 31 and 32: 2.8.8 Nodes 2.8.9 Pools 2.8.10 Volu
- Page 33 and 34: 3 Saving and Restoring Data 3.1 Arc
- Page 35 and 36: 3.1.5 Destination 3.1.6 Drives 3.1.
- Page 37 and 38: 3.1.12 Volume Sets Saving and Resto
- Page 39 and 40: 3.2.5 Staging 3.2.6 Catalog Save En
- Page 41 and 42: • Save Type - Copied from related
- Page 43 and 44: Example 3-4 Staging Information in
- Page 45 and 46: 3.4.3 Compression 3.4.4 Data Safety
- Page 47 and 48: Saving and Restoring Data 3.4 Envir
- Page 49 and 50: Saving and Restoring Data 3.5 Saves
- Page 51 and 52: Saving and Restoring Data 3.5 Saves
- Page 53 and 54: Table 3-3 Disk, File, Path and Data
- Page 55 and 56: Saving and Restoring Data 3.5 Saves
- Page 57 and 58: Saving and Restoring Data 3.5 Saves
- Page 59 and 60: • First disk/file specification p
- Page 61 and 62: 3.5.17.1 HOLIDAYS.DAT Record Format
- Page 63: Saving and Restoring Data 3.6 Selec
- Page 67: 3.7.5 Include and Exclude 3.7.6 Tim
- Page 70 and 71: Media Management 4.2 Domain 4.2.1 A
- Page 72 and 73: Media Management 4.2 Domain 4.2.15
- Page 74 and 75: Media Management 4.3 Drives 4.3.5 D
- Page 76 and 77: Media Management 4.3 Drives 4.3.15
- Page 78 and 79: Media Management 4.5 Jukeboxes 4.5.
- Page 80 and 81: Media Management 4.5 Jukeboxes 4.5.
- Page 82 and 83: Media Management 4.7 Magazines 4.6.
- Page 84 and 85: Media Management 4.8 Media Types 4.
- Page 86 and 87: Media Management 4.11 Volumes 4.10.
- Page 88 and 89: Media Management 4.11 Volumes Table
- Page 90 and 91: Media Management 4.11 Volumes 4.11.
- Page 92 and 93: Media Management 4.11 Volumes neede
- Page 94 and 95: Media Management 4.11 Volumes • R
- Page 96 and 97: Media Management 4.11 Volumes 4.11.
- Page 99 and 100: 5 Security The security model used
- Page 101 and 102: Security 5.1 MDMS Rights Table 5-1
- Page 103 and 104: Table 5-4 Domain Access Control Opt
- Page 105 and 106: 6 User Interfaces ABS and MDMS supp
- Page 107 and 108: 6.1.3 Logging In User Interfaces 6.
- Page 109 and 110: User Interfaces 6.1 Graphical User
- Page 111 and 112: User Interfaces 6.1 Graphical User
- Page 113 and 114: Figure 6-5 Domain View Showing Expa
3.7.2 Command<br />
3.7.3 Restriction<br />
Saving and Res<strong>to</strong>ring Data<br />
3.7 Schedules<br />
• FATAL - Run the schedule if the dependent save or res<strong>to</strong>re completed with a fatal status<br />
• NONE - Never run the schedule (can be used as a temporary placeholder)<br />
If an after schedule name is defined, but no conditions are specified, the default condition is<br />
ALL. To remove the after schedule dependency, specify no after schedule.<br />
For ABS save and res<strong>to</strong>re commands, the command <strong>to</strong> run a schedule and execute the associated<br />
save and res<strong>to</strong>re request is:<br />
MDMS RUN SCHEDULE schedule_name<br />
You should not modify this command line, unless you know how <strong>to</strong> activate an ABS request in<br />
some other way.<br />
For non-ABS save or res<strong>to</strong>re requests, this command line can be any command that can be submitted<br />
<strong>to</strong> the <strong>OpenVMS</strong> CLI.<br />
There is a restriction with using the /AFTER_SCHEDULE qualifier. Only those schedules (created<br />
au<strong>to</strong>matically by MDMS) that have an associated save can be assigned <strong>to</strong> the<br />
/AFTER_SCHEDULE qualifier. Schedules that do NOT have an associated save cannot be<br />
assigned <strong>to</strong> the /AFTER_SCHEDULE qualifier. Hence, any schedule (one with an associated<br />
save, or one which executes DCL commands) can have a dependency on a schedule with an<br />
associated save, but not on a schedule which executes DCL commands. This is a current MDMS<br />
design limitation.<br />
3.7.4 Dates, Days and Months<br />
ABS supplies three attributes in the schedule object by which you can specify on what days you<br />
want the schedule <strong>to</strong> be regularly executed. These are:<br />
• Dates - The dates of the month you want the schedule <strong>to</strong> execute<br />
• Days - The days of the week you want the schedule <strong>to</strong> execute<br />
• Months - The months of the year you want the schedule <strong>to</strong> execute<br />
You can specify the actual dates in the month that you want the schedule <strong>to</strong> run by number. Here<br />
are some examples:<br />
If you don’t specify a date attribute, the default is every day of the month.<br />
Table 3–6 Date Specifications<br />
Dates<br />
Explanation<br />
1 First day of month<br />
1-7 First week of month<br />
1-7, 15-21 First and third week of month<br />
1-31 Every day of month (default)<br />
Saving and Res<strong>to</strong>ring Data 3–33
Change language