test

N1 Grid Service Provisioning System 5.0 Installation Guide

Chapter 9 Upgrading to the N1 Grid Service Provisioning System 5.0

This chapter contains instructions for upgrading from the 4.1 version of product to the N1 Grid Service Provisioning System 5.0.

Note –

If you have a version of the software that was released prior to version 4.1, you must upgrade to version 4.1 before you upgrade to the N1 Grid Service Provisioning System 5.0. If you have a version of the software that was released prior to version 4.0, you must upgrade to version 4.0 before you upgrade to version 4.1.

Upgrading Overview

The upgrade procedure that you complete depends on whether the N1 Service Provisioning System 4.1 is running on an operating system version that is supported for the N1 Grid Service Provisioning System 5.0. Occasionally, new versions of the N1 Grid Service Provisioning System no longer contain support for operating systems that were previously supported.

Upgrading Requirements

When upgrading any of the N1 Grid Service Provisioning System applications, the new server on which you install the 5.0 application must meet the following requirements:

Upgrading – Process Overview

The following process overview describes the tasks necessary to properly upgrade from the N1 Grid Service Provisioning System 4.1 to the N1 Grid Service Provisioning System 5.0.

  1. Determine whether the servers that you are upgrading meet the minimum requirements to run the N1 Grid Service Provisioning System 5.0.

    See Chapter 2, System Requirements for the N1 Grid Service Provisioning System 5.0.

  2. Choose the Master Server upgrade instructions for your operating system.

  3. Complete the instructions to upgrade the Master Server.

  4. Identify any servers that are running Remote Agents and Local Distributors on operating systems that are not supported by the N1 Grid Service Provisioning System 5.0. See, Supported Operating Systems

  5. Upgrade those servers to an operating system that is supported by N1 Grid Service Provisioning System 5.0.

  6. Complete the instructions to upgrade the Remote Agents and Local Distributors.

    See, Upgrading Remote Agents and Local Distributors

  7. CLI Clients do not need to be upgraded. Simply install the 5.0 version of the CLI Client and uninstall the 4.1 version.

Upgrading the Master Server

The Master Server application is not upgraded like most software is upgraded. Rather, the new version of the Master Server is installed on the same server as the previous version of the Master Server. Then, the data is migrated from the previous version of the Master Server to the new version of the Master Server. The upgrade procedure you complete depends on whether you are running the 4.1 Master Server on an operating system version that is supported by the N1 Grid Service Provisioning System 5.0.

ProcedureHow to Migrate Master Server Data From Supported Operating Systems

Migrating data from the 4.1 version of the Master Server to the 5.0 version of the Master Server deletes any data in the 5.0 version of the Master Server. The migration script stops both versions of the Master Server until the script completes the migration. The Master Servers will be unavailable for the duration of the migration.

Before You Begin

Verify that the operating system version on the server you want to upgrade is supported by the N1 Grid Service Provisioning System 5.0. For a list of supported operating systems, see Supported Operating Systems. If the operating system version is no longer supported, follow the instructions in How to Upgrade a Master Server From an Operating System That Is No Longer Supported.

Back up your data before you migrate. See Chapter 9, Backing Up and Restoring, in N1 Grid Service Provisioning System 5.0 System Administration Guide.

