HP Archive Backup System for OpenVMS Guide to Operations

More documents

Recommendations

Info

System Backup to Tape for Oracle Databases 9.4 Configuring System Backup to Tape in the Archive Backup System $ DEFINE/SYSTEM/NOLOG MDMS$SBT_TRACE_LEVEL 'tracefilter' $! After editing SYS$STARTUP:MDMS$SYSTARTUP.COM, be sure to execute it so the logical is defined. By default the general information and media movement information are traced in the trace file ORA_DUMP:SBTIO.LOG. Refer to Section 9.11.1 for more information about the logical MDMS$SBT_TRACE_LEVEL. 9.4 Configuring System Backup to Tape in the Archive Backup System Before you can use SBT, you must configure a catalog and an archive in ABS/MDMS. This section describes how to create catalogs and archives. Catalogs store information about what information was backed up. Archives allow you to implement your storage policies. This section shows you how to create the default catalog (ORACLE_DB) and the default archive (ORACLE_DB_ARCHIVE). By creating these two default objects, you can test SBT easier as described in Section 9.5. 9.4.1 Creating an ORACLE_DB Catalog Before you can us the SBT feature, you must create a catalog. The catalog stores the tape volume, saveset name, and piece name. The catalog allows SBT to lookup the tape volume for a restore. You should only create one oracle_db type catalog that is accessible to Oracle’s Recover Manager(s). The catalog is created in ABS$CATALOG:. The catalog must be created in the ABS$CATALOG: directory that is local to all nodes that will access the catalog. Use the following command to create a catalog named ORACLE_ DB: $ MDMS CREATE CATALOG ORACLE_DB /TYPE=ORACLE_DB Note Do not use the /NODE qualifier when creating the catalog. This version of SBT can only access catalogs that are local to the node. 9.4.2 Creating an Archive When doing an Oracle Recovery Manager restore, allocateForMaint, or validate command, you must specify the catalog you want to use. However, the default catalog name for SBT is ORACLE_DB. Therefore, if you do not specify a catalog, it will lookup information in the ORACLE_DB catalog on the local node. Refer to Section 9.7 for information on how to access the ORACLE_DB catalog. An archive defines the tape volumes and archive attributes where you can safely store data. Each archive has a unique name and contains a set of archive characteristics. You can have as many archives as you want to implement your storage policies. This section describes how to create an archive and what attributes pertain to SBT. You should refer to the command reference guide for information about creating archives and their attributes. You may want to create an archive that keeps tape volumes for a year and another that keeps tape volumes for 35 days. Note When using SBT you do not use an environment, save, or restore object. The following command creates an archive named ORACLE_DB_ ARCHIVE: $ MDMS CREATE ARCHIVE ORACLE_DB_ARCHIVE - /ARCHIVE_TYPE=TAPE - 9-8 System Backup to Tape for Oracle Databases
System Backup to Tape for Oracle Databases 9.4 Configuring System Backup to Tape in the Archive Backup Sys- /CATALOG=(NAME=ORACLE_DB) - /MAXIMUM_SAVES=36 - /MEDIA_TYPE=DLT_III - /POOL=DB_BACKUP_POOL - /RETENTION_DAYS=35 $ MDMS SHOW ARCHIVE ORACLE_DB_ARCHIVE Archive: ORACLE_DB_ARCHIVE 1 Description: Access Control: NONE Owner: MOE::ORACLE9I Archive Type: TAPE 2 Catalog - - Name: ORACLE_DB 3 - Nodes: Consolidation - - Interval: 0007 00:00:00 4 - Savesets: 0 - Volumes: 0 Destination: Drives: 5 Expiration Date: NONE Location: CR_2 6 Maximum Saves: 36 7 Media Type: DLT_III 8 Pool: DB_BACKUP_POOL 9 Retention Days: 35 10 Volume Sets: The following describes the different attributes of the archive: 1. Archive: ORACLE_DB_ARCHIVE is the name of the archive created. This is the name you must specify in Oracle's Recovery Manager allocate command. See Section 9.6.2, Specifying an Archive on how to specify the archive name in the allocate command. If you do not specify an archive in Oracle's Recovery Manager commands, ORACLE_DB_ARCHIVE is used as the default. See Section 9.9.1 for more information. 2. Archive Type: this specifies that the backup will be archived to tape. This version does not support archive to disk. 3. Catalog Name: you need to specify which catalog used by this archive. If you create more than one catalog, you must have a different archive for each catalog. However, all archives can use the same catalog. See Section 9.9.2 for more information. 4. Consolidation Interval: specifies the consolidation interval for the volume sets. The volumes sets are stored in the Volume Sets: attribute. In this example, after 7 days a new volume set is started. The default consolidation interval is 7 days. 5. Drives: specifies the tape drives that you want to use when using this archive. This limits the tape drives that you can use. Unless you need to limit which tape drives to use, I suggest you do not. See Section 9.10.1 for restrictions in using this attribute. 6. Location: this location came from the MDMS domain object. SBT uses it in selecting a tape volume and tape drive. Your tape volume, jukebox, and node must also have this location attribute. If you do not need a location to specify the volumes you want to allocate, specify /NOLOCATION. System Backup to Tape for Oracle Databases 9–9
Page 1 and 2:
HP Archive Backup System for OpenVM
Page 3 and 4:
Contents Preface . . . . . . . . .
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:
Page 53 and 54:
Table 3-3 Disk, File, Path and Data
Page 55 and 56:
Page 57 and 58:
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:
Page 92 and 93:
Media Management 4.11 Volumes neede
Page 94 and 95:
Media Management 4.11 Volumes • R
Page 96 and 97:
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 113 and 114: Figure 6-5 Domain View Showing Expa
Page 117 and 118: 6.1.13 Viewing MDMS Audit and Event
Page 119 and 120: 6.2.1 Syntax Overview User Interfac
Page 121 and 122: User Interfaces 6.3 User Interface
Page 123 and 124: 7 Preparing For Disaster Recovery I
Page 125 and 126: 7.1.2 Backup of MDMS$ROOT Preparing
Page 127 and 128: 7.2 Prolog and Epilog Procedure Pre
Page 129 and 130: 7.2.1 Restoring The System Disk To
Page 131 and 132: 8 Remote Devices 8.1 RDF Installati
Page 133 and 134: Remote Devices 8.4 Monitoring and T
Page 135 and 136: 8.4.4 Changing Network Parameters f
Page 137 and 138: • Free Space is 20 Remote Devices
Page 139 and 140: Remote Devices 8.5 Controlling Acce
Page 141: Remote Devices 8.7 RDF Error Messag
Page 144 and 145: System Backup to Tape for Oracle Da
Page 174 and 175: Virtual Library System (VLS) 10.3 Q
Page 176 and 177: Architecture 11.1 The Server Proces
Page 178 and 179: Architecture 11.2 Scheduler Interfa
Page 180 and 181: Architecture 11.3 Catalogs Example
Page 182 and 183: Architecture 11.4 Coordinator 11.4.
Page 184 and 185: Troubleshooting 12.2 Media Manageme
Page 186 and 187: Troubleshooting 12.2 Media Manageme
Page 188 and 189: Troubleshooting 12.4 ABS Catalogs 1
Page 190 and 191: Troubleshooting 12.5 Windows and Un
Page 192 and 193: Troubleshooting 12.6 RDF (Remote De
Page 195 and 196: A Configuration Example Getting ABS
Page 197 and 198: Configuration Example * Magazine -
Page 199 and 200: Configuration Example Configuring s
Page 201 and 202:
Configuration Example If you comple
Page 203 and 204:
Configuration Example Assist: YES C
Page 205 and 206:
B Migrating from SLS/MDMS V2.X to A
Page 207 and 208:
Migrating from SLS/MDMS V2.X to ABS
Page 209 and 210:
Table B-1 SBK Symbols in ABS Termin
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
$ WRITE EpilogComFile - Migrating f
Page 245 and 246:
Table B-6 Execution Environment Par
Page 247 and 248:
• SAVE Migrating from SLS/MDMS V2
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Solution - Follow these steps: Migr
Page 257 and 258:
C Prev3 Support Prev3 Support is pr
Page 259 and 260:
Prev3 Support C.2 Using SLS as the
Page 261:
Prev3 Support C.2 Using SLS as the
Page 264 and 265:
Upgrading from ABS V2.X/V3.X to V4.
Page 266 and 267:
Upgrading from ABS V2.X/V3.X to V4.
Page 268 and 269:
ABS/MDMS Support for Fibre Channel
Page 270 and 271:
ABS/MDMS Support for Fibre Channel
Page 273 and 274:
Index Numerics 100 times per day 3-
Page 275 and 276:
MDMS$SBT_ ARCHIVE_n 9-20 MDMS$SBT_
Page 277:
volumes 3-4 W WARNING 3-14, 3-31 WE
show all

HP Archive Backup System for OpenVMS Guide to Operations

Create successful ePaper yourself

Delete template?

Save as template?