HP Archive Backup System for OpenVMS Guide to Operations

More documents

Recommendations

Info

System Backup to Tape for Oracle Databases 9.11 Troubleshooting Tips server backups to certain drives, I suggest you do not put anything in this attribute. If you do use this attribute, be sure you have enough drives for the number of streams in the parallel backup. • Setting the Maximum Saves in the Archive to a number less than the number of parallel streams that Oracle's Recovery Manager starts. I suggest you set it at 36 and control the number of backups from the Oracle Recovery Manager. • Starting more parallel backups than you have tape drives. Do not start two or more parallel backups at the same time unless you have drives available for all streams in the parallel backups. To illustrate the problems stated above, I will give an example of setting the Maximum Saves in the archive to 2 and then using a Oracle Recovery Manager script that starts 3 parallel streams. Each stream starts the backup, the first two are allowed to get a volume set and start their backup. The third server starts up and finds that there is no volume set available at this time. It keeps trying to get a volume set. In the mean time, the first two servers finish doing the backup. However, the controlling server will not let them end until the third server is finished. Therefore, they hold on to the resources: drive and volume set. The third server can not finish for lack of resources. Any of the above problems stated above can cause this deadlock. 9.10.2 Piece Name Length Greater than 254 Characters A piece name length greater than 254 characters is not supported. This restriction may be lifted in subsequent versions to 511 characters for a piece name length. 9.10.3 Using RDF Drives with SBT You can NOT use Remote Device Facility (RDF) drives when using Oracle’s tape I/O slaves. RDF drives may be used with SBT if you are not using Oracle’s tape I/O slaves. 9.10.4 Backup with Oracle Dead Connection enabled During backup, Oracle background server process results in access violation when "Oracle Dead connection" detection is enabled by setting the parameter SQLNET.EXPIRE_TIME with Oracle 9.2.0.4. To use the sqlnet.expire parameter, the 'backup_tape_io_slaves=TRUE' should be set in the init.ora file specific to the instance and execute the backup. This is a workaround when using RMAN and ABS SBT with "sqlnet.expire" set to a non-zero value. 9.11 Troubleshooting Tips This section gives you some tips that may help you troubleshoot SBT if you have problems. 9.11.1 Using the logical MDMS$SBT_TRACE_LEVEL The logical MDMS$SBT_TRACE_LEVEL allows you define how much tracing appears in the trace file, ORA_DUMP:SBTIO.LOG. By default any error that is detected by SBT, is traced in the trace file. You can define the logical MDMS$SBT_TRACE_LEVEL to display more information. The definition of MDMS$SBT_ TRACE_LEVEL is defined in SYS$STAR- TUP:MDMS$SYSTARTUP.COM. If the logical is not defined on your system, see Section 9.3 to setup the logical. There are only three values that you might want to use. The rest of the values are for support use. By default the following values are enabled: • TR_GENINFO - general information about the backup and restore. With this value defined, you will see message about starting the backup or restore. 9-20 System Backup to Tape for Oracle Databases
System Backup to Tape for Oracle Databases 9.11 Troubleshooting Tips • TR_MEDINFO - information about drives and volumes. With this value define, you will see messages about allocating, loading, mounting, unloading, and deallocating tape volumes and drives. As a very minimum, we suggest that you enable the above two values so that you can check the progress of backups and restores. If the backup or restore can not get a volume set, it will loop, once a minute, waiting for the volume set to become available. If a tape drive is unavailable,SBT loops waiting for a drive to become available. SBT tries to allocate the tape drive every minute. SBT reports that it can not allocate the tape drive after five minutes and then after 10 minutes and so forth. Example 9–18 shows an example of ORA_DUMP:SBTIO.LOG with TR_GENINFO and TR_MEDINFO values enabled. Note that the SBT-00008140 is the pid, in hexadecimal, of the process doing the backup with SBT- prepended. Example 9–18 ORA_DUMP:SBTIO.LOG with TR_GENINFO and TR_MEDINFO Values Enabled EDINFO Values Enabled SBT-00008140 12/17/01 09:27:11 Using archive RMAN_TAPE_TL875_ARCH SBT-00008140 12/17/01 09:27:12 Starting backup of r1dbtgjd_1_1 for DB: EMPLOYEE SBT-00008140 12/17/01 09:27:12 Using catalog ORACLE_DB SBT-00008140 12/17/01 09:27:12 Allocated drive: MKC200 Device: MOE$MKC200: SBT-00008140 12/17/01 09:27:13 Drive is in jukebox TLZ875 SBT-00008140 12/17/01 09:27:13 Allocated volume AIF078 SBT-00008140 12/17/01 09:27:17 Unloading drive MKC200 SBT-00008140 12/17/01 09:27:46 Loading volume AIF078 on drive MKC200 SBT-00008140 12/17/01 09:28:39 Deallocating drive MKC200 SBT-00008140 12/17/01 09:28:39 Initializing volume AIF078 SBT-00008140 12/17/01 09:29:00 Allocated drive: MKC200 Device: MOE$MKC200: SBT-00008140 12/17/01 09:29:00 Drive is in jukebox TLZ875 SBT-00008140 12/17/01 09:29:00 Loading/mounting volume AIF078 on drive MKC200 SBT-00008140 12/17/01 09:29:00 Loading volume AIF078 on drive MKC200 SBT-00008140 12/17/01 09:29:09 Mounting volume AIF078 on device MOE$MKC200: SBT-00008140 12/17/01 09:29:18 Ready to write to saveset 2001121709291582. on volume AIF078 SBT-00008140 12/17/01 09:30:47 Using catalog ORACLE_DB SBT-00008140 12/17/01 09:30:48 Finished writing saveset 2001121709291582. on volume AIF078 We hope the only thing that might not be obvious in Example 9–18 is the saveset name. We are limited to 17 characters so I change piece name, r1dbtgjd_1_1, into a saveset name, 2001121709291582., on a particular volume. Another value that you may want to use is TR_TAPSTAT. This gives you statistics about the reading/writing to a tape volume. Example 9–19 shows an example of tape statistics. Example 9–19 Trace of Tape Statistics SBT-00008140 12/17/01 09:50:49 I/O Statistics: SBT-00008140 12/17/01 09:50:49 DB block size: 262144 bytes 1 SBT-00008140 12/17/01 09:50:50 I/O block size: 65024 bytes 2 SBT-00008140 12/17/01 09:50:50 Total I/Os: 620 3 SBT-00008140 12/17/01 09:50:50 Total I/O wait: 23279 milliseconds 4 SBT-00008140 12/17/01 09:50:50 Maximum I/O wait: 936 milliseconds 5 SBT-00008140 12/17/01 09:50:50 Average I/O wait: 37 milliseconds 6 SBT-00008140 12/17/01 09:50:50 Total Kbytes: 40300 7 SBT-00008140 12/17/01 09:50:50 Total bytes: 40314880.000 8 SBT-00008140 12/17/01 09:50:50 Total seconds: 23 9 System Backup to Tape for Oracle Databases 9–21
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 111 and 112: User Interfaces 6.1 Graphical User
Page 113 and 114: Figure 6-5 Domain View Showing Expa
Page 115 and 116: User Interfaces 6.1 Graphical User
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: Migrating from SLS/MDMS V2.X to ABS
Page 213 and 214:
Migrating from SLS/MDMS V2.X to ABS
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?