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 Table B–4 Verifying Objects and their Attributes after the Conversion Object Attribute Description/Verification Drive Drive Ensure that all the drives are defined during the conversion. In the MDMS V3 domain, you can have only one drive with a given name. But, in MDMS V2.x, you could have two drives with the same name provided they were in different TAPE- START.COM files. Ensure that all drives in your domain are in the database. Example: You can create two drives named “DRIVE1” and “DRIVE2”. • “DRIVE1” has the device name as “$1$MUA520” and the node name as “NODE1”. • “DRIVE2” has the device name as “$1$MUA520” and the node name as “NODE2”. Every time a node is added to the drive, a conflict is added to the conflict file. This prompts you to verify if the node really belongs to this drive or if you need to create another drive. Description Device Nodes Disabled State Automatic reply RW media types RO Media Types Access Jukebox Drive Number This attribute is left blank during the conversion. Ensure that you provide the appropriate description after the conversion. Ensure that only the device name is displayed after the conversion. The node name must not be a part of the device name. Ensure that the list of node(s) displayed are the node(s) that can communicate with the drive. The conversion program enables all the drives. If you want the drive disabled, then set the “DISABLED” attribute to “YES”. Ensure that the drive is in the appropriate state. If not, set the “STATE” attribute to the appropriate value. You can also verify the state by issuing the following command: $ MDMS SHOW DRIVE /CHECK This attribute is set from the QUICKLOAD symbol (SLS/MDMS V2.x). Ensure that it is the intended drive behavior. The conversion program, as and when it finds a media type(s), immediately adds it to the drive. Make sure the one that is added is the correct read-write media type(s) for the drive. There is no read-only media type(s) in MDMS V2.x. So, it is not added to the drives during the conversion. If needed, you can add read-only media type(s) to the drive object. The conversion program is not aware of the access type that must be set. Hence, it sets the access to “ALL”. Ensure that it is the access type that you want to be set for the drive. Ensure that the jukebox name displayed is the one that the drive belongs to. Ensure that the drive number displayed is the one that is used for the robot commands on the drive. B–26 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 Object Attribute Description/Verification Domain Description Ensure that the description displayed is appropriate for the domain. The default description is: Default MDMS Domain. Mail Ensure that the account displayed is the intended recepient for the e-mails sent when a volume reaches its scratch date and MDMS deallocates it. If you do not want any e-mails sent, then leave the “Mail” field blank. The default recepient is “SYSTEM”. Offsite location Onsite location Default media type Deallocate state Opcom classes Protection Maximum scratch time Scratch time Transition time Network timeout Ensure that the offsite location displayed is the default location for the objects that you create. This default value is set from the value defined for the VLT symbol in the TAPESTART.COM. It can be different in different TAPESTART.COM files. Ensure that the onsite location displayed is the default location for the objects that you create. Ensure that the media type displayed is the default media type you want to be assigned to volumes that do not have a media type specified when they are created. Ensure that the deallocate state displayed is the default state you want volumes to move to, once they reach their scratch date. The state can be modified every time you convert the TAPE- START.COM on a new node. Ensure that the Opcom Classe(s) displayed is the one that should receive all the MDMS Opcom messages. The Opcom Class can be modified every time you convert the TAPE- START.COM on a new node. Ensure that the protection displayed is the default protection that is assigned to volumes for which the protection is not specified. Ensure that the maximum scratch time value displayed is the default value to be assigned for volumes in your domain. The maximum scratch time can be modified every time you convert the TAPESTART.COM on a new node. Ensure that the scratch time value displayed is the default value to be assigned for volumes in your domain. The scratch time can be modified every time you convert the TAPESTART.COM on a new node. Ensure that the transition time value displayed is the default value assigned to volumes in your domain. The transition time can be modified every time you convert the TAPESTART.COM on a new node. Ensure that the network timeout value displayed is the default timeout value that you want. The network timeout value can be modified every time you convert the TAPESTART.COM on a new node. Location Description Ensure that you provide the appropriate description for the location after the conversion is completed. By default, the description is not provided during the conversion. Spaces Ensure that you set the spaces after the conversion is completed. By default, the spaces are not set during the conversion. Migrating from SLS/MDMS V2.X to ABS/MDMS V4.X B–27
- 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 and 228: Migrating from SLS/MDMS V2.X to ABS
- Page 229: 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 />
Object Attribute Description/Verification<br />
Domain Description Ensure that the description displayed is appropriate <strong>for</strong> the<br />
domain. The default description is: Default MDMS Domain.<br />
Mail<br />
Ensure that the account displayed is the intended recepient <strong>for</strong><br />
the e-mails sent when a volume reaches its scratch date and<br />
MDMS deallocates it. If you do not want any e-mails sent, then<br />
leave the “Mail” field blank.<br />
The default recepient is “SYSTEM”.<br />
Offsite location<br />
Onsite location<br />
Default media<br />
type<br />
Deallocate state<br />
Opcom classes<br />
Protection<br />
Maximum<br />
scratch time<br />
Scratch time<br />
Transition time<br />
Network timeout<br />
Ensure that the offsite location displayed is the default location<br />
<strong>for</strong> the objects that you create. This default value is set from the<br />
value defined <strong>for</strong> the VLT symbol in the TAPESTART.COM. It<br />
can be different in different TAPESTART.COM files.<br />
Ensure that the onsite location displayed is the default location<br />
<strong>for</strong> the objects that you create.<br />
Ensure that the media type displayed is the default media type<br />
you want <strong>to</strong> be assigned <strong>to</strong> volumes that do not have a media<br />
type specified when they are created.<br />
Ensure that the deallocate state displayed is the default state you<br />
want volumes <strong>to</strong> move <strong>to</strong>, once they reach their scratch date.<br />
The state can be modified every time you convert the TAPE-<br />
START.COM on a new node.<br />
Ensure that the Opcom Classe(s) displayed is the one that<br />
should receive all the MDMS Opcom messages. The Opcom<br />
Class can be modified every time you convert the TAPE-<br />
START.COM on a new node.<br />
Ensure that the protection displayed is the default protection<br />
that is assigned <strong>to</strong> volumes <strong>for</strong> which the protection is not specified.<br />
Ensure that the maximum scratch time value displayed is the<br />
default value <strong>to</strong> be assigned <strong>for</strong> volumes in your domain. The<br />
maximum scratch time can be modified every time you convert<br />
the TAPESTART.COM on a new node.<br />
Ensure that the scratch time value displayed is the default value<br />
<strong>to</strong> be assigned <strong>for</strong> volumes in your domain. The scratch time<br />
can be modified every time you convert the TAPESTART.COM<br />
on a new node.<br />
Ensure that the transition time value displayed is the default<br />
value assigned <strong>to</strong> volumes in your domain. The transition time<br />
can be modified every time you convert the TAPESTART.COM<br />
on a new node.<br />
Ensure that the network timeout value displayed is the default<br />
timeout value that you want. The network timeout value can be<br />
modified every time you convert the TAPESTART.COM on a<br />
new node.<br />
Location Description Ensure that you provide the appropriate description <strong>for</strong> the location<br />
after the conversion is completed. By default, the description<br />
is not provided during the conversion.<br />
Spaces<br />
Ensure that you set the spaces after the conversion is completed.<br />
By default, the spaces are not set during the conversion.<br />
Migrating from SLS/MDMS V2.X <strong>to</strong> ABS/MDMS V4.X B–27
Change language