Upgrading IBM Storage Protect 8.1.27 to IBM Storage Protect 8.2 in a clustered environment for Windows

IBM Storage Protect maintenance updates, which are also referred to as fix packs, bring your server up to the current maintenance level.

Before you begin

To upgrade to IBM Storage Protect 8.2, install the server at the level on which you want to run it. You do not have to start the server installation at the base release level. For example, if you currently have V8.1.27 installed, you can go directly to V8.2.
Note:

Before you upgrade to IBM Storage Protect Server version 8.2, upgrade your deployment to IBM Storage Protect 8.1.27.

Procedure

  1. Complete steps 2 - 6 for each server instance.
  2. Back up the database by using the BACKUP DB command.
    The preferred method is to use a snapshot backup, which provides a full database backup without interrupting scheduled backups.
    For example, you can run the following command to create a snapshot backup:
    backup db type=dbsnapshot devclass=tapeclass
  3. Back up the device configuration information to another directory by issuing the following command:
    backup devconfig filenames=file_name
    Where file_name specifies the name of the file in which to store device configuration information.
  4. Back up the volume history file to another directory by issuing the following command:
    backup volhistory filenames=file_name
    Where file_name specifies the name of the file in which to store the volume history information.
  5. Save a copy of the server options file, typically named dsmserv.opt, which is in the server instance directory.
  6. Ensure that the resource group is on the primary node, and that all nodes in the cluster are running. Take the following actions on the primary node:
    1. Take the server resource offline and remove it by completing the following steps:
      1. In the Failover Cluster Manager window, select the cluster. Click Roles and select the cluster role from the Name column. At the end of the Roles window, click the Resources tab. The server resource is displayed in the Other Resources section.
      2. In the Other Resources section, right-click on each entry and view the properties. Review the Name and Type properties to determine which resource is the IBM Storage Protect server resource and which resource is the Db2 resource.
        For example, the IBM Storage Protect server resource might have the following properties:
        Name: IBM Storage Protect SERVER1 Group Server
        Type: TSM Server
        The Db2 resource might have the following properties:
        Name: Server1
        Type: DB2 Server
        Warning: Do not remove the Db2 resource. If you unintentionally remove the Db2 resource during this step, you will be unable to recluster after you upgrade the server.
      3. Select the IBM Storage Protect server resource, and right-click Take Offline.
      4. To remove the IBM Storage Protect server resource, select it, and right-click Remove.
    2. In the Failover Cluster Manager window, remove the network name and IP address by completing the following steps:
      1. In the Server Name section, expand the network name to view the IP address. Note the network name and IP address. Right-click Take Offline.
        Note: This action also takes the Db2 server resource offline.
      2. Select the network name and the IP address, and right-click Remove. In the confirmation message, confirm that you want to remove the client access point.
    3. Using the command-line, remove Db2 clustering for each IBM Storage Protect instance in the cluster by issuing the following command for each instance:
      db2mscs -u:instancename
      For example, to remove Db2 clustering from the SERVER1 instance, issue the following command:
      db2mscs -u:server1
      Tip: You might see an error message about a missing cluster resource. Ignore this message.
      Note: This action will remove the Db2 resource from the cluster and will delete the DB2 -DB2TSM1 – SERVERX service from the secondary node.
    4. On the primary node, in the Failover Cluster Manager window, review the resource group Summary section. Verify that only the shared disks and any tape resources remain in the resource group.
  7. Stop the cluster service on all nodes in the cluster. One way to stop it is by using the Services Application. Right-click Cluster Service and select Stop.
  8. Beginning with the primary node, install the IBM Storage Protect V8.1 server on all nodes in the cluster. For instructions, see Installing the server components. To install the server by using the installation wizard, click the Update icon on the IBM Installation Manager window. Do not click the Install or Modify icons.
    Note:

    When the console prompts you to complete prerequisite steps during the installation or upgrade of IBM Storage Protect, you can ignore the prerequisite steps and enter Y when prompted with Do you want to proceed with the upgrade? (Yes/No): to continue with the upgrade.

  9. Restart the cluster service on all nodes in the cluster. One way to start it is by using the Services Application. Right-click Cluster Service and select Start. Verify that all cluster resources are on the primary node.
  10. With cluster resources on the primary node, start the configuration wizard by clicking Start > Apps > IBM Storage Protect > Configuration Wizard. Complete the following steps in the configuration wizard:
    1. In the Instance User ID panel, enter the following:
      • The Instance name that you want to cluster.
      • The User ID that is associated with the cluster. Domain accounts use the following format: domain\account_name
      • The account password.
    2. When prompted, click Yes to confirm that you want to recluster.
    3. Continue all steps in the wizard until you see a message confirming that the configuration was successful.
      Note: In the Cluster Manager, the status for the Db2 and IBM Storage Protect Group Server resources might be in a failed state until the server finishes retrying startup.
    4. If your environment has multiple server instances, complete step 9 for each server instance.
  11. Optional: If necessary, register licenses for the IBM Storage Protect server components that are installed on your system by issuing the REGISTER LICENSE command:
    register license file=installation_directory\server\component_name.lic