Installation Guide › Migrating CA VM:Backup from AIM to CA Mainframe VM Product Manager

Migrating CA VM:Backup from AIM to CA Mainframe VM Product Manager

The previous versions of CA VM:Backup reside in an AIM-maintained environment using VMRMAINT. The current versions reside in a VMSES-maintained environment using VMANAGER and the CA Mainframe VM Product Manager. This section describes the recommended procedure for the one-time initial migration of the product from the AIM environment to the VMSES environment.

This section contains the following topics:

Prepare for Product Migration

Update the Product Virtual Machine Definition

Update the Product Initialization Files

Prepare for Product Migration

To prepare your environment for this migration, perform the product installation steps that the Installing Product Materials section describes.

Important! We recommend that you back up your existing environment before proceeding.

Before you perform this procedure, ensure that you understand the concepts and the procedures that the CA Mainframe VM Product Manager Reference Guide documents. This procedure converts the AIM installed CA VM:Backup release to use the CA Mainframe VM Product Manager for server startup processing and server administration tasks. This setup is similar to the installation that the CA Mainframe VM Product Manager performs.

Update the Product Virtual Machine Definition

The CA VM:Backup Server Virtual Machine (SVM) requires minor changes in the virtual machine configuration to operate with the CA Mainframe VM Product Manager.

Note: The changes in this section can be performed without an outage of your VMBACKUP server.

The server is first defined in the VMSERVER NAMES file, which serves as the main software manager database. To define the server, issue the following command:

VMDEFINE name ppfname component

name: Specifies the user ID of the product server machine you are upgrading. In most cases, the name is VMBACKUP.
ppfname: Specifies the CMS file name for the Product Parameter File for this specific version of the product. If you created a PPF override file, use its file name here. If you use the supplied PPF, its name is ZVMB036A.
component: Specifies the name of the component. Use the name VMBACKUP for installing on minidisks. Use the name VMBACKUPSFS for installing on SFS.

The VMDEFINE command creates the entry and then enters a NAMES panel for you to view or modify the definitions. You can tailor the characteristics of the CA VM:Backup product server machine on the VMSERVER NAMES panel.

For the definitions of all available tag values of the CA VM:Backup product, see the Product Tags in VMSERVER NAMES File section. To match your current CA VM:Backup configuration, make any necessary modifications to the NAMES file entry.

Note: For more information about the usage of the NAMES panel, see the IBM NAMES command documentation and HELP file.

To change the definitions, overtype the values and press PF6. Press PF3 to exit the panel.

Retrieve the needed directory statements and minidisk definitions for the new release of CA VM:Backup from the product materials you previously loaded from the distribution media. The VMALLOC command must be set up first as described in the Allocating User ID Entries and Disk Space section. In the simplest form, create or update a VMALLOC CONFIG file to add a device or volume record. To produce a directory entry, issue the following command:

VMALLOC SERVER name ( DIRECT

name: Specifies the user ID of the product server machine you are migrating.

Update the Product Initialization Files

The final set of changes requires an outage of the VMBACKUP server. The server startup files are modified to interface with the CA Mainframe VM Product Manager startup interface. Shut down the VMBACKUP server.

Compare the CP Directory entry file that VMALLOC created, with your existing directory entry for the CA VM:Backup server. To match the requirements for the new release of CA VM:Backup, update your current definition. The following extra changes can be required, depending on what you have defined already:

Add an alternate runtime and an alternate public disk at addresses 0292 and 0293, respectively. These disks are populated when you deploy your new release.
Increase the size of existing disks following the size requirements from the DIRECT file that VMALLOC created.
Remove the LINK to the VMRMAINT 192 as 1FF.
Add a LINK to the VMANAGER 1FF disk as 1FF.
Add a LINK to the VMANAGER 195 disk as 1FE.

From the VMANAGER user ID, issue the VMDEPLOY command to upgrade the server startup procedure and deploy the new release product code. Execute the command as follows:

VMDEPLOY name INIT ALTERNATE

name: Specifies the user ID of the product server machine you are migrating.

VMDEPLOY verifies all minidisks and then makes necessary changes. Each disk is checked for correct size and block size. Minidisks that have errors are flagged with a message. Fix any problems reported with the minidisks and then rerun the preceding VMDEPLOY command. If all minidisks are correct, then VMDEPLOY loads the code.

Because the new CA VM:Backup code is deployed to the ALTERNATE series of minidisks, your current release remains intact. VMDEPLOY also creates a backup copy of the original PROFILE EXEC on the VMBACKUP 191 as PROFILE OLDEXEC. VMDEPLOY creates a PROFILE EXEC that contains the following command:

EXEC PROFRUN

PROFRUN integrates the server initialization process with the CA Mainframe VM Product Manager procedures.

Use XEDIT to add authorizations for your CA Mainframe VM Product Manager user ID, VMANAGER, to the CA VM:Backup configuration file.

Note: For specific information about updating the configuration file, see the CA VM:Backup System Administration Guide.

Add the authorizations for the VMANAGER user ID, so that it has the same authorizations as the old VMRMAINT user ID.
Add this record to the VMBACKUP CONFIG file:
```
PRODUCT VMSISERV VMANAGER
```
Remove the DIRECT record from the VMBACKUP CONFIG file.

Log on to the CA VM:Backup server user ID and perform the following steps:

In response to the initial prompt asking whether you want to start the server, enter NO.
Using XEDIT, add any desired PROFILE statements from your PROFILE OLDEXEC file to the PROFILE EXEC, but leave the PROFRUN call as the last line.
Check for any product materials from your old release of CA VM:Backup on the A-Disk of the server. Issue the command:
```
VMNDFCAD
```
Any duplicate file on the A-Disk must replace the corresponding file on the D-Disk. These duplicate files were probably created when fixes were applied to the release of CA VM:Backup installed by AIM. Copy these duplicate files to the D-DISK using the COPYFILE command with the OLDDATE and REPLACE options. Then erase the copy of the duplicated file from the A-Disk.

Your CA VM:Backup server is now setup to run under control of the CA Mainframe VM Product Manager. The ENVIRONMENT tag definition in the NAME file entry can be set to PRIMARY. Then the next time you start it, the server executes the older release of CA VM:Backup that you originally installed using AIM.

When you are ready to test the new CA VM:Backup release, set the ENVIRONMENT tag definition to ALTERNATE and restart the server virtual machine. When you decide to complete the upgrade to the new CA VM:Backup release, move the new release materials to the PRIMARY disk space. Overwrite the older release product materials. To copy product materials to the primary runtime disk space, Use the following format of the VMDEPLOY command:

VMDEPLOY name PRIMARY

name: Specifies the user ID of the product server machine being deployed.
PRIMARY: Copies product files to the product PRIMARY disk space. This value results in overwriting the Product Materials of the older release with the materials of the newer release.