6.2.1 Upgrading on Non-clustered Systems

With the following procedure, back up the operation environment of the previous version of the AdvancedCopy Manager's manager.
Refer to "A.7 Capacity Necessary for Backup of Previous Version" for information on the capacity required to perform a backup.

Login to the server on which to perform the tasks. Perform operations after logging in with root (superuser).
Insert the DVD "ETERNUS SF SC/ACM Mediapack for Solaris (V16.9 or higher) Manager Program (2/2)" or "ETERNUS SF SC/ACM/Express Mediapack for Linux 64bit (V16.9 or higher) Manager Program (2/2)" of this version into the DVD drive.
Mount the DVD media.
- Example for Solaris environments
```
# mount -F hsfs -o ro /dev/dsk/c0t4d0s0 dvdMountPoint
```
  The device name of the DVD drive may differ depending on the device. In this example, the device name of the DVD drive is mounted as "/dev/dsk/c0t4d0s0".
- Example for Linux environments
```
# mount -t iso9660 -r /dev/cdrom dvdMountPoint
```
  The device name of the DVD drive may differ depending on the device. In this example, the device name of the DVD drive is mounted as "/dev/cdrom".
Execute the following command to stop the daemon of ETERNUS SF Manager.
```
# /opt/FJSVesfcm/bin/stopesf.sh
```
Execute the following command to perform a backup of the previous version.
For backupDir, specify the directory in which to store the backup data with an absolute path. For tmpDir, specify a directory in which to temporarily place the files related to the performance management function of Storage Cruiser with an absolute path. When the performance management function is not being used, it is unnecessary to specify a directory for the tmpDir.
```
# dvdMountPoint/Manager_unix/vuptools/esfpreinst.sh backupDir [tmpDir]
```
When the backup fails, after confirming the output error message and removing the cause of the failure, re-execute the command.
Point
- Spaces and the characters " / ` * ? \ $ [ ] , % ! { } are not supported for directory names.
- The number of characters in a directory name must be up to 220.
- Move the files (tmpDir) related to the performance management function to under /var/opt. In the case of backup to a different location from that under /var/opt, it may take time to perform backup and restore.

6.2.1.1.2 Checking for Available Disk Space

Ensure that there is enough available disk space on the server where the upgrade is performed.
The required disk space for the upgrade is calculated as the "Required Disk Space for New Version" minus the "Required Disk Space for Previous Version".

Required Disk Space for New Version: The space required to install this version of the ETERNUS SF Manager.
Refer to "Operating Environment of ETERNUS SF Manager" in the Installation and Setup Guide for this version for information on the required disk space.

Required Disk Space for Previous Version: The space required to install the previous version of the ETERNUS SF Manager.
Refer to "Operating environment of ETERNUS SF Manager" in the Installation and Setup Guide for the previous version for information on the required disk space.

6.2.1.1.3 Uninstalling Incompatible Software

Check if any incompatible software for this version of the ETERNUS SF Manager is installed on the server where the upgrade is performed.
If incompatible software is found, refer to the relevant software manual and uninstall it before starting the upgrade.

See

Refer to "Operating Environment of ETERNUS SF Manager" in the Installation and Setup Guide for this version for information on the incompatible software.

6.2.1.1.4 Estimating Database Size

A database is necessary for this version of AdvancedCopy Manager.
The database size must be estimated before starting the upgrade.

See

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

6.2.1.1.5 Tuning Kernel Parameters

Kernel parameter tuning must be performed in order to use this version of the AdvancedCopy Manager's manager. Therefore, perform the necessary kernel parameter tuning before starting the upgrade.

See

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

6.2.1.1.6 Confirming Port Number for Communication Service

Therefore, ensure the new ports are available before starting the upgrade.

See

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

6.2.1.1.7 Preparing for Uninstallation

Refer to "A.5 Cancelling Repository Settings" to unsetup the repository database of the previous version.

6.2.1.2 Performing Upgrade

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

Information

When the Upgrade Installation terminates in an error, perform recovery by following the steps outlined below.

Install the target version.
If the installation is successfully completed, continue from "6.2.1.3 Tasks to Be Performed After Upgrade".

