HP Archive Backup System for OpenVMS Guide to Operations

More documents

Recommendations

Info

Upgrading from ABS V2.X/V3.X to V4.x Environment D.2 Upgrading from ABS/MDMS V2.x/V3.x to V4.x Sample Conversion – $ RUN SYS$SYSTEM:ABS$CONVERT_V3_TO_V4.EXE Enter the Path of ABS V3.x Policy Database Files [ABS$DATABASE:] : Converting ARCHIVE Objects... Converting ENVIRONMENT Objects... Converting SAVE Objects... Converting RESTORE Objects...$ Additional Information – The additional information on backing up of Oracle database, managing history files and running SLS and ABS/MDMS simultaneously help you to manage the backups effectively. Backing up Oracle Database – Oracle RDB backups are available in ABS/MDMS as it was in SLS. When a Save request in created, select the appropriate DATA_SELECT_TYPE for the version and the area of RDB that you want to backup. This will automatically create the SELECTION policy. The backup must be scheduled as any other ABS/MDMS backup. Though not required, it would be a good practice to create a CATALOG for only these types of backups. Note ABS/MDMS can also backup up Oracle 8i and 9i databases. However, this functionality is not available in SLS. Refer to Chapter 9, “System Backup to Tape for Oracle Databases” on how to set up the Oracle database. Managing the SLS data in History Files. Currently there is no functionality for reading the SLS history files from ABS/MDMS and initiating a backup. Two scenarios are available for recovering pre ABS/MDMS data from SLS: • Keep an instance of SLS running for history lookups only. The SLS and ABS licenses will support this environment. Once information is located in SLS, initiate a restore manual restore command using the Backup utility. • Capture data from SLS volumes and feed data directly into ABS catalogs. This can prove to be a large task so it is important to consider which backups may need to be restored mostly commonly. To catalog existing savesets, create a SAVE policy as follows: – MDMS CREATE SAVE mysaveset_catalog – – /INCLUDE=yourtape:*- – /DATA_TYPE=VMS_SAVESET- – /ARCHIVE=my_archive- – /ENVIRONMENT=my_environment – /START=your_start_time The data from the tape will be written to the catalog designated by the ARCHIVE Policy. D–4 Upgrading from ABS V2.X/V3.X to V4.x Environment
E ABS/MDMS Support for Fibre Channel E.1 Introduction The following section describes the support by the ABS/MDMS for the Fibre Channel (FC) connected devices. It discusses the configurations supported and restrictions if any. Fibre Channel, a highly-reliable, gigabit interconnect technology allows concurrent, guaranteed delivery communications among workstations, mainframes, servers, data storage systems, and other peripherals using SCSI and IP protocols. FC offers significant speed, distance and cost advantages. Computer and storage systems can be separated and distributed efficiently with FC. The ability to easily share resources amongst systems is both a major benefit and a possible source of problems. This section assumes basic level of familiarity with FC protocol and configuration and administration of FC connected device. Refer chapter 7, Configuring Fibre Channel as an OpenVMS Cluster Storage Interconnect, of the Guidelines for OpenVMS Cluster Configurations manual (April 2001) for details on • Tape and Medium Changer Device Names • Configuring a Fibre Channel Tape Device • Changing the Name of an Existing Fibre Channel Tape Device • Moving a Physical Tape Device on Fibre Channel • Serving a Fibre Channel Tape Device • Replacing a Fibre Channel Tape Device • Determining the Physical Location of a Fibre Channel Tape Device OpenVMS V7.3 documentation are available online at http://www.openvms.hp.com:8000/ E.2 Issues with sharing FC connected devices Hosts on the fabric can be configured as a single cluster or as multiple clusters and/or non-clustered nodes. Devices connected over the FC can potentially be visible to all the servers on the storage area network. For the purposes of this paper, we will assume that all of the systems are running OpenVMS so that communications between non-clustered systems will be well defined. Note Fibre Channel is not directly supported on VAX computers. However, VAX computers within a VMScluster can access FibreChannel devices that are (T)MSCP-Served by one or more Alpha computers within the same VMScluster. SMS software supports this configuration and provides access and control of robot device(s) not directly visible by the VAX computers. ABS/MDMS Support for Fibre Channel E–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 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:
Page 113 and 114:
Figure 6-5 Domain View Showing Expa
Page 115 and 116:
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 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
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: Migrating from SLS/MDMS V2.X to ABS
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 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 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?