Steps

  1. Log into the machine as the user who installed the 4.1 version of the Master Server.

  2. Install the 5.0 version of the Master Server on the same server where the 4.1 version of the Master Server is installed.

  3. For Solaris OS and Red Hat Linux Master Servers, verify that the database will not be optimized during the migration process.

    Check that you do not have any cron jobs scheduled that would start a database optimization while you are migrating the data.

  4. Access a command prompt.

    • On Solaris OS or Red Hat Linux servers, open a shell window and log in as the user that owns the Master Server.

    • On Windows, open a Command Prompt window.

  5. Change to the directory that contains the migration script.

    • On Solaris OS or Red Hat Linux servers, type:


      % cd /N1SPS5.0-home/server/bin/migrate

      N1SPS5.0-home is the directory where you installed the Master Server.

    • On Windows, type:


      C:\> cd C:\N1SPS5.0-home\server\bin\migrate

      C:\N1SPS5.0-home is the directory in which you installed the Master Server.

  6. Start the migration script.

    • On Solaris OS or Red Hat Linux servers, type:


      % ./migrateMS_4.1-5.0.sh

    • On Windows, type:


      C:\N1SPS5.0-home\5.0\server\bin\migrate\>.\migrateMS_4.1-5.0.cmd

  7. Follow the instructions on the screen to complete the migration.

    When the migration is complete, the following message appears.


    Master Server migration completed successfully.
    Note –

    The listener port numbers for the Postgres database, browser interface, and the Master Server are not migrated. The N1 Grid Service Provisioning System 5.0 Master Server uses the port numbers that you supplied during installation.

  8. Check the log file for any errors that might have occurred during migration.

    The migration script displays the location of the log file.

  9. Clear the cache on the browser that you use to access the Master Server browser interface.

    If you started a browser session before upgrading the Master Server, graphics and style sheets that are cached in the browser might prevent you from seeing the upgraded browser interface.

  10. Back up the data that you migrated to the new Master Server by using the instructions in Chapter 9, Backing Up and Restoring, in N1 Grid Service Provisioning System 5.0 System Administration Guide.

    You cannot restore data from the 4.1 Master Server to the 5.0 Master Server. Back up the data on the 5.0 Master Server so that you have a complete and accurate backup of the data to use if necessary.

  11. (Optional) Uninstall the 4.1 version of the Master Server.

    You can uninstall the 4.1 version of the Master Server if you do not want to use it by following the instructions in Chapter 10, Uninstalling the N1 Grid Service Provisioning System 5.0.

ProcedureHow to Upgrade a Master Server From an Operating System That Is No Longer Supported

Occasionally, new versions of the N1 Grid Service Provisioning System no longer contain support for operating systems that were previously supported. Upgrading the Master Server from a previously supported operating system to a new operating system version requires two phases. In the first phase, the data from the previous version of the Master Server is archived into a file. In the second phase, the data stored in the archive file is migrated into the new version of the Master Server.

Steps

  1. Log into the machine as the user who installed the 4.1 version of the Master Server.

  2. Verify that the database will not be optimized during the migration process.

    Check that you do not have any cron jobs scheduled that would start a database optimization while you are migrating the data.

  3. Access a command prompt.

  4. Access the migration script.

    • If you are migrating using a CD, insert the N1 Grid Service Provisioning System 5.0: IBM-AIX, Red Hat Linux CD.

    • If you are migrating using a image that you downloaded, change to the directory where you saved the downloaded image.

  5. Change to the directory on the software CD or within the downloaded image where the migration script is located.


    % cd /migrate

  6. Copy the migration script to the 4.1 Master Server.


    % cp migrateMS_4.1-5.0.sh /N1SPS4.1-home/server/bin

    N1SPS4.1-home is the directory where you installed the 4.1 Master Server.

  7. Change to the directory on 4.1 Master Server that contains the migration script that you copied.


    % cd /N1SPS4.1-home/server/bin

  8. Create a file that contains the data from the 4.1 Master Server.


    % ./migrateMS_4.1-5.0.sh -archive /path-to-archive-file/filename

    path-to-archive-file is the directory in which you want to save the archive file created by the migration script. filename is the name that you designate for the archive file.

  9. Follow the instructions on the screen to complete the creation of the file.

  10. Install the 5.0 version of the Master Server.

  11. Change to the directory that contains the migration script.


    % cd /N1SPS5.0-home/server/bin/migrate

  12. Start the migration script.


    % ./migrateMS_4.1-5.0.sh -migrate path-to-archive-file/filename

    path-to-archive-file is the path that you specified for the migration script to save the file that contains the archived data. filename is the name that you designated for the archive file.

  13. Follow the instructions on the screen to complete the migration.

    When the migration is complete, the following message appears.


    Master Server migration completed successfully.
    Note –

    The listener port numbers for the Postgres database, browser interface, and the Master Server are not migrated. The N1 Grid Service Provisioning System 5.0 Master Server uses the port numbers that you supplied during installation.

  14. Check the log file for any errors that might have occurred during migration.

    The migration script displays the location of the log file.

  15. Clear the cache on the browser that you use to access the Master Server browser interface.

    If you started a browser session before upgrading the Master Server, graphics and style sheets that are cached in the browser might prevent you from seeing the upgraded browser interface.

  16. Back up the data that you migrated to the new Master Server by using the instructions in Chapter 9, Backing Up and Restoring, in N1 Grid Service Provisioning System 5.0 System Administration Guide.

    You cannot restore data from the 4.1 Master Server to the 5.0 Master Server. Back up the data on the 5.0 Master Server so that you have a complete and accurate backup of the data to use if necessary.