6.2.1.3 Tasks to Be Performed After Upgrade

6.2.1.3.1 Restoring Environment from Previous Version

With the following procedure, restore the operation environment of the previous version of the AdvancedCopy Manager's manager.
Note that if step 1 through step 3 have already been performed, perform from step 4.

Login to the server on which to perform the tasks. Perform operations after logging in with root (superuser).
Insert the DVD "ETERNUS SF SC/ACM Mediapack for Solaris (V16.9 or higher) Manager Program (2/2)" or "ETERNUS SF SC/ACM/Express Mediapack for Linux 64bit (V16.9 or higher) Manager Program (2/2)" of this version into the DVD drive.
Mount the DVD media.
- Example for Solaris environments
```
# mount -F hsfs -o ro /dev/dsk/c0t4d0s0 dvdMountPoint
```
  The device name of the DVD drive may differ depending on the device. In this example, the device name of the DVD drive is mounted as "/dev/dsk/c0t4d0s0".
- Example for Linux environments
```
# mount -t iso9660 -r /dev/cdrom dvdMountPoint
```
  The device name of the DVD drive may differ depending on the device. In this example, the device name of the DVD drive is mounted as "/dev/cdrom".
Execute the following command to restore of the previous version.
For backupDir, specify the directory in which the backup data is stored with an absolute path. For tmpDir, specify a directory in which to temporarily place the files related to the performance management function of Storage Cruiser with an absolute path. When the performance management function is not backed up, it is unnecessary to specify a directory for the tmpDir.
```
# dvdMountPoint/Manager_unix/vuptools/esfpostinst.sh backupDir [tmpDir]
```
When the restore fails, after confirming the output error message and removing the cause of the failure, re-execute the command.
Point
- Spaces and the characters " / ` * ? \ $ [ ] , % ! { } are not supported for directory names.
- The number of characters in a directory name must be up to 220.
Unmount the DVD media.
```
# umount dvdMountPoint
```
Eject the DVD media.
Execute the following command to restart the daemon of ETERNUS SF Manager.
```
# /opt/FJSVesfcm/bin/startesf.sh
```

6.2.1.3.2 Importing Configuration Information

Import the configuration information from the previous version by executing the "esfadm devconf import" command using Administrator permissions.

Check that the managed devices and servers can be accessed before executing the "esfadm devconf import" command.

/opt/FJSVesfcm/bin/esfadm devconf import -all

After executing the "esfadm devconf import" command, confirm that "Complete" is displayed in IMPORT STATUS column in the "esfadm devconf importstatus" command.

In addition, confirm that "Complete" is displayed in STATUS column of the import status of the migration target resources. When "Failed" is displayed, the import of configuration information has failed. Refer to "9.2 What to Do When Error Occurs" to take the corrective action.

Note

When executing the "esfadm devconf import" command, if a managed device or server is not accessible, the "esfadm devconf import" command should be re-executed since the device configuration information is not imported.

6.2.1.3.3 Deleting Backup Data

Once normal operation has been confirmed after the upgrade, the backup data in the backup destination directory created in step 5 of "6.2.1.1.1 Backing Up Operational Environment of Previous Version" maybe deleted.

6.2.1.3.4 Uninstalling Symfoware

In the version level of this ETERNUS SF Manager, Symfoware is not used.
Symfoware should only be installed in cases where it was used by ETERNUS SF Manager only.

The procedures to uninstall Symfoware are stated below.

Start the uninstaller of Symfoware to delete the Symfoware package.
Before deleting the package, confirm that none of the package functions used by any system other than ETERNUS SF Manager.
```
# /opt/symfoware/setup/symfo_remove
```

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.

The following message is displayed after the Symfoware uninstallation is completed normally.
```
Uninstallation of "Symfoware Server Enterprise Edition" is ended normally.
```
When FSUNiconv package is installed, delete it (only in Solaris environments).
Delete after confirming that this package function is used only by ETERNUS SF Manager.
```
# pkgrm FSUNiconv
```

Subsequently, go to "6.2.3 Resuming Operation".