HP Archive Backup System for OpenVMS Guide to Operations

More documents

Recommendations

Info

Preparing For Disaster Recovery 7.3 Non-OpenVMS Systems Example 7–6 BACKUP Command to Restore ABS$ROOT $ BACKUP/NOASSIST/OVERLAY - $_MKA500:25DEC20010101010./LABEL=(GKF033,GKF044)- $_DGA100:[VMS$COMMON.ABS.*...]/LOG Because ABS has not been started up the ABS$ROOT logical is not available yet. This restores the ABS$ROOT files in saveset “24DEC20012359590.” on tape volumes “GKF033” and “GKF044” to disk location “DGA100:[VMS$COMMON.ABS...]”. This assumes that you ABS$ROOT logical was defined as a concealed device name of “DGA100:[VMS$COMMON.ABS.]”. 7.3 Non-OpenVMS Systems Note It is important to note the full pathname when you save these components or products. ABS cannot restore a bootable system disk of a non-OpenVMS system. Therefore you need to be able to save and restore the system disk locally. Once you have the system disk restored and booted the system you have to install the ABS client software for that platform. Once the ABS client software has been installed you can use ABS on your OpenVMS system to restore data to the client node. 7.4 Thoughts on Save and Restore Procedures When it comes to setup procedures on how to save and restore files for disaster recovery there is a variety of possibilities depending on your configuration and other system activities. You do not need to have an up-to-date copy of your system disk to restore your ABS environment. You could start with a fresh installation of OpenVMS. Install ABS and products required to run ABS (e.g. a 3rd party scheduler). While ABS is shutdown restore the MDMS$ROOT and ABS$ROOT and other required components. Startup ABS to restore all the rest of your data. Or in a VMSCluster with more than one system disk you may be able to restore all your data online using ABS from another node in the cluster. You can keep a printout of the ABS save log in a safe place. This allows you to restore the data for files on OpenVMS systems using OpenVMS BACKUP. You need to keep the volume IDs, the name of the save sets and the include specifications used in the save operation. Typically you do not want to keep multiple copies of your disaster recovery saves. You may want to keep 2 copies. So, if you are doing daily disaster recovery saves the archive expiration should be set to 2 days. You should use non-incremental saves for the disaster recovery. This allows for an easy restore in case of an emergency. You can use incremental saves, but on a restore you have to do all the incremental restores on your own until you have ABS fully up-and-running Note And a final word: Make sure that you have a clear procedure on how to do a disaster recovery. Test your disaster recovery procedure! 7-8 Preparing For Disaster Recovery
8 Remote Devices 8.1 RDF Installation 8.2 Configuring RDF This chapter explains how to configure and manage remote devices using the Remote Device Facility (RDF). RDF is used for devices remotely connected over a wide-area network, and DECnet is still a requirement for access to these remote devices. RDF is not required for devices connected remotely via Fibre Channel, as these are considered local devices. When you install ABS (non-standard installation) or MDMS, you are asked whether you want to install the RDF software. With the ABS standard installation, the RDF client and server software is installed by default. During the installation you place the RDF client software on the nodes with disks you want to access for ABS or HSM. You place the RDF server software on the systems to which the tape devices (jukeboxes and drives) are connected. This means that when using RDF, you serve the tape device to the systems with the client disks. All of the files for RDF are placed in SYS$COMMON:[MDMS.TTI_RDF] for your system. There are separate locations for VAX or Alpha. Note RDF is available on OpenVMS Alpha V8.3 RDF is not available under the following conditions: * For ABS-OMT license based installation * On OpenVMS I64 After installing RDF you should check the TTI_RDEV:CONFIG_nodename.DAT file to make sure it has correct entries. This file: • is located on the RDF server node with the tape device • is created initially during installation • is a text file • includes the definition of each device accessible by the RDF software. This definition consists of a physical device name and an RDF characteristic name. Example: Verify: Device $1$MIA0 MIAO Remote Devices 8–1
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 92 and 93: Media Management 4.11 Volumes neede
Page 94 and 95: Media Management 4.11 Volumes • R
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: 7.2.1 Restoring The System Disk To
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

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

Delete template?

Save as template?