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 The conversion pre-requisistes are explained in detail. The SBK symbols and the corresponding ABS object attributes are also listed in Table B–1, “SBK Symbols in ABS Terminology” for your reference. B.2.4.3.1 Pre-requsites for the Conversion – The following sub-sections provide pointers to tasks that need to be accomplished before proceeding with the conversion of SLS SBK files to ABS Policy objects. For a smooth conversion, ensure that you are aware of your site requirements and backup management policies. Converting MDMS V2.x Symbols and Databases to MDMS V4.x Database Objects – The first step in migrating from SLS to ABS environment is to convert the SLS/MDMS V2.x Symbols and Databases into ABS/MDMS V4.x Database objects. For more information, see Section B.2.4.1, “Converting SLS/MDMS V2.x Symbols and Database Files to ABS/MDMS V4.x”. Note that this version of ABS (T4.4) and all future versions require the accompanying version of MDMS that is included in the installation kit. Determining Use of SLS – The next step in migrating from SLS to ABS is to identify the need for SLS and to know that ABS is at par with SLS. The following are the three major functionalities in SLS: • Taking System Backups • Taking Standby Archiving • Taking User Backups ABS provides the same functionality as SLS SBK files and User Backups. However, ABS cannot provide the same function as SLS Standby Archiving. If you use SLS SBK files (as many sites do), then converting to ABS is relatively simple. If you use SLS User Backups, converting to ABS is slightly more involved, but is still straightforward. If you use SLS Standby Archiving, ABS does not provide the equivalent functionality. Determining Valid SBK Files – At many sites, only few of the SBK files located in the SLS$SYSBAK are actually used for regular backups. The other SBK files available are a result of experimentation or are outdated. In order to simplify the conversion of SLS SBK files to ABS Policy objects, you need to identify the SBK files that are active or in use. Some pointers to select valid SBK files: • SBK files that are regularly scheduled for taking data backups by SLS The DAYS_1 symbol is defined for scheduling automatic backups. • SBK files that are manually executed by yourself or the Operator If the DAYS_1 symbol is left blank or is commented out, then those SBK files will be manually executed by yourself or the Operator. It is important to determine whether SBK files that are not scheduled for taking automatic backups are at least manually executed. If not, they are the prime candidates to be considered as outdated or unused. Once you have identified the obsolete or unused SBK files, you can remove them from SLS$SYSBAK (take backup of these files before removing them in case they are required in thefuture). B–32 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 Installing SLS SBK Files to ABS Policy Objects Conversion Utility – After you have cleaned the SLS$SYSBAK directory to contain only those SBK files you actually want to convert, install the appropriate conversion utility provided as part of the ABS kit. Two separate conversion utilities are provided for OpenVMS VAX and Alpha architectures: • SLSTOVABS, example: SLSTOVABSA043 • SLSTOAABS, example: SLSTOAABSA043 You need to determine the OpenVMS architecture being used on the node where you want to execute the conversion and then install the appropriate utility. The conversion is managed by SLS_CONVERT.COM that is provided when the conversion utility is installed. • To install the conversion utility on OpenVMS VAX, issue the following command: $ @SYS$UPDATE:VMSINSTAL SLSTOVABS ABS$SYSTEM: Example: $ @SYS$UPDATE:VMSINSTAL SLSTOVABSA043 ABS$SYSTEM: • To install the conversion utility on OpenVMS Alpha, issue the following command: $ @SYS$UPDATE:VMSINSTAL SLSTOAABS ABS$SYSTEM: Example: $ @SYS$UPDATE:VMSINSTAL SLSTOAABSA043 ABS$SYSTEM: It is also an interactive installation procedure and is on similar lines with ABS installation, where you are prompted to provide appropriate details for the installation to complete. The conversion utility is installed into ABS$SYSTEM:SLS_CONVERT.COM. A sub-directory called SLS_CONVERSION is created under ABS$ROOT. In addition, the logical name ABS$SLS_CONVERSION is defined to point to the work directory for the conversion effort. B.2.4.3.2 Executing SLS SBK Files to ABS Policy Objects Conversion – Once you have installed the conversion utility, issue the following command to convert the selected SBK Symbols to ABS Policy objects: $ @ABS$SYSTEM:SLS_CONVERT ! Conversion of a single SBK file $ @ABS$SYSTEM:SLS_CONVERT * ! Conversion of all SBK files Note SLS/MDMS V2.x must be restarted before executing the conversion utility. Use the following command to restart SLS/MDMS V2.x: @SYS$STARTUP:SLS$STARTUP The conversion utility when executed requires a SBK file name or a “*” as the input parameter. The asterisk symbol is used when you want to convert all the SBK files to ABS DCL Command procedures. If you want to convert a single SBK file, you must specify the SBK file name without the “_SBK.COM” or “SLS$SYSBAK” on the command line. See Section B.2.4.3.3, “Command Syntax” for more information. The conversion utility creates a DCL command procedure for every SBK file. Each command procedure will be named the same as the SBK file but substituting “SBK” with “ABS”. For example, if the SBK file “Example1_SBK.COM” is converted, the output command procedure will be “ABS$SLS_CONVERSION:Example1_ABS.COM”. Each command procedure will have the ABS Policy objects defined from the respective symbols in the SBK file. Modifications are not made to your ABS Policy Configuration directly. This allows you to experiment with the conversion utility safely, without affecting either the execution of your SLS SBK files or starting the ABS Save requests inadvertently. Migrating from SLS/MDMS V2.X to ABS/MDMS V4.X B–33

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

