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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

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

SBK Symbol ABS Equivalent Meaning<br />

DRIVE_TYPE S<strong>to</strong>rage Class /DRIVE_LIST Determines the list of tape drives <strong>to</strong><br />

be used.<br />

Note: It is recommended that<br />

MDMS media types be set up correctly<br />

rather than using this field.<br />

N_DRIVES<br />

Environment<br />

/DRIVE_COUNT<br />

Determines the number of tape<br />

drives <strong>to</strong> be used during a backup<br />

operation.<br />

PROGRESS Not supported ABS notifies the opera<strong>to</strong>r after a<br />

certain number of files are backed<br />

up.<br />

REPLY_MSG<br />

STATUS_MAIL<br />

LOG_FILE<br />

LISTING_GEN<br />

FULL<br />

Not supported. MDMS issues<br />

all OPCOM messages in a<br />

standard <strong>for</strong>mat<br />

Environment /NOTIFICA-<br />

TION<br />

Not supported. ABS generates<br />

a log file in ABS$LOG.<br />

To view a save log, you need<br />

<strong>to</strong> type ABS$log followed by<br />

the name of the save request.<br />

Environment<br />

/LISTING_OPTION. ABS<br />

generates the listing files, but<br />

they are always located in<br />

ABS$LISTINGS. They are<br />

named the same as the Save<br />

request followed by the save<br />

operation number.<br />

Environment /LIST<br />

ING_OPTION=FULL<br />

Determines the notification <strong>to</strong> be<br />

per<strong>for</strong>med when each backup operation<br />

is executed and completed.<br />

Determines the recepient who must<br />

be e-mailed when the job completes.<br />

Determines the name of the log file<br />

<strong>for</strong> the operation.<br />

Determines the name of the backup<br />

listing file <strong>to</strong> be produced from each<br />

operation.<br />

Determines if the listing file provides<br />

complete in<strong>for</strong>mation or only<br />

a brief about the backed up files .<br />

PRINT_Q Not supported. Determines the Print queue where<br />

the listing file is printed.<br />

B.2.3 Operational Differences between MDMS V2 and MDMS V3<br />

This section discusses the main operational differences between MDMS V3 (includes MDMS<br />

V3 and later versions) and its previous version MDMS V2 (includes MDMS V2 and lower versions).<br />

In some cases, there are conceptual differences in the approach but the output is the same.<br />

You are also given an insight in<strong>to</strong> the changes implemented in order <strong>to</strong> make the upgrade as<br />

smooth as possible. Also, the reasons <strong>for</strong> implementing some changes are explained. It also<br />

enables you <strong>to</strong> use the new features <strong>to</strong> optimize your configuration and usage of the products.<br />

– Any reference <strong>to</strong> MDMS V2 in this chapter points <strong>to</strong> MDMS V2 and lower versions<br />

– Any reference <strong>to</strong> MDMS V3 in this chapter points <strong>to</strong> MDMS V3 and later versions<br />

B–8 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!