06.11.2014 Views

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

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 />

Opcom classes<br />

Transports<br />

The Opcom class is defined in the domain object as an Opcom<br />

class when the node was created. Ensure that this is the Opcom<br />

class <strong>for</strong> this particular node.<br />

Ensure that the transport displayed is the one that you want <strong>for</strong><br />

this particular node. The conversion program cannot identify<br />

the transports that you want and hence takes only the defaults.<br />

POOL Description Ensure that you provide the appropriate description <strong>for</strong> the<br />

pool(s) after the conversion is completed. By default, the<br />

description is not provided during the conversion.<br />

Authorized<br />

users<br />

Ensure that the comma separated list contains the names of all<br />

the authorized users <strong>for</strong> the pool. The <strong>for</strong>mat <strong>for</strong> specifying an<br />

authorized user must be:<br />

NODE::user<br />

Default users<br />

Ensure that you specify the default users <strong>for</strong> the pool as the conversion<br />

program does not provide the default users list. The <strong>for</strong>mat<br />

<strong>for</strong> specifying a default user must be:<br />

NODE::user.<br />

VOLUME<br />

The conversion program provides all the necessary attributes.<br />

Type the following command <strong>to</strong> view the complete volume<br />

attributes.:<br />

MDMS SHOW VOLUME /FULL<br />

B.2.4.1.5 Upgrading the Domain <strong>to</strong> MDMS V4.x –<br />

Upgrading your SLS/MDMS V2 domain starts with the nodes, which have been defined as database<br />

servers in symbol DB_NODES in file TAPESTART.COM. See <strong>HP</strong> <strong>Archive</strong> <strong>Backup</strong> <strong>System</strong><br />

<strong>for</strong> <strong>OpenVMS</strong> Installation <strong>Guide</strong> <strong>for</strong> details on how <strong>to</strong> execute the following steps:<br />

1. Shut down all SLS/MDMS database servers in your SLS/MDMS domain.<br />

2. Install version MDMS V4 on nodes that were acting as database servers previously.<br />

3. When the new servers are up-and-running, veify and if possible change the configuration<br />

and database entries so that they match your previous SLS/MDMS V2 setup.<br />

4. Edit SYS$MANAGER:MDMS$SYSTARTUP.COM and ensure that:<br />

– Logical name MDMS$DATABASE_SERVERS includes the current node’s DECnet<br />

(Phase IV) node name.<br />

– Logical name MDMS$PREV3_SUPPORT is set <strong>to</strong> TRUE <strong>to</strong> enable the SLS/MDMS<br />

V2 support function in the new server.<br />

– Logical name MDMS$VERSION3 is set <strong>to</strong> TRUE <strong>to</strong> direct ABS and/or HSM <strong>to</strong> use<br />

the new MDMS V4 interface.<br />

If you had <strong>to</strong> change any of the previous logical name settings, you have <strong>to</strong> restart the<br />

server by executing the following command procedure :<br />

$ @SYS$STARTUP:MDMS$STARTUP RESTART<br />

You can type the server's logfile <strong>to</strong> verify that the DECnet listener <strong>for</strong> object SLS$DB<br />

has been successfully started.<br />

B–30 Migrating from SLS/MDMS V2.X <strong>to</strong> ABS/MDMS V4.X

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!