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.5 Saves and Restores not perform the Level 6 incremental backup operation. ABS resumes the full backup operation again on Monday, and the schedule once again repeats itself. – Notice also in Example B that ABS repeats the full backup operation until a successful full backup operation is achieved on Wednesday. If one of the incremental backup operations fail, ABS skips to the next level of the incremental backup operations. Unlike repeating the full backup operation, ABS does not repeat the same level of incremental backup operations during the 7-day cycle. – In the Example B, the Level 4 incremental backup operation failed on Friday. On Saturday, ABS resumes with a Level 5 incremental backup operation. However, the contents of the incremental backup operations are correct because ABS will back up all new or modified files since the last successful full backup or the last successful lower level incremental backup operation. – The save log file will contain the following backup command issued by ABS for Saturday, 05-APR-1997: – $ BACKUP/.../SINCE=”03-APR-1997 02:00:00.00” – Because the last successful lower level incremental backup operation was performed on 03-APR-1997, all changes to any file since the date and time specified in the BACKUP command are included in the backup operation. • WEEKLY - Executes the save request once per week according to the date and time specified for the start time. • BIWEEKLY - Executes the save request once every two weeks according to the date and time specified for the start time. • MONTHLY - Executes the job the first time on the date and time specified in the start time attribute. Subsequent jobs are scheduled on the first day of each month. • QUARTERLY - Executes the job the first time on the date and time specified in the start time attribute. Subsequent jobs are scheduled to execute on the first day of the quarter (3 month period). • SEMI_ANNUALLY - Executes the job the first time on the date and time specified in the start time attribute. Subsequent jobs are scheduled to execute on the first day of the month every 6 months and 12 months. • ANNUALLY - Executes the job the first time on the date and time specified in the start time attribute. Subsequent jobs are scheduled to execute every 12 months. • LOG-2 (Saves only) - ABS executes a full backup operation on day 1, and an incremental backup operation on day 2. On day 3, ABS executes an extended incremental backup operation. An extended incremental backup operation backs up any file modified since the last full or extended incremental backup operation. • LOG-3 (Saves only) - ABS executes a full backup operation on day 1, and an incremental backup operation on days 2 and 3. On day 4, ABS executes an extended incremental backup operation. An extended incremental backup operation backs up any file modified since the last full or extended incremental backup operation. Advantages of Log-n backup operations: Performing Log-n backup operations require less restore operations to fully restore a lost or corrupted disk volume. The higher the number of Log-n, the less restore operations you need to perform. Log-n backup operations are configured on a 32-day schedule, as shown in the examples below: 3-24 Saving and Restoring Data
Saving and Restoring Data 3.5 Saves and Restores Figure 3–2 Complex Backup Schedules • CUSTOM - This option allows you to define a specialized frequency by manipulating the associated schedule object directly. In this way you can define more flexible scheduling frequencies than are offered by the standard options. If you specify CUSTOM but do not modify the schedule object, then the default custom frequency is daily. This option applies only if internal MDMS scheduling is enabled (scheduler options INTERNAL and EXTERNAL). • EXPLICIT - This option enables you to submit the save request using a specific scheduler interval. If you select Explicit, you must enter a scheduler time format valid for the scheduler being used in the EXPLICIT INTERVAL attribute. This option applies only if a thirdparty scheduler is being used (scheduler options SCHEDULER). 3.5.11 Incremental • NEVER - Never submits the save request and does not call the scheduler to create a job. For example, you may need to create one or more save requests before you determine their schedule. To submit the save request, modify the save request and change the scheduling option. Depending on the selected scheduling option and the use of a 3rd party scheduler product, the Explicit Interval option allows to specify more flexible intervals. The Explicit Interval is passed as a string to the scheduler in use. Consult your scheduler’s manual for more information. Every save or restore request can be flagged as an incremental operation or a non-incremental operation. An incremental operation saves or restores files based on a previous operation - either a full operation or another incremental operation. For example, you could define a save request that performs a full disk save on Sunday, and an incremental save request that performs incremental saves on Monday through Saturday. The incremental saves will only save files that have been created or modified since the previous save (whether full or incremental). Restores can be performed in a similar fashion. Saving and Restoring Data 3–25
- Page 5 and 6: 3.6.1 Agent Qualifiers . . . . . .
- Page 7 and 8: 4.11.7 Previous and Next Volumes .
- Page 9 and 10: 9.3 Defining the Logical MDMS$SBT_T
- Page 11 and 12: B.2 SLS/MDMS V2.x to ABS/MDMS V4.x
- 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: 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 and 64: Saving and Restoring Data 3.6 Selec
- Page 65 and 66: 3.7.2 Command 3.7.3 Restriction Sav
- 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
Saving and Res<strong>to</strong>ring Data<br />
3.5 Saves and Res<strong>to</strong>res<br />
not per<strong>for</strong>m the Level 6 incremental backup operation. ABS resumes the full backup<br />
operation again on Monday, and the schedule once again repeats itself.<br />
– Notice also in Example B that ABS repeats the full backup operation until a successful<br />
full backup operation is achieved on Wednesday. If one of the incremental backup operations<br />
fail, ABS skips <strong>to</strong> the next level of the incremental backup operations. Unlike<br />
repeating the full backup operation, ABS does not repeat the same level of incremental<br />
backup operations during the 7-day cycle.<br />
– In the Example B, the Level 4 incremental backup operation failed on Friday. On Saturday,<br />
ABS resumes with a Level 5 incremental backup operation. However, the contents<br />
of the incremental backup operations are correct because ABS will back up all new or<br />
modified files since the last successful full backup or the last successful lower level<br />
incremental backup operation.<br />
– The save log file will contain the following backup command issued by ABS <strong>for</strong> Saturday,<br />
05-APR-1997:<br />
– $ BACKUP/.../SINCE=”03-APR-1997 02:00:00.00”<br />
– Because the last successful lower level incremental backup operation was per<strong>for</strong>med on<br />
03-APR-1997, all changes <strong>to</strong> any file since the date and time specified in the BACKUP<br />
command are included in the backup operation.<br />
• WEEKLY - Executes the save request once per week according <strong>to</strong> the date and time specified<br />
<strong>for</strong> the start time.<br />
• BIWEEKLY - Executes the save request once every two weeks according <strong>to</strong> the date and<br />
time specified <strong>for</strong> the start time.<br />
• MONTHLY - Executes the job the first time on the date and time specified in the start time<br />
attribute. Subsequent jobs are scheduled on the first day of each month.<br />
• QUARTERLY - Executes the job the first time on the date and time specified in the start<br />
time attribute. Subsequent jobs are scheduled <strong>to</strong> execute on the first day of the quarter (3<br />
month period).<br />
• SEMI_ANNUALLY - Executes the job the first time on the date and time specified in the<br />
start time attribute. Subsequent jobs are scheduled <strong>to</strong> execute on the first day of the month<br />
every 6 months and 12 months.<br />
• ANNUALLY - Executes the job the first time on the date and time specified in the start time<br />
attribute. Subsequent jobs are scheduled <strong>to</strong> execute every 12 months.<br />
• LOG-2 (Saves only) - ABS executes a full backup operation on day 1, and an incremental<br />
backup operation on day 2. On day 3, ABS executes an extended incremental backup operation.<br />
An extended incremental backup operation backs up any file modified since the last<br />
full or extended incremental backup operation.<br />
• LOG-3 (Saves only) - ABS executes a full backup operation on day 1, and an incremental<br />
backup operation on days 2 and 3. On day 4, ABS executes an extended incremental backup<br />
operation. An extended incremental backup operation backs up any file modified since the<br />
last full or extended incremental backup operation.<br />
Advantages of Log-n backup operations:<br />
Per<strong>for</strong>ming Log-n backup operations require less res<strong>to</strong>re operations <strong>to</strong> fully res<strong>to</strong>re a lost or corrupted<br />
disk volume. The higher the number of Log-n, the less res<strong>to</strong>re operations you need <strong>to</strong> per<strong>for</strong>m.<br />
Log-n backup operations are configured on a 32-day schedule, as shown in the examples<br />
below:<br />
3-24 Saving and Res<strong>to</strong>ring Data