Installing SLS SBK Files <strong>to</strong> ABS Policy Objects Conversion Utility –<br />

After you have cleaned the SLS$SYSBAK direc<strong>to</strong>ry <strong>to</strong> contain only those SBK files you actually<br />

want <strong>to</strong> convert, install the appropriate conversion utility provided as part of the ABS kit.<br />

Two separate conversion utilities are provided <strong>for</strong> <strong>OpenVMS</strong> VAX and Alpha architectures:<br />

• SLSTOVABS, example: SLSTOVABSA043<br />

• SLSTOAABS, example: SLSTOAABSA043<br />

You need <strong>to</strong> determine the <strong>OpenVMS</strong> architecture being used on the node where you want <strong>to</strong><br />

execute the conversion and then install the appropriate utility. The conversion is managed by<br />

SLS_CONVERT.COM that is provided when the conversion utility is installed.<br />

• To install the conversion utility on <strong>OpenVMS</strong> VAX, issue the following command:<br />

$ @SYS$UPDATE:VMSINSTAL SLSTOVABS ABS$SYSTEM:<br />

Example: $ @SYS$UPDATE:VMSINSTAL SLSTOVABSA043 ABS$SYSTEM:<br />

• To install the conversion utility on <strong>OpenVMS</strong> Alpha, issue the following command:<br />

$ @SYS$UPDATE:VMSINSTAL SLSTOAABS ABS$SYSTEM:<br />

Example: $ @SYS$UPDATE:VMSINSTAL SLSTOAABSA043 ABS$SYSTEM:<br />

It is also an interactive installation procedure and is on similar lines with ABS installation, where<br />

you are prompted <strong>to</strong> provide appropriate details <strong>for</strong> the installation <strong>to</strong> complete. The conversion<br />

utility is installed in<strong>to</strong> ABS$SYSTEM:SLS_CONVERT.COM. A sub-direc<strong>to</strong>ry called<br />

SLS_CONVERSION is created under ABS$ROOT. In addition, the logical name<br />

ABS$SLS_CONVERSION is defined <strong>to</strong> point <strong>to</strong> the work direc<strong>to</strong>ry <strong>for</strong> the conversion ef<strong>for</strong>t.<br />

B.2.4.3.2 Executing SLS SBK Files <strong>to</strong> ABS Policy Objects Conversion –<br />

Once you have installed the conversion utility, issue the following command <strong>to</strong> convert the<br />

selected SBK Symbols <strong>to</strong> ABS Policy objects:<br />

$ @ABS$SYSTEM:SLS_CONVERT ! Conversion of a single SBK file<br />

$ @ABS$SYSTEM:SLS_CONVERT * ! Conversion of all SBK files<br />

Note<br />

SLS/MDMS V2.x must be restarted be<strong>for</strong>e executing the conversion utility. Use the following<br />

command <strong>to</strong> restart SLS/MDMS V2.x: @SYS$STARTUP:SLS$STARTUP<br />

The conversion utility when executed requires a SBK file name or a “*” as the input parameter.<br />

The asterisk symbol is used when you want <strong>to</strong> convert all the SBK files <strong>to</strong> ABS DCL Command<br />

procedures. If you want <strong>to</strong> convert a single SBK file, you must specify the SBK file name without<br />

the “_SBK.COM” or “SLS$SYSBAK” on the command line. See Section B.2.4.3.3, “Command<br />

Syntax” <strong>for</strong> more in<strong>for</strong>mation.<br />

The conversion utility creates a DCL command procedure <strong>for</strong> every SBK file. Each command<br />

procedure will be named the same as the SBK file but substituting “SBK” with “ABS”. For<br />

example, if the SBK file “Example1_SBK.COM” is converted, the output command procedure<br />

will be “ABS$SLS_CONVERSION:Example1_ABS.COM”.<br />

Each command procedure will have the ABS Policy objects defined from the respective symbols<br />

in the SBK file. Modifications are not made <strong>to</strong> your ABS Policy Configuration directly. This<br />

allows you <strong>to</strong> experiment with the conversion utility safely, without affecting either the execution<br />

of your SLS SBK files or starting the ABS Save requests inadvertently.<br />

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

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

Saved successfully!

Ooh no, something went wrong!