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 TAPESTART.COM Symbol MAXSCRATCH MTYPE_x NET_REQUEST_TIM EOUT PROTECTION QUICKLOAD TAPE_JUKEBOXES MDMS V4 Attribute or Object If defined, adds the maximum scratch time attribute to the domain object. Creates a media type object for each MTYPE_x. If defined, adds the “NETWORK_TIMEOUT” attribute to the domain object. Adds the default protection to the domain object. When drives are created, the “QUICKLOAD” attribute is added as automatic reply. Creates a jukebox object for each jukebox in the list. Possible Conflict If the MAXSCRATCH symbol is different in different TAPESTART.COM files, then that MAXSCRATCH value resulting in the conflict is added to the conflicts file. If the media type is duplicated, the duplicate media type name is added to the conflicts file. In SLS/MDMS V2.x, you can have the same media type name with Compaction and Nocompaction attributes set. But, in ABS/MDMS V4.x, you cannot have duplicate media types. You need to change the name of one of the media type and enter it into the database again. You might have to change ABS or HSM and the respective volume, and drive objects to reflect the media type change. If the NET_REQUEST_TIMEOUT is different in different TAPE- START.COM files, then that TIMEOUT value resulting in the conflict is added to the conflicts file. If the PROTECTION is different in different TAPESTART.COM files, then that “PROTECTION” attribute resulting in the conflict is added to the conflicts file. If the drive’s automatic reply is changed, then the modified attribute resulting in the conflict is added to the conflicts file. If the jukebox is already defined and any of the attributes change, the changed attribute resulting in the conflict is added to the conflicts file. TAPEPURGE_MAIL If defined, adds the “MAIL” attribute to the domain object. If the TAPEPURGE_MAIL is different in different TAPESTART.COM files, then that TAPEPURGE_MAIL value resulting in the conflict is added to the conflicts file. TOPERS TRANS_AGE If defined, adds the “OPCOM CLASS” attribute to the domain object. If defined, adds the “TRAN- SITION TIME” attribute to the domain object. If the TOPERS symbol is different in different TAPESTART.COM files, then that TOPERS symbol resulting in the conflict is added to the conflicts file. If the TRANS_AGE symbol is different in different TAPESTART.COM files, then that TRANS_AGE symbol resulting in the conflict is added to the conflicts file. B–24 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 TAPESTART.COM Symbol VLT MDMS V4 Attribute or Object Creates a location object and also sets the “OFFSITE_LOCATION” attribute in the domain object. Possible Conflict If the object exists or is different than the “OFFSITE_LOCATION” attribute in the domain object, then that VLT value resulting in the conflict is added to the conflicts file. The conflict can result if you have different VLT symbols in two Tapestart.Com files. B.2.4.1.4 Verifying Objects and their Attributes after the Conversion – There are possibilities that the object’s attributes are modified after the conversion due to the differences between MDMS V2.x and MDMS V4.x. Ensure that the attributes you want are set for each of the objects. Table B–4 (Verifying Objects and their Attributes after the Conversion) lists the objects, their attributes that must be set and appropriate descriptions for the same. Migrating from SLS/MDMS V2.X to ABS/MDMS V4.X B–25
- 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
- Page 225 and 226: Migrating from SLS/MDMS V2.X to ABS
- Page 227: 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-
- Page 275 and 276: MDMS$SBT_ ARCHIVE_n 9-20 MDMS$SBT_
- Page 277: volumes 3-4 W WARNING 3-14, 3-31 WE
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 />
TAPESTART.COM<br />
Symbol<br />
MAXSCRATCH<br />
MTYPE_x<br />
NET_REQUEST_TIM<br />
EOUT<br />
PROTECTION<br />
QUICKLOAD<br />
TAPE_JUKEBOXES<br />
MDMS V4 Attribute or<br />
Object<br />
If defined, adds the maximum<br />
scratch time attribute <strong>to</strong> the<br />
domain object.<br />
Creates a media type object <strong>for</strong><br />
each MTYPE_x.<br />
If defined, adds the<br />
“NETWORK_TIMEOUT”<br />
attribute <strong>to</strong> the domain object.<br />
Adds the default protection <strong>to</strong><br />
the domain object.<br />
When drives are created, the<br />
“QUICKLOAD” attribute is<br />
added as au<strong>to</strong>matic reply.<br />
Creates a jukebox object <strong>for</strong><br />
each jukebox in the list.<br />
Possible Conflict<br />
If the MAXSCRATCH symbol is different<br />
in different TAPESTART.COM<br />
files, then that MAXSCRATCH value<br />
resulting in the conflict is added <strong>to</strong> the<br />
conflicts file.<br />
If the media type is duplicated, the duplicate<br />
media type name is added <strong>to</strong> the<br />
conflicts file. In SLS/MDMS V2.x, you<br />
can have the same media type name with<br />
Compaction and Nocompaction<br />
attributes set. But, in ABS/MDMS V4.x,<br />
you cannot have duplicate media types.<br />
You need <strong>to</strong> change the name of one of<br />
the media type and enter it in<strong>to</strong> the database<br />
again. You might have <strong>to</strong> change<br />
ABS or HSM and the respective volume,<br />
and drive objects <strong>to</strong> reflect the media<br />
type change.<br />
If the NET_REQUEST_TIMEOUT is<br />
different in different TAPE-<br />
START.COM files, then that TIMEOUT<br />
value resulting in the conflict is added <strong>to</strong><br />
the conflicts file.<br />
If the PROTECTION is different in different<br />
TAPESTART.COM files, then that<br />
“PROTECTION” attribute resulting in<br />
the conflict is added <strong>to</strong> the conflicts file.<br />
If the drive’s au<strong>to</strong>matic reply is changed,<br />
then the modified attribute resulting in<br />
the conflict is added <strong>to</strong> the conflicts file.<br />
If the jukebox is already defined and any<br />
of the attributes change, the changed<br />
attribute resulting in the conflict is added<br />
<strong>to</strong> the conflicts file.<br />
TAPEPURGE_MAIL If defined, adds the “MAIL”<br />
attribute <strong>to</strong> the domain<br />
object.<br />
If the TAPEPURGE_MAIL is different<br />
in different TAPESTART.COM<br />
files, then that TAPEPURGE_MAIL<br />
value resulting in the conflict is<br />
added <strong>to</strong> the conflicts file.<br />
TOPERS<br />
TRANS_AGE<br />
If defined, adds the<br />
“OPCOM CLASS” attribute<br />
<strong>to</strong> the domain object.<br />
If defined, adds the “TRAN-<br />
SITION TIME” attribute <strong>to</strong><br />
the domain object.<br />
If the TOPERS symbol is different<br />
in different TAPESTART.COM files,<br />
then that TOPERS symbol resulting<br />
in the conflict is added <strong>to</strong> the conflicts<br />
file.<br />
If the TRANS_AGE symbol is different<br />
in different TAPESTART.COM<br />
files, then that TRANS_AGE symbol<br />
resulting in the conflict is added<br />
<strong>to</strong> the conflicts file.<br />
B–24 Migrating from SLS/MDMS V2.X <strong>to</strong> ABS/MDMS V4.X