Sun and OracleChannel SunHow to BuyLog In繁體中文

Sun N1 Service Provisioning System 6.0 Installation Guide
只搜尋這本書
搜尋說明
包含在
尋找其他文件
熱門支援資源
 以 PDF 格式下載這本書 (1340 KB)

Chapter 11 Upgrading to the Sun N1 Service Provisioning System 6.0

This chapter contains instructions for upgrading from the 5.2 or 5.2 Update 2 version of product to the Sun N1 Service Provisioning System 6.0.

Note –

If you have a version of the software that was released prior to version 5.2, you must upgrade to version 5.2 before you upgrade to the Sun N1 Service Provisioning System 6.0.

Upgrading Overview

The upgrade procedure that you complete depends on whether the N1 Service Provisioning System 5.2 or 5.2 Update 2 release is running on an operating system version that is supported for the Sun N1 Service Provisioning System 6.0. Occasionally, new versions of the Sun N1 Service Provisioning System no longer contain support for operating systems that were previously supported.

Upgrading Requirements

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

  • Operating System – The operating system on which you run the 6.0 application must be the same type of operating system on which you were running the 5.2 or 5.2 Update 2 application. For example, you can migrate a Master Server running on Red Hat Linux Advanced Server 3.0 to a Master Server running on Red Hat Linux Advanced Server 4.0. You cannot migrate a Master Server running on Red Hat Linux Advanced Server 3.0 to a Master Server running on any version of the Solaris OS.

  • Hardware Architecture – The hardware architecture of the server on which you run the 6.0 application must be the same as the architecture on which you were running the 5.2 or 5.2 Update 2 application. For example, you can upgrade a Remote Agent from a SPARC based server running on the Solaris OS to another SPARC based server running on the Solaris OS. You cannot upgrade a Remote Agent from a SPARC based server running on the Solaris OS to an x86 based server running on the Solaris OS.

  • User Ownership of Application – The 6.0 application must be owned by the same user that owns the 5.2 or 5.2 Update 2 application. For example, if you installed the 5.2 Update 2 Master Server and assigned ownership to user foo, then the 6.0 Master Server must have user foo assigned as its owner.

Upgrading – Process Overview

The following process overview describes the tasks necessary to properly upgrade from the Sun N1 Service Provisioning System 5.2 or 5.2 Update 2 release to the Sun N1 Service Provisioning System 6.0.

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

    See Chapter 2, System Requirements for the Sun N1 Service Provisioning System 6.0.

  2. Complete the instructions to upgrade the Master Server.

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

    See, Upgrading Remote Agents and Local Distributors

  4. CLI Clients do not need to be upgraded. Simply install the 6.0 version of the CLI Client and uninstall the 5.2 or 5.2 Update 2 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.

程序How to Migrate Master Server Data

Migrating data to the 6.0 version of the Master Server deletes any data in the 6.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 Sun N1 Service Provisioning System 6.0. For a list of supported operating systems, see Operating System Requirements.

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

  1. Log into the machine as the user who installed the 5.2 or 5.2 Update 2 version of the Master Server.

  2. Install the 6.0 version of the Master Server on the same server where the 5.2 or 5.2 Update 2 version of the Master Server is installed.

    • If you are running a Linux or UNIX system, follow the instructions in How to Install the Sun N1 Service Provisioning System 6.0 on Linux and UNIX Systems to install the Sun N1 Service Provisioning System 6.0 Master Server.

    • If you are running Windows, complete the following steps.

      1. Stop the 5.2 or 5.2 Update 2 Master Server by using the Service application in the Windows Administrative Tools to stop the IPC Daemon service.

      2. Set the 5.2 or 5.2 Update 2 Master Services to start manually, specifically the IPC Daemon and Server.

      3. Install the 6.0 version of the Master Server by following the instructions in How to Install the Sun N1 Service Provisioning System 6.0 Master Server on Windows.

        Install the 6.0 version of the Master Server with ownership by the same user and group that owns the 5.2 or 5.2 Update 2 version of the Master Server.

  3. For Linux and UNIX 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 Linux and UNIX 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 Linux and UNIX servers, type:


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

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

    • On Windows, type:


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

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

  6. Start the migration script.

    • On Linux and UNIX servers, type:


      % ./migrateMS_5.2-6.0.sh

      The migration script has the following command line options:

      -a archive_file or -archive archive_file

      Specify archive_file to which Master Server is archived

      -bg

      Run migration in the background

      Note –

      If you use the -bg option, you need to review the MS-Migration-number.log file to make sure that the migration completed successfully before starting the Master Server.


      Migration started : date_and_time
