HP Archive Backup System for OpenVMS Guide to Operations
Share Embed Flag
Download ePaper

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

h71000.www7.hp.com
from h71000.www7.hp.com More from this publisher
06.11.2014 Views

Migrating from SLS/MDMS V2.X to ABS/MDMS V4.X B.2 SLS/MDMS V2.x to ABS/MDMS V4.x Migration B.2.2 SLS and ABS/MDMS Comparisons B.2.2.1 The information provided in the following sections will help you map SLS/MDMS attributes to the equivalent ABS/MDMS attributes. The mapping of attributes will also provide clarity on how the data is populated in ABS/MDMS. Compared to SLS, ABS/MDMS contains mostly executable code with 60% being DCL command procedures. The result of this difference is that ABS/MDMS cannot be easily customized to your needs. Many of the SLS customizations may already be there in ABS/MDMS. The modifications incorporated in SLS will have to be considered and a strategy to implement this functionality must be taken up in ABS/MDMS. In some cases, a new process might have to be developed on how the backups operations are managed in ABS/MDMS. Comparing SLS SBK Symbols and ABS Equivalent Backup Attributes Table B–1 (SBK Symbols in ABS Terminology) lists the symbols in an SLS SBK file and the equivalent ABS DCL attributes. B–4 Migrating from SLS/MDMS V2.X to ABS/MDMS V4.X

Table B–1 SBK Symbols in ABS Terminology Migrating from SLS/MDMS V2.X to ABS/MDMS V4.X B.2 SLS/MDMS V2.x to ABS/MDMS V4.x Migration SBK Symbol DAYS_n ABS Equivalent DCL Attribute Save Request /SCHEDULE and /EXPLICIT_INTERVAL Meaning Defines how often the backup operations are performed. If INTER- VAL=EXPLICIT is used, you must set the EXPLICIT qualifier. TIME_n Save Request /START_TIME Defines when the backup operation starts NODE_n BACKUP_TYPE Save Request /SOURCE_NODE Save Request /OBJECT_TYPE Defines the node in your network where the data resides. Defaulted to the node where the save request is created. For UNIX and NT save requests, EXECUTION_NODE means the node specified for the storage policy that is used for the UNIX or NT save request. Defines the type of data to be backed up or restored. PRE_PROCESS_FIRST Environment /PROLOGUE Defines the command to be executed when the backup job starts PRE_PROCESS_EACH Save Request /PROLOGUE Defines the command to be executed prior to every backup operation within a job POST_PROCESS_EACH Save Request /EPILOGUE Defines the command to be executed when each operation within a job completes POST_PROCESS_LAST Environment /EPILOGUE Defines a command to be executed when the backup job completes NEXT_JOB SUMMARY_FILE PRIVS FILES_n Use dependencies in current scheduler interface option if available. /AFTER_SCHEDULE in the Save’s Schedule object. ABS REPORT SAVE/FULL or you can search the ABS Catalogs for the job details. Environment /PROFILE=(PRIVS) Save request Include Specifi cation Defines the job that must be executed after the current job completes Gives overview information about a save operation in a job. Defines the set of privileges to be used when executing the operation Defines the set of files or other data objects that need to be backed up or restored. You can create a comma separated list of disk or file names. To add or remove disk or file names on an existing save request (or restore request), use the /ADD or /REMOVE qualifiers. Migrating from SLS/MDMS V2.X to ABS/MDMS V4.X B–5

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

B.2.2 SLS and ABS/MDMS Comparisons<br />

B.2.2.1<br />

The in<strong>for</strong>mation provided in the following sections will help you map SLS/MDMS attributes <strong>to</strong><br />

the equivalent ABS/MDMS attributes. The mapping of attributes will also provide clarity on<br />

how the data is populated in ABS/MDMS.<br />

Compared <strong>to</strong> SLS, ABS/MDMS contains mostly executable code with 60% being DCL command<br />

procedures. The result of this difference is that ABS/MDMS cannot be easily cus<strong>to</strong>mized<br />

<strong>to</strong> your needs. Many of the SLS cus<strong>to</strong>mizations may already be there in ABS/MDMS. The modifications<br />

incorporated in SLS will have <strong>to</strong> be considered and a strategy <strong>to</strong> implement this functionality<br />

must be taken up in ABS/MDMS. In some cases, a new process might have <strong>to</strong> be<br />

developed on how the backups operations are managed in ABS/MDMS.<br />

Comparing SLS SBK Symbols and ABS Equivalent <strong>Backup</strong> Attributes<br />

Table B–1 (SBK Symbols in ABS Terminology) lists the symbols in an SLS SBK file and the<br />

equivalent ABS DCL attributes.<br />

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

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

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

Saved successfully!

Ooh no, something went wrong!