Master Server Data Migration Details

This section describes details about the data that is migrated from the previous version of the Master Server to the new version of the Master Server.

Master Server Data Migration

The following table details the types of data that are migrated on the Master Server.

Table 9–1 Migration Overview

Data on the Master Server 

Is the Data Migrated? 

Mechanism for Migration 

PostgresSQL data 

Yes 

SQL scripts 

CLI Client script for changes to existing commands 

No 

 

Migration of objects serialized through CLI Client 

No 

 

Migration of changes to the config.properties file on each host

Yes 

Properties listed in the file are migrated using the details found in Migration Details for the Properties File.

Resource migration 

Yes  

Copy the resources directory. 

Logger Configuration file 

No 

 

User interface customizations 

No 

 

Migration Details for the Properties File

The 4.1 config.properties file is migrated to the 5.0 config.properties file. During the migration, the value of each property in the 4.1 file is compared to the value of the property in the 5.0 config.properties file. If the value is the same, the property is ignored. If the value is different, then the 4.1 value is copied to the 5.0 config.properties file. If a property exists in the 4.1 file and is absent in the 5.0 file, then the 4.1 value is added to the 5.0 file. Values for the following properties are not migrated to the 5.0 config.properties file:

If you have changed the values for any of these properties in the 4.1 properties file, you need to manually change the value in the 5.0 config.properties file.

Upgrading Remote Agents and Local Distributors

The N1 Grid Service Provisioning System 5.0 provides an automatic upgrade utility that allows you to upgrade Remote Agents and Local Distributors by using the browser interface to the Master Server. Before you use the automatic utility, all of the Remote Agents and Local Distributors must be running on operating system versions that are supported by the N1 Grid Service Provisioning System 5.0. If you begin an automatic upgrade and receive an error message indicating that some Remote Agents or Local Distributors were not upgraded because the operating system version is not supported, you will need to manually upgrade the Remote Agents and Local Distributors on those servers. See How to Manually Upgrade Remote Agents and Local Distributors From an Operating System That Is No Longer Supported.

ProcedureHow to Upgrade Remote Agents and Local Distributors

If you are running Remote Agents and Local Distributors on an operating system version that is not supported by the N1 Grid Service Provisioning System 5.0, you first upgrade the server to an operating system that is supported by both the 4.1 and 5.0 versions of the N1 Grid Service Provisioning System. Then, you use the browser interface to upgrade all of the Remote Agents and Local Distributors in your network. After the applications have been upgraded, you can then upgrade your servers to numerically higher versions of the operating system, if they are supported by the N1 Grid Service Provisioning System 5.0.

For example, you are running a 4.1 Remote Agent on a Red Hat Linux 7.1 server and you want to upgrade that server to Red Hat Linux 3.0 Advanced Server. First, you need to upgrade the server to Red Hat Linux Advanced Server 2.1, which is supported by both the 4.1 and 5.0 versions of the N1 Grid Service Provisioning System. Second, upgrade all of the Remote Agents by using the browser interface to the Master Server. Finally, upgrade the server to Red Hat Linux 3.0.

Before You Begin

Migrate the Master Server before upgrading Remote Agents and Local Distributors.