...
Master server migration completed successfully: date_and_time

Stopping 5.2 Database
stop Database in /opt/SUNWn1sps/N1_Service_Provisioning_System_5.2/server succeeded
Issuing sync for flushing buffer data to disk.

A log of migration can be found in 
/opt/SUNWn1sps/N1_Service_Provisioning_System_5.2/server/bin/migration/MS-Migration-number.log

A log of output of database commands can be found in 
/opt/SUNWn1sps/N1_Service_Provisioning_System_5.2/server/bin/migration/MS-Migration-DB-CMD-number.log
      -d logfile

      Write database migration log output to logfile instead of the default log file

      -dbfsyncon

      The migration script now turns the fsync() system call off while restoring the database for performance improvement. This option can be used to keep the fsync() system call on.

      -dbtextdump

      The migration script now uses a new method to migrate the database. The new method uses binary dumps instead of textual dumps for a significant performance improvement. The -dbtextdump option is provided if you want to revert back to the previous method.

      -l logfile

      Write migration log output to logfile instead of the default log file

      -m archive_file or -migrate archive_file

      Specify archive_file from which to migrate Master Server

      -n new_ms_path

      Specify the path of the new Master Server installation.

      -o old_ms_path

      Specify the path of the old Master Server installation.

      -sj

      Skip Java migration

      -y

      Default to yes

    • On Windows, type:


      C:\N1SPS6.0-home\6.0\server\bin\migrate\>.\migrateMS_5.2-6.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 Sun N1 Service Provisioning System 6.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 Sun N1 Service Provisioning System 5.2 System Administration Guide.

    You cannot restore data from the 5.2 or 5.2 Update 2 Master Server to the 6.0 Master Server. Back up the data on the 6.0 Master Server so that you have a complete and accurate backup of the data to use if necessary.

  11. (Optional) Uninstall the 5.2 or 5.2 Update 2 version of the Master Server.

    You can uninstall the 5.2 or 5.2 Update 2 version of the Master Server if you do not want to use it by following the instructions in Chapter 12, Uninstalling the Sun N1 Service Provisioning System 6.0.

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 11–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 5.2 Update 2 config.properties file is migrated to the 6.0 config.properties file. During the migration, the value of each property in the 5.2 Update 2 file is compared to the value of the property in the 6.0 config.properties file. If the value is the same, the property is ignored. If the value is different, then the 5.2 Update 2 value is copied to the 6.0 config.properties file. If a property exists in the 5.2 Update 2 file and is absent in the 6.0 file, then the 5.2 Update 2 value is added to the 6.0 file. Values for the following properties are not migrated to the 6.0 config.properties file:

  • webserver.TomcatHome

  • rsrc.localrepo

  • db.port

  • db.password

  • db.hostname

  • db.instancename

  • db.username

  • db.type

  • db.maxconnections

  • hostdb.ms.ipaddress

  • hostdb.ms.port

  • note.mailsubject

  • net.server.nconn

  • net.server.type.1

  • net.server.ip.1

  • net.server.port.1

  • net.server.parms.1

  • note.url

  • pe.defaultUserToRunAs

  • hostdb.ms.connectiontype

  • pe.maxSimulPlans

If you have changed the values for any of these properties in the 5.2 Update 2 properties file, you need to manually change the value in the 6.0 config.properties file.

Upgrading Remote Agents and Local Distributors

The Sun N1 Service Provisioning System 6.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.

For information on upgrading by using a CLI command, see Overview of the node Commands in Sun N1 Service Provisioning System 5.2 Command-Line Interface Reference Manual.

程序How to Upgrade Remote Agents and Local Distributors

Before You Begin

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

  1. Log in to the browser interface of the Sun N1 Service Provisioning System 6.0 Master Server.

  2. Click Hosts.

  3. Click masterserver.

  4. Click the Upgrade Entire 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.

  5. Click the Close button.

    The upgrade is complete.

  6. 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 Sun N1 Service Provisioning System 5.2 System Administration Guide .