Top
ETERNUS SF Express V16.9 / Storage Cruiser V16.9 / AdvancedCopy Manager V16.9 Migration Guide
FUJITSU Storage

7.2.1 Upgrading on Non-clustered Systems

7.2.1.1 Preparing for Upgrade

Point

It is recommended that you back up the system before starting the upgrade.
By preparing a backup, in cases when an error occurs during the upgrade, it is possible to return the system to its state prior to the upgrade, simply by recovering (restoring) the system from the backup.

  1. Login to the server on which to perform the tasks. Perform operations after logging in with root (superuser).

  2. Ensure that there is enough available disk space (650 MB in a Solaris environment, 200 MB in a Linux environment) on the server where the upgrade is performed.

    In cases when upgrade installation is executed in a state where the capacity required for the upgrade is not available, the following message is displayed and the installation terminates in an error. Re-execute the upgrade after securing the capacity required for the installation.

    Output Message (in cases when the directory of the destination of the installation is "/opt"):

    ERROR:Disk /opt has an insufficient free space. Please execute it again after increasing the disk area.
  3. Execute the following command to stop the daemon of ETERNUS SF Manager.

    # /opt/FJSVesfcm/bin/stopesf.sh

7.2.1.2 Performing Upgrade

Refer to "C.4 Procedures for Upgrade Installation of Manager Feature of Express / Storage Cruiser / AdvancedCopy Manager Version 16.x (for Solaris, Linux)" and perform the Upgrade Installation.

Point

If the Upgrade Installation has ended in an error, after removing the cause of the failure of the Upgrade Installation, re-execute the installation from the execution of the installation shell.

7.2.1.3 Tasks to Be Performed After Upgrade

The tasks below need to be performed.

  1. In the version level of this ETERNUS SF Manager, Symfoware is not used.
    To upgrade from Version 16.1 or later, the procedures listed below are not needed.
    To upgrade from Version 16.0 or earlier, follow the procedures listed below to uninstall the Symfoware Server.

    1. Confirm that other products are not utilizing the Symfoware. If Symfoware is in use by another product, refrain from uninstalling Symfoware.

    2. Start the uninstaller of Symfoware to delete the Symfoware package.

      # /opt/symfoware/setup/symfo_remove
    3. Confirmation message to uninstall Symfoware is displayed.
      To perform the uninstallation, enter "y". To cancel the process, enter "q".
      When "y" is entered, a message allowing to select the function to uninstall is shown. Input "all" or "number to delete" to select the function to uninstall.
      A message to re-confirm uninstallation appears. Enter "y" to perform the uninstallation and "q" when it is not required.

      Example of Uninstallation with the Specification "all"
      Start checking the installation environment.
      Check of installation environment is ended.
      
      WARNING: There is a possibility that another product uses "Symfoware Server Enterprise Edition".
      
      Continue the uninstallation?
      y: Continue the uninstallation
      q: End directly without uninstallation
      [y,q]: y
      
      Uninstallation of "Symfoware Server Enterprise Edition" begins.
      
      Please select the functions to be uninstalled.
      1: Base function (Server function, Client function)
      Separate multiple selections with ",". (Example: 1, 2)
      [all:All functions,1,q]: all
      
      Selected functions
      - Base function (Server function, Client function)
      
      Start the uninstallation of the above functions?
      y: Uninstallation begins
      n: Select the functions again
      q: End directly without uninstallation
      [y,n,q]: y
      
      Uninstallation begins.
    4. The following message is displayed after the Symfoware uninstallation is completed normally.

      Uninstallation of "Symfoware Server Enterprise Edition" is ended normally.
  2. Perform the kernel parameter tuning.

    See

    Refer to "Before Installation" in "Installation of ETERNUS SF Manager" in the Installation and Setup Guide for this version for information on tuning.

  3. As required, start the daemon of ETERNUS SF Manager.

    If the operating system is not restarted after having performed kernel parameter tuning in step 2, execute the following command to start the daemon of ETERNUS SF Manager.

    # /opt/FJSVesfcm/bin/startesf.sh

Subsequently, go to "7.2.3 Resuming Operation".