Steps

  1. Identify any server that is running the 4.1 Remote Agent or Local Distributor on an operating system that is not supported by the N1 Grid Service Provisioning System 5.0.

    For a list of supported operating systems, see Supported Operating Systems.

  2. On each server that is running the 4.1 Remote Agent or Local Distributor on an operating system that is not supported by the N1 Grid Service Provisioning System 5.0, upgrade the operating system to a version that is supported by both the 4.1 and 5.0 versions of the N1 Grid Service Provisioning System.

  3. Log in to the browser interface of the N1 Grid Service Provisioning System 5.0 Master Server.

  4. Click Hosts.

  5. Click masterserver.

  6. Click the Update Entire N1 SPS network... button.

    A window opens and displays a list of hosts that are being upgraded. The progress of the upgrade is also displayed. When the process completes, the window displays the following message.


    Host Update not yet complete.

  7. Click the Close button.

  8. To complete the second phase of the upgrade, click the Update Entire N1 SPS network... button again.

    A window displays a list of hosts that are being upgraded. The progress of the upgrade is also displayed. When the process completes, the status for each of the hosts displays as Updated.

  9. Click the Close button.

    The upgrade is complete.

  10. Prepare the Hosts that you upgraded.

    Before you can run a Plan on a Host that you upgraded, you must Prepare the Host. To Prepare Hosts, follow the instructions in How to Prepare a Physical Host in N1 Grid Service Provisioning System 5.0 System Administration Guide .

  11. (Optional) If you want to upgrade the operating system on your servers to a numerically higher version, you may do so.

    The version to which you upgrade the operating system must be supported by the N1 Grid Service Provisioning System 5.0.

ProcedureHow to Manually Upgrade Remote Agents and Local Distributors From an Operating System That Is No Longer Supported

If you did not upgrade servers running operating systems that are no longer supported by the N1 Grid Service Provisioning System 5.0 before you automatically upgraded the Remote Agents and Local Distributors, you need to manually upgrade those systems.

Steps

  1. On the server that is running the 4.1 Remote Agent or Local Distributor that you want to upgrade, log into the machine as the user who installed the 4.1 version of the Remote Agent or Local Distributor.

  2. Change to the directory that contains the application scripts.


    % cd /N1SPS4.1-home/app/bin/

    N1SPS4.1-home is the directory where you installed the application.

    app is agent for the Remote Agent and ld for the Local Distributor.

  3. Stop the 4.1 Remote Agent or Local Distributor.


    % ./cr_app stop

    app is agent for the Remote Agent and ld for the Local Distributor.

  4. Verify that the 4.1 Remote Agent or Local Distributor is not automatically started upon system reboot by system start up scripts.

  5. Upgrade the operating system on the server to a version that the N1 Grid Service Provisioning System 5.0 supports.

  6. Move the 4.1 Remote Agent or Local Distributor to a temporary location on the server.


    % mv /N1SPS4.1-home/app /temporary_directory

    N1SPS4.1-home is the directory where you installed the application.

    app is agent for the Remote Agent and ld for the Local Distributor.

    temporary_directory is the temporary directory in which to move the application.

  7. Install the 5.0 Remote Agent or Local Distributor in the same directory where the 4.1 application had been installed.

    For instructions, see How to Install the N1 Grid Service Provisioning System 5.0 on Solaris OS, Red Hat Linux, and IBM AIX Systems.

  8. Change to the directory that contains the scripts for the 5.0 Remote Agent or Local Distributor.


    % cd /N1SPS5.0-home/app/bin/

    N1SPS5.0-home is the directory where you installed the application.

    app is agent for the Remote Agent and ld for the Local Distributor.

  9. Migrate the data to the 5.0 Remote Agent or Local Distributor.


    % ./migrateNode_4.1-5.0.sh -n /N1SPS5.0-home/app -o /temporary_directory/N1SPS4.1-home/app

    N1SPS5.0-home is the directory where you installed the 5.0 application.

    /temporary_directory/N1SPS4.1-home is the directory to which you moved the 4.1 application.

    app is agent for the Remote Agent and ld for the Local Distributor.

    The migration script migrates the following files:

    • config.properties

    • transport.config

    • keystores

    • snapshots on the Remote Agent

  10. Start the 5.0 Remote Agent or Local Distributor.


    % ./cr_app start

    app is agent for the Remote Agent and ld for the Local Distributor.