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
Migrating from SLS/MDMS V2.X to ABS/MDMS V4.X B.2 SLS/MDMS V2.x to ABS/MDMS V4.x Migration Note The device on which the SLS/MDMS V2.x databases are located must be provided for the conversion to proceed further. In a mixed-architecture (Alpha/VAX) OpenVMS Cluster, the SLS/MDMS V2.x TAPEMAST.DAT (volume database file), is typically located on a shared device accessible by both the Alpha and VAX nodes. You need to identify the device where the TAPEMAST.DAT file is located. – During the conversion, any command that caused a conflict or a change in the object when the MDMS$LOAD_DB_.COM was executed, is logged into a node specific conflicts file: Format: MDMS$LOAD_DB_CONFLICTS_.COM To view the conflicts file, you need to give the complete file name: MDMS$SYSTEM:MDMS$LOAD_DB_CONFLICTS_.COM For information on resolving conflicts, see Section B.2.4.1.3, “Resolving Conflicts during the Conversion”. Note This conversion must be executed on every node that has a different TAPE- START.COM and populates the MDMS database. 2. Adding the nodes from the Database Access Authorization file (VALIDATE.DAT) to the Node database. This addition/part of the conversion is executed only once on the database server node. – The conversion process prompts you to restart the MDMS server as the server must be active for the database to be populated with the node objects. On providing your consent, the conversion process automatically restarts the MDMS server. 3. Converting the following SLS/MDMS V2.x database files to ABS/MDMS V4.x database files: – Pool Authorization file (POOLAUTH.DAT) – Slot Definition file (SLOTMAST.DAT) – Volume Database file (TAPEMAST.DAT) – Magazine Database file (SLS$MAGAZINE_MASTER_FILE.DAT) This conversion is executed only once on the database server node. MDMS server should not be active during the conversion of the above-mentioned database files. The conversion process informs you that the MDMS server must be shutdown to proceed with the conversion. On providing your consent, the conversion process automatically shuts down the server and complete the conversion. Note On any other node that does not use the same TAPESTART.COM as the database node, in addition to converting the SBK (SLS System Backup) files, you also convert the TAPESTART.COM. B–20 Migrating from SLS/MDMS V2.X to ABS/MDMS V4.X
Migrating from SLS/MDMS V2.X to ABS/MDMS V4.X B.2 SLS/MDMS V2.x to ABS/MDMS V4.x Migration B.2.4.1.2 Executing the Conversion Command Procedure – This is an interactive command procedure wherein the conversion process prompts you for particular inputs. Based on the inputs received, it provides you the required information and also the intended outputs. The whole concept is about converting SLS/MDMS V2.x Symbols and Database objects into ABS/MDMS V4.x Database objects. When the command procedure is executed, a brief on what exactly are converted from SLS/MDMS V2.x and how they are converted is displayed. For more information, see Section B.2.4.1.1, “Phases in SLS/MDMS V2.x to ABS/MDMS V4.x Conversion”. Note SLS/MDMS V2.x DB server must be shut down before executing the conversion command procedure. Use the following command to shut down the SLS/MDMS V2.x DB server: $ @SLS$SYSTEM:SLS$SHUTDOWN To execute the conversion command procedure, type the following command at the DCL prompt (this command procedure is copied to MDMS$ROOT:[SYSTEM] during the ABS/MDMS installation): $ @MDMS$SYSTEM:MDMS$CONVERT_V2_TO_V4 • The conversion procedure at every stage prompts you on whether you want to proceed with the conversion or cancel it. • The conversion procedure in order to execute or complete certain sections of the conversion has to restart MDMS server. When informed, provide your consent and the conversion process automatically restarts MDMS server to complete the intended task. • The conversion procedure generates a conflicts file to log all the conflicts generated during the conversion. B.2.4.1.3 Resolving Conflicts during the Conversion – The differences between SLS/MDMS V2.x and ABS/MDMS V4.x result in conflicts during the conversion. Instead of stopping the conversion and prompting you to verify every conflict, the conversion program generates a node-specific conflicts file and logs all the conflicts for every conversion: $ TYPE MDMS$LOAD_DB_CONFLICTS_.COM In the above-mentioned file name, is replaced by the actual node name where the conversion procedure is executed. The conflicts file provides you the commands that were executed and which caused a change in the database. The change is flagged because there already existed an object in the database or that particular command changed an attribute of the existing object. Note The conflicts file must not be executed, instead you have to go through each and every conflict logged, and resolve it. Migrating from SLS/MDMS V2.X to ABS/MDMS V4.X B–21
- 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: 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: Migrating from SLS/MDMS V2.X to ABS
- Page 227 and 228: Migrating from SLS/MDMS V2.X to ABS
- Page 229 and 230: Migrating from SLS/MDMS V2.X to ABS
- Page 231 and 232: Migrating from SLS/MDMS V2.X to ABS
- Page 233 and 234: Migrating from SLS/MDMS V2.X to ABS
- Page 235 and 236: Migrating from SLS/MDMS V2.X to ABS
- Page 237 and 238: Migrating from SLS/MDMS V2.X to ABS
- Page 239 and 240: Migrating from SLS/MDMS V2.X to ABS
- Page 241 and 242: 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 249 and 250: Migrating from SLS/MDMS V2.X to ABS
- Page 251 and 252: Migrating from SLS/MDMS V2.X to ABS
- Page 253 and 254: Migrating from SLS/MDMS V2.X to ABS
- 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-
Migrating from SLS/MDMS V2.X <strong>to</strong> ABS/MDMS V4.X<br />
B.2 SLS/MDMS V2.x <strong>to</strong> ABS/MDMS V4.x Migration<br />
Note<br />
The device on which the SLS/MDMS V2.x databases are located must be provided <strong>for</strong><br />
the conversion <strong>to</strong> proceed further. In a mixed-architecture (Alpha/VAX) <strong>OpenVMS</strong><br />
Cluster, the SLS/MDMS V2.x TAPEMAST.DAT (volume database file), is typically<br />
located on a shared device accessible by both the Alpha and VAX nodes. You need <strong>to</strong><br />
identify the device where the TAPEMAST.DAT file is located.<br />
– During the conversion, any command that caused a conflict or a change in the object<br />
when the MDMS$LOAD_DB_.COM was executed, is logged in<strong>to</strong> a node<br />
specific conflicts file:<br />
Format: MDMS$LOAD_DB_CONFLICTS_.COM<br />
To view the conflicts file, you need <strong>to</strong> give the complete file name:<br />
MDMS$SYSTEM:MDMS$LOAD_DB_CONFLICTS_.COM<br />
For in<strong>for</strong>mation on resolving conflicts, see Section B.2.4.1.3, “Resolving Conflicts during<br />
the Conversion”.<br />
Note<br />
This conversion must be executed on every node that has a different TAPE-<br />
START.COM and populates the MDMS database.<br />
2. Adding the nodes from the Database Access Authorization file (VALIDATE.DAT) <strong>to</strong> the<br />
Node database. This addition/part of the conversion is executed only once on the database<br />
server node.<br />
– The conversion process prompts you <strong>to</strong> restart the MDMS server as the server must be<br />
active <strong>for</strong> the database <strong>to</strong> be populated with the node objects. On providing your consent,<br />
the conversion process au<strong>to</strong>matically restarts the MDMS server.<br />
3. Converting the following SLS/MDMS V2.x database files <strong>to</strong> ABS/MDMS V4.x database<br />
files:<br />
– Pool Authorization file (POOLAUTH.DAT)<br />
– Slot Definition file (SLOTMAST.DAT)<br />
– Volume Database file (TAPEMAST.DAT)<br />
– Magazine Database file (SLS$MAGAZINE_MASTER_FILE.DAT)<br />
This conversion is executed only once on the database server node.<br />
MDMS server should not be active during the conversion of the above-mentioned database<br />
files. The conversion process in<strong>for</strong>ms you that the MDMS server must be shutdown<br />
<strong>to</strong> proceed with the conversion. On providing your consent, the conversion<br />
process au<strong>to</strong>matically shuts down the server and complete the conversion.<br />
Note<br />
On any other node that does not use the same TAPESTART.COM as the database<br />
node, in addition <strong>to</strong> converting the SBK (SLS <strong>System</strong> <strong>Backup</strong>) files, you also convert<br />
the TAPESTART.COM.<br />
B–20 Migrating from SLS/MDMS V2.X <strong>to</strong> ABS/MDMS V4.X
Change language