5.1.2 General procedure for upgrading SLM

(1) Upgrading SLM - Manager and SLM - UR version 09-50

The figure below shows the general procedure for upgrading SLM - Manager and SLM - UR version 09-50.

Figure 5‒2: General procedure for upgrading SLM that has already been deployed (upgrading from 09-50)

When you back up data from the old version of SLM, see 8.1.1 Backing up the definition files and 8.1.2 Backing up the database.

When you restore data from the old version of SLM, see 8.1.4 Restoring the definition files and 8.1.5 Restoring the database.

When you upgrade a version of SLM that has already been deployed, you must set up SLM - Manager twice, as described in the procedure. The first setup prepares for restore processing, and the second setup migrates the database. You perform the second setup using the same command line arguments and options file contents as were used for the first setup.

After you have finished upgrading SLM, verify that the displays in the following windows are the same as they were before upgrading:

• Home window

• Troubleshoot window

• Report window

• Settings window

If the displays in these windows differ from before upgrading, you must apply the following procedure to redo the installation, and then perform setup:

1. Uninstall SLM

2. Install the old version of SLM.

3. Restore the backup data obtained before upgrading.

4. Re-install the new version of SLM.

To Page Top

(2) Upgrading SLM - Manager version 09-51 or later

When SLM - Manager 09-51 or later is upgraded, the upgrade procedure differs depending on whether the capacity of the database that will be used after upgrading will be greater than the capacity before upgrading. For this reason, before you start the procedure, estimate the database capacity that will be needed after upgrading. For details, see the description of how to estimate the size of the database area in 9.12 jslmmgrsetup (sets up SLM - Manager) in 9. Commands.

Compare the estimated value and the value shown in the table below to determine whether the capacity of the database that will be used after the upgrade will be greater than the capacity of the database before upgrading.

Table 5‒1: Database capacity before upgrading

No.	SLM - Manager version before upgrading	Database capacity before upgrading
1	09-51	39,000 MB
2		5,000 MB#
3	10-00 or later	Value of the hdb_area_size definition item in the jslmmgrsetup command's options file that was specified when SLM - Manager was newly set up.

#: This is the value used at the time of setup of SLM - Manager 09-51 when the number of monitored services was about 10 and pdi_small_s.ini was set to the default value pdi_s.ini.

If the capacity of the database that will be used after upgrading will not exceed the database capacity before upgrading, you must re-create the database area. Use the general procedure shown in the following figure for upgrading SLM - Manager.

Figure 5‒3: General procedure for upgrading SLM - Manager that has already been deployed (when upgrading from 09-51 or later and the database capacity after upgrading will not exceed the database capacity before upgrading)

If the capacity of the database that will be used after upgrading will exceed the database capacity before upgrading, you must re-create the database area. Use the general procedure shown in the following figure for upgrading SLM - Manager.

Figure 5‒4: General procedure for upgrading SLM - Manager that has already been deployed (when upgrading from 09-51 or later and the database capacity after upgrading will exceed the database capacity before upgrading)

To Page Top

(3) Upgrading SLM - UR version 09-51 or later

The following figure shows the general procedure for upgrading SLM - UR 09-51 or later.

Figure 5‒5: General procedure for upgrading SLM - UR that has already been deployed (upgrading from 09-51 or later)

To Page Top