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
Virtual Library System (VLS) 10.3 Qualification 10.3Qualification • RAID 5: RAID 5 provides protection for your data should a drive fail. • Flexibility in configuration: You can integrate HP VLS into a HP rack with your other storage and server devices. • Simulation capacity: HP VLS allows simulation of the following six types of drives: DLT7000, DLT8000, SDLT320, LTO1, LTO2, and LTO3. VLS is qualified to be used with ABS/MDMS V4.3A and later versions. 10.4Restrictions while using VLS • When using VLS, volumes should be created with volume labels in uppercase only. • Since backup is not taken to a physical tape, volumes cannot be moved to any offsite location. 10-2 Virtual Library System (VLS)
11 Architecture 11.1 The Server Process This chapter describes in more technical details the ABS and MDMS infrastructure and implementation. Each OpenVMS node participating in an MDMS Domain runs a generic process called MDMS$SERVER. Each MDMS server process can implement 3 functions: • Current access to the database, the database server • Forwarding a user request to the current database server • Executing remote requests on behalf of the database server Domain All nodes communicating with the same database server belong to the same MDMS Domain. Each MDMS Domain has its own database. Typically you have only one MDMS Domain in your network. But the architecture allows to setup more than one domain. However, one has to make sure that none of the nodes and none of the MDMS objects (i.e jukeboxes) are used in more than one domain. 11.1.1 The Database (DB) Server 11.1.1.1 Database MDMS keeps all its permanent settings in files in a location defined by logical MDMS$DATA- BASE. The summary of these files are called the MDMS Database. Each MDMS server needs access to the MDMS database before it is fully functional. The server translates logical name MDMS$DATABASE_SERVERS which contains a list of potential database server nodes. This logical is defined in MDMS$SYSTARTUP.COM and contains the network names of other servers. Because the server has not yet accessed the database it cannot use an MDMS node name. While scanning through the database servers list the server tries to contact the remote server using the appropriate network for a given network name: • DECnet, if only alphanumeric characters, e.g. “STAR” • DECnet-Plus, if network name contains “:.”, e.g. “VMS:.STAR” • TCP/IP, if network name contains just dots “.” and a possible colon “:” followed by a number range, e.g. “star.vms.com” or “star.vms.com:2501-2510” Following are examples of valid TCPIP and DECnet names. Valid DECnet node names: DEC:.CXO.FARMS[::] NABSCO[::] - Phase IV - Phase V Architecture 11–1
- 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: System Backup to Tape for Oracle Da
- Page 148 and 149: System Backup to Tape for Oracle Da
- Page 150 and 151: System Backup to Tape for Oracle Da
- Page 152 and 153: System Backup to Tape for Oracle Da
- Page 154 and 155: System Backup to Tape for Oracle Da
- Page 156 and 157: System Backup to Tape for Oracle Da
- Page 158 and 159: System Backup to Tape for Oracle Da
- Page 160 and 161: System Backup to Tape for Oracle Da
- Page 162 and 163: System Backup to Tape for Oracle Da
- Page 164 and 165: System Backup to Tape for Oracle Da
- Page 166 and 167: System Backup to Tape for Oracle Da
- Page 168 and 169: System Backup to Tape for Oracle Da
- Page 170 and 171: System Backup to Tape for Oracle Da
- Page 172 and 173: System Backup to Tape for Oracle Da
- 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: Migrating from SLS/MDMS V2.X to ABS
- Page 217 and 218: Migrating from SLS/MDMS V2.X to ABS
- Page 219 and 220: Migrating from SLS/MDMS V2.X to ABS
- Page 221 and 222: Migrating from SLS/MDMS V2.X to ABS
- Page 223 and 224: Migrating from SLS/MDMS V2.X to ABS
Virtual Library <strong>System</strong> (VLS)<br />
10.3 Qualification<br />
10.3Qualification<br />
• RAID 5:<br />
RAID 5 provides protection <strong>for</strong> your data should a drive fail.<br />
• Flexibility in configuration:<br />
You can integrate <strong>HP</strong> VLS in<strong>to</strong> a <strong>HP</strong> rack with your other s<strong>to</strong>rage and server devices.<br />
• Simulation capacity:<br />
<strong>HP</strong> VLS allows simulation of the following six types of drives: DLT7000, DLT8000,<br />
SDLT320, LTO1, LTO2, and LTO3.<br />
VLS is qualified <strong>to</strong> be used with ABS/MDMS V4.3A and later versions.<br />
10.4Restrictions while using VLS<br />
• When using VLS, volumes should be created with volume labels in uppercase only.<br />
• Since backup is not taken <strong>to</strong> a physical tape, volumes cannot be moved <strong>to</strong> any offsite location.<br />
10-2 Virtual Library <strong>System</strong> (VLS)
Change language