5.2 Upgrading the Sentinel Log Manager Server

  1. Make a backup of your configuration, then create an ESM export.

    For more information on backing up data, see Backing Up and Restoring Data.

  2. Download the latest patch from the Novell download site.

  3. (Conditional) If you want to upgrade to Sentinel Log Manager Hotfix 1, download the patch from the Novell Patch Finder site.

  4. Log in as root to the server where you want to install Sentinel Log Manager.

  5. Specify the following command to stop the Sentinel Log Manager server:

    <install_directory>/bin/server.sh stop

    For example, /opt/novell/sentinel_log_mgr/bin # ./server.sh stop.

  6. Specify the following command to extract the install files from the tar file:

    tar xfz <install_filename>

    Replace <install_filename> with the actual name of the install file.

  7. Change to the directory where the install file was extracted.

  8. Specify the following command to run the install-slm script to upgrade Sentinel Log Manager:

  9. To proceed with a language of your choice, select the number next to the language.

    The end user license agreement is displayed in the selected language.

  10. Read the end user license, enter yes or y to accept the license, then continue with the installation.

  11. The installation script detects that an older version of the product already exists and prompts you to specify if you want to upgrade the product. If you press n, the installation terminates. To continue with the upgrade, press y.

    The installation starts installing all RPM packages. This installation might take a few seconds to complete.

    If you are upgrading a Sentinel Log Manager 1.1 system that was upgraded from Sentinel Log Manager 1.0, the existing Sentinel Log Manager 1.0 installation is left intact, with the following exceptions:

    • If the 1.0 data directory (For example, /opt/novell/sentinel_log_manager_1.0_x86-64/data) and the 1.1 data directory (For example, /var/opt/novell/sentinel_log_mgr/data) are in the same file system, then the <1.0>/data/eventdata and <1.0>/data/rawdata subdirectories are moved to the 1.1 location because the eventdata and rawdata directories are typically large. If the 1.0 data and 1.1 data directories are in different file systems, then the eventdata and rawdata subdirectories are copied to the 1.1 location and the 1.0 files are left intact.

    • If the existing 1.0 data directory, such as /opt/novell/sentinel_log_mgr_1.0_x86-64, is on a separately mounted file system and there is insufficient space on the file system containing the 1.1 data directory (/var/opt/novell/sentinel_log_mgr/data), then you can allow the installer to remount the file system from the 1.0 location to the 1.1 location. Any entry in /etc/fstab is also updated. If you decide not to allow the installer to remount the existing file system, the upgrade exits. You can then create sufficient space on the file system for the 1.1 data directory.

    After the Sentinel Log Manager installation is successful and the server is functional, specify the following command to manually remove the Sentinel Log Manager 1.0 directory:

    rm -rf /opt/novell/slm_1.0_install_directory

    For example:

    rm -rf /opt/novell/sentinel_log_mgr_x86-64

    Removing the installation directory permanently deletes the Sentinel Log Manager 1.0 installation.

  12. Specify the following command to start the Sentinel Log Manager server:

    <install_directory>/bin/server.sh start
  13. Make sure that all the Collector Managers are upgraded to a version compatible with the upgraded Sentinel Log Manager server.

    For more information on upgrading Collector Managers, see Section 5.3, Upgrading the Collector Manager.

NOTE:When you start the system for the first time after the upgrade, it might take approximately five minutes for the system to initialize before you can start using it. This delay occurs only when you start the system for the first time after the installation or an upgrade.