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 Sample Conflicts File – The following sample conflicts file shows the commands that created the conflict. Conflicts file name: MDMS$SYSTEM:MDMS$LOAD_DB_CONFLICTS_NODE1.COM $ MDMS SET DOMAIN/ONSITE_LOCATION=HEADQUARTERS/OFFSITE_LOCATION=ABC $ MDMS SET DOMAIN /NETWORK_TIMEOUT=0-0:0:0 $ MDMS SET DOMAIN /SCRATCH_TIME=30-0:0:0 $ MDMS SET DOMAIN /TRANSITION_TIME=0-0:0:0 $ MDMS SET DOMAIN /MAXIMUM_SCRATCH_TIME=0-00:00:00 $ MDMS SET DOMAIN /DEALLOCATE_STATE=FREE $ MDMS SET DOMAIN/MEDIA_TYPE=SLS_MEDIA $ MDMS SET NODE Test/DATABASE_SERVER/ENABLE/DECNET_FULLNAME=LOCAL:.Test/LOC=HEADQ $ MDMS SET MEDIA_TYPE SLS_MEDIA/COMP $ MDMS SET DRIVE $1$ABC500/ADD/NODES=Test_1 $ MDMS SET DOMAIN/MEDIA_TYPE=SLS_MEDIA is one of the conflicts logged. It implies that two media types cannot have the same name in ABS/MDMS V4.x though it is permitted in SLS/MDMS V2.x. One of the media type name must be changed to resolve this conflict. Table B–3 (Symbols in TAPESTART.COM and the Corresponding MDMS Objects) describes the SLS/MDMS V2.x TAPESTART.COM Symbols and their equivalent ABS/MDMS V4.x attributes or objects, and the possible conflict that can result if the TAPESTART.COM Symbol definitions are not accepted in the ABS/MDMS V4.x environment. B–22 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 Table B–3 TAPESTART.COM Symbols and the Corresponding MDMS Objects TAPESTART.COM Symbol ALLOCSCRATCH DB_NODES DCSC_n_NODES DCSC_DRIVES DENS_x FRESTA LOC MDMS V4 Attribute or Object If defined, adds the SCRATCH_TIME attribute to the domain object. If defined, creates a node object for the nodes in the DB_NODES list. If defined, creates a node object and adds the “NODE” attribute to the DCSC jukebox. If defined, creates a drive object for DCSC. If defined, adds the density or compaction attribute to a media type. If the value is “COMP” or “NOCOMP” then the compaction attribute is defined as “YES” or “NO”. If the density is anything other than “COMP” or “NOCOMP”, then the value is placed in the “Density” attribute. If defined, adds the deallocate state attribute to the domain object. Creates a location object and also sets the “ONSITE_LOCATION” attribute in domain object. Possible Conflict If the ALLOCSCRATCH symbol is different in different TAPESTART.com files, the modified ALLOCSCRATCH value resulting in the conflict is added to the conflicts file. A conflict can be added if the node exists and an attribute changed in a different TAPESTART.COM file. Every drive and jukebox definition in the TAPE- START.COM can cause a node to be created with a /NODATABASE_SERVER qualifier. A DB node will change the attribute to database server, this can cause a conflict to be added to the conflicts file. All addition of nodes to jukeboxes cause a conflict to be added to the conflicts file. When adding attributes, if an attribute is found to be different, then that attribute is added to the conflicts file. If the DENS_x is different for the same media type, then that DENS_x value is added to the conflicts file. If the FRESTA symbol is different in different TAPESTART.COM files, then that Fresta value resulting in the conflict is added to the conflicts file. If the location object exists or is different than the “ONSITE LOCATION” attribute set in the domain object, then that LOC value resulting in the conflict is added to the conflicts file. This conflict can result if you have different LOC symbols in two TAPESTART.COM files. Migrating from SLS/MDMS V2.X to ABS/MDMS V4.X B–23
- 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
- Page 225: 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-
- Page 275 and 276: MDMS$SBT_ ARCHIVE_n 9-20 MDMS$SBT_
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 />
Table B–3 TAPESTART.COM Symbols and the Corresponding MDMS Objects<br />
TAPESTART.COM<br />
Symbol<br />
ALLOCSCRATCH<br />
DB_NODES<br />
DCSC_n_NODES<br />
DCSC_DRIVES<br />
DENS_x<br />
FRESTA<br />
LOC<br />
MDMS V4 Attribute or<br />
Object<br />
If defined, adds the<br />
SCRATCH_TIME<br />
attribute <strong>to</strong> the domain object.<br />
If defined, creates a node object<br />
<strong>for</strong> the nodes in the<br />
DB_NODES list.<br />
If defined, creates a node object<br />
and adds the “NODE” attribute<br />
<strong>to</strong> the DCSC jukebox.<br />
If defined, creates a drive object<br />
<strong>for</strong> DCSC.<br />
If defined, adds the density or<br />
compaction attribute <strong>to</strong> a media<br />
type. If the value is “COMP” or<br />
“NOCOMP” then the compaction<br />
attribute is defined as<br />
“YES” or “NO”. If the density<br />
is anything other than “COMP”<br />
or “NOCOMP”, then the value<br />
is placed in the “Density”<br />
attribute.<br />
If defined, adds the deallocate<br />
state attribute <strong>to</strong> the domain<br />
object.<br />
Creates a location object and<br />
also sets the<br />
“ONSITE_LOCATION”<br />
attribute in domain object.<br />
Possible Conflict<br />
If the ALLOCSCRATCH symbol is different<br />
in different TAPESTART.com<br />
files, the modified ALLOCSCRATCH<br />
value resulting in the conflict is added <strong>to</strong><br />
the conflicts file.<br />
A conflict can be added if the node exists<br />
and an attribute changed in a different<br />
TAPESTART.COM file. Every drive<br />
and jukebox definition in the TAPE-<br />
START.COM can cause a node <strong>to</strong> be<br />
created with a<br />
/NODATABASE_SERVER qualifier. A<br />
DB node will change the attribute <strong>to</strong><br />
database server, this can cause a conflict<br />
<strong>to</strong> be added <strong>to</strong> the conflicts file.<br />
All addition of nodes <strong>to</strong> jukeboxes cause<br />
a conflict <strong>to</strong> be added <strong>to</strong> the conflicts<br />
file.<br />
When adding attributes, if an attribute is<br />
found <strong>to</strong> be different, then that attribute<br />
is added <strong>to</strong> the conflicts file.<br />
If the DENS_x is different <strong>for</strong> the same<br />
media type, then that DENS_x value is<br />
added <strong>to</strong> the conflicts file.<br />
If the FRESTA symbol is different in different<br />
TAPESTART.COM files, then<br />
that Fresta value resulting in the conflict<br />
is added <strong>to</strong> the conflicts file.<br />
If the location object exists or is different<br />
than the “ONSITE LOCATION”<br />
attribute set in the domain object, then<br />
that LOC value resulting in the conflict<br />
is added <strong>to</strong> the conflicts file. This conflict<br />
can result if you have different LOC<br />
symbols in two TAPESTART.COM<br />
files.<br />
Migrating from SLS/MDMS V2.X <strong>to</strong> ABS/MDMS V4.X B–23
Change language