The section describes the upgrade of clustered systems.
Note
If Cluster Unsetup is executed after upgrading from Version 15.0B to this version, the cluster resources and scripts created by the old version's commands starting with "stgclset" will not be deleted.
The operational environment must be prepared prior to upgrading the Storage Cruiser's manager, as described below.
Install of essential package.
According to the environment in which the upgrade is performed, the packages required for primary node and secondary node should be installed.
The environment and the package are as follows. The installed package version shall be later than the described versions.
When the upgrade is performed excluding the following environments, this procedure is not needed.
For Red Hat Enterprise Linux 5 (for Intel64), 32-bit AdvancedCopy Manager is installed of the previous version:
libXrender-0.9.1-3.1.i386.rpm
For Red Hat Enterprise Linux 6 (for Intel64):
libXrender-0.9.5-1.el6.i686.rpm
Note
When libXrender is installed, other packages might be demanded. Install the package (the end of the package name is i386.rpm or i686.rpm) of 32-bit when OS is 64-bit environment.
The required packages for the installation are included in the OS installation media.
Check that the cluster application (transaction) has stopped on the secondary node.
Check whether the cluster application (transaction) to which ETERNUS SF Manager belongs has stopped.
If not stopped, stop the cluster application (transaction).
Refer to the relevant cluster software manuals for information on stopping the cluster application (transaction).
Stop the cluster application (transaction) on the primary node.
Stop the cluster application (transaction) to which ETERNUS SF Manager belongs.
However, the shared disk for shared data of ETERNUS SF Manager must be mounted.
Refer to the relevant cluster software manuals for information on stopping the cluster application (transaction).
If Managed Server transactions exist in a clustered system, perform the following.
On the secondary node for the target transactions, check that the Managed Server transactions have stopped.
If not stopped, stop them on the secondary node.
If multiple Managed Server transactions exist, perform this procedure for each secondary node for Managed Server transaction.
Refer to the relevant cluster software manuals for information on stopping the Managed Server transactions.
On the primary node for the target transactions, stop the Managed Server transactions.
Stop the Managed Server transactions by referring to the relevant cluster software manuals.
However, the shared disk for shared data of Managed Server transactions must be mounted.
If multiple Managed Server transactions exist, perform this procedure for each primary node for Managed Server transaction.
Stop the local transactions on all the nodes.
Stop the communication daemon for the local transactions of the AdvancedCopy Manager's manager.
Refer to "Starting and stopping the communication daemon" in the ETERNUS SF AdvancedCopy Manager Operation Guide relevant to the OS of the Management Server for this version for information on stopping the daemon.
Back up the environment and data.
On the primary and secondary nodes, back up the operating system.
On the primary node, back up the shared disk for shared data of ETERNUS SF Manager.
If Managed Server transactions exist in a clustered system, backup the shared disk for shared data of Managed Server transactions for each the primary node for Managed Server transactions.
Point
If a failure occurs during the upgrade, you cannot restore the environment to the pre-installation status (rollback). Therefore, it is recommended to back up the following before performing the upgrade.
Operating system
Shared disk for shared data of ETERNUS SF Manager
Shared disk for shared data of Managed Server transaction
If a failure occurs during the upgrade and you want to restore the environment to the pre-installation status, restore the system from the backup.
On the primary node, check that AdvancedCopy Manager's RDB daemon is started.
If not started, refer to "Starting and stopping the RDB daemon" in the ETERNUS SF AdvancedCopy Manager Operation Guide for this version for the corresponding operating system.
Note
If the RDB daemon is to be monitored in a clustered system, cancel the monitoring temporarily to perform the upgrade.
The following describes the upgrade procedure for the primary node.
Login to the server as a superuser.
Insert the DVD-ROM "ETERNUS SF SC/ACM Mediapack for Solaris (Manager Program) (2/2)", "ETERNUS SF SC/ACM/Express Mediapack for Linux (Manager Program) (2/2)" or "ETERNUS SF SC/ACM/Express Mediapack for Linux 64bit (Manager Program) (2/2)" for this version into the DVD-ROM drive.
Refer to "DVD-ROM contents" in the ETERNUS SF Installation and Setup Guide for this version for information on the DVD-ROM structure and detailed contents.
Mount the DVD-ROM (if automount is not enabled).
Example:
# mount /mnt/dvd
Change the directory on the DVD-ROM where the installation shell script is stored.
Example:
# cd /mnt/dvd/Manager_unix
Execute the following installation shell script:
# ./esfinstall.sh
The license agreement information will be displayed. Display example is mentioned below.
If the conditions are agreeable, enter "y".
License Agreement
Subject to the acceptance of the terms and conditions contained in this License Agreement
("Agreement"), Fujitsu Limited ("Fujitsu") grants to customers the license to use the obje
ct product as permitted hereunder.
This Agreement certifies the license to the ETERNUS SF Storage Cruiser / AdvancedCopy Mana
ger / Express ("Object Product") as permitted hereunder and your acceptance of the terms a
nd conditions hereof.
1. INSTALLATION
You are allowed to install and use manager module and agent module of the Object Product o
n any computer connected to the Storage Device directly or through network and you are als
o allowed to install and use client module of the Object Product on any computer.
2. ARCHIVAL COPY
You may make one (1) archival copy of the Object Product.
3. EMBEDDING
If the Object Product is expected to be used as embedded in another program, you may embed
the Object Product, in whole or in part, in such other program, in accordance with the pr
ocedure described in the applicable documentation.
4. NO ASSIGNMENT
You may not rent, lease, sublicense, assign, transfer or create lien against the Object Pr
oduct.
5. MODIFICATION
You may not modify or, except to the extent expressly permitted by applicable law, reverse
engineer (including, without limitation, decompile and disassemble) the Object Product, a
nd you may not permit others to do so.
6. LIMITED WARRANTY
(a) You acknowledge that Fujitsu cannot guarantee that your use of the Object Product will
be uninterrupted, that the Object Product will be error free or that all Product errors w
ill be corrected. However, if within ninety (90) days following your acquisition of the Ob
ject Product you notify the reseller from which you have acquired the Object Product of ph
ysical defects of the media containing the Object Product, Fujitsu will, at its sole discr
etion, correct the non-conformance or provide you with information necessary to correct th
e non-conformance, or replace the defective media with a new media. Only if you inform suc
h reseller of your problem with the Object Product during the above mentioned warranty per
iod and provide satisfactory evidence of the date you acquired the Object Product will Fuj
itsu be obligated to honor this warranty.
(b) THIS IS A LIMITED WARRANTY AND IT IS THE ONLY WARRANTY MADE BY FUJITSU. FUJITSU MAKES
NO OTHER WARRANTY, EXPRESS OR IMPLIED, AND EXPRESSLY DISCLAIMS ANY IMPLIED WARRANTY OF MER
CHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT OF THIRD PARTIES' RIGHTS
. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO LIMITATION MAY N
OT APPLY TO YOU. NO FUJITSU RESELLER, AGENT, EMPLOYEE IS AUTHORIZED TO MAKE ANY MODIFICATI
ONS, EXTENSIONS, OR ADDITIONS TO THIS WARRANTY. IF ANY MODIFICATIONS ARE MADE TO THE OBJEC
T PRODUCT BY YOU DURING THE WARRANTY PERIOD, IF THE MEDIA IS SUBJECTED TO ACCIDENT, ABUSE,
OR IMPROPER USE, OR IF YOU VIOLATE THE TERMS AND CONDITIONS HEREOF, THEN THIS WARRANTY SH
ALL IMMEDIATELY BE TERMINATED.
(c) LIMITATION OF LIABILITY. UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, TORT, CONTR
ACT, OR OTHERWISE, SHALL FUJITSU BE LIABLE TO YOU OR ANY OTHER PERSON FOR ANY INDIRECT, SP
ECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER, INCLUDING, WITHOUT LIMITATIO
N, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, OR LOSS OF DATA, OR FOR ANY DAMAGES IN EXC
ESS OF THE LIST PRICE TO THE PRODUCT, EVEN IF FUJITSU SHALL HAVE BEEN INFORMED OF THE POSS
IBILITY OF SUCH DAMAGES, OR FOR ANY CLAIM BY ANY OTHER PARTY. THIS LIMITATION OF LIABILITY
SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONNEL INJURY TO THE EXTENT APPLICABLE LAW P
ROHIBITS SUCH LIMITATION. FURTHERMORE, SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LI
MITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS LIMITATION AND EXCLUSION MAY NOT
APPLY TO YOU.
(d) The above states the entire liability of Fujitsu in connection with the use, performan
ce or non-performance of the Object Product.
(e) Even if a part of the Object Product has been developed by a third party, the warranty
and remedy for that part of the Object Product are limited to those provided for in this
Section, and the third party developer shall have no liability in connection with the use,
performance or non-conformance of the Object Product.
7. MISCELLANEOUS
(a) The terms and conditions hereof represent the complete agreement concerning this licen
se between the parties and supersede all prior or contemporaneous oral and written communi
cations between them. In the event that any additional terms or conditions are provided in
the accompanied documentation, you must also comply with such terms and conditions.
(b) You agree to comply with all applicable export laws and regulations.
(c) Use, duplication or disclosure of the Object Product by the U.S. Government is subject
to restrictions set forth in subparagraph (a) through (b) of the Commercial Computer-Rest
ricted Rights clause at FAR 52.227 - 19 when applicable, or in subparagraphs (c)(1) and (2
) of the Rights in Technical Data and Computer Software clause at DFAR 252.227 - 7013, and
in similar clauses in the NASA FAR Supplement. Contractor/manufacturer is Fujitsu Limited
, 1-1, Kamikodanaka 4-chome, Nakahara-ku, Kawasaki-shi, Kanagawa-ken 211-8588, Japan.
Do you accept the terms of the above License Agreement? (default: n) [y,n]:The following upgrade message will be displayed.
To continue the upgrade, enter "y". To discontinue, enter "q".
Do you want to upgrade? [y,q]:
If the upgrade completes successfully, the following message is displayed.
INFO: ETERNUS SF was installed successfully.
Change to a directory other than the DVD-ROM.
Example:
# cd
Unmount the DVD-ROM.
Example:
# umount /mnt/dvd
Eject the DVD-ROM.
Point
If the upgrade was terminated abnormally, refer to "Corrective actions to be taken when any error occurs in version upgrade from 15.x (for Solaris, Linux)" in the Software Release Guide, recover the system to the normal status.
When the upgrade has been completed, the tasks below need to be performed:
Check that AdvancedCopy Manager's RDB daemon is stopped.
Refer to "Starting and stopping the RDB daemon" in the ETERNUS SF AdvancedCopy Manager Operation Guide for this version for the corresponding operating system to stop the RDB daemon.
Note
If you have temporarily cancelled monitoring setting of the RDB daemon using "5.2.2.1 Preparing for the upgrade", set monitoring to RESUME status.
For the ETERNUS SF Manager Version 15.0B installed environment, perform the following procedure.
Edit the stxs_etcdir information within the AdvancedCopy Manager CCM environment setting file (/opt/FJSVccm/micc/sys/.install.sys) as follows:
Before | After |
|---|---|
stxs_etcdir=previousDir | stxs_etcdir=upgradedDir (*1) |
*1: Specify the value of stxs_etcdir set to the /opt/FJSVccm/noncluster/micc/sys/.install.sys file for upgradedDir.
Note
Do not change anything other than the stxs_etcdir line in the /opt/FJSVccm/micc/sys/.install.sys file.
The /opt/FJSVccm/noncluster/micc/sys/.install.sys file is for reference only, do not edit.
Edit the following environment setting files for ETERNUS SF Manager.
<Mount point of shared disk for shared data of ETERNUS SF Manager>/etc/opt/swstorage/clsetup.ini
<Mount point of shared disk for shared data of ETERNUS SF Manager>/etc/opt/swstorage/swstg.ini
Change the version information within each file, as follows:
Upgrade patterns | Descriptive contents of the version information | |
|---|---|---|
Before | After | |
Version 15.0B to 15.3 | Version=V15.0 | Version=V15.3 |
Version 15.1 to 15.3 | Version=V15.1 | |
Version 15.2 to 15.3 | Version=V15.2 | |
Note
Do not change anything other than the version information.
If Managed Server transactions exist in the clustered system, edit the environment setting files for AdvancedCopy Manager on the shared disk for shared data of Managed Server transactions, on the primary node for a target service.
On the primary node for target transactions, edit the following files:
<Mount point of shared disk for shared data of Managed Server transaction>/etc/opt/swstorage/clsetup.ini
<Mount point of shared disk for shared data of Managed Server transaction>/etc/opt/swstorage/swstg.ini
Change the version information within each file, as follows:
Upgrade patterns | Descriptive contents of the version information | |
|---|---|---|
Before | After | |
Version 15.0B to 15.3 | Version=V15.0 | Version=V15.3 |
Version 15.1 to 15.3 | Version=V15.1 | |
Version 15.2 to 15.3 | Version=V15.2 | |
Note
Do not change anything other than the version information.
For the ETERNUS SF Manager Version 15.0B installed environment, perform the following procedure.
Edit the line starting with "System=" in /opt/FJSVswstf/cluster/swcluster.ini as follows:
System=GEN
Note
Do not change anything other than the line starting with "System=".
If the SNMP Trap XML definition file has been customized, re-customize the definition file to use the new features of Storage Cruiser.
Customize the newly installed definition file:
1_3_6_1_4_1_789.xml
See
Refer to "SNMP Trap XML Definition File" in the ETERNUS SF Storage Cruiser Operation Guide for information on customizing the SNMP Trap XML definition file.
Perform the upgrade for the secondary node.
The upgrade procedure is the same as that for the primary node. Refer to "5.2.2.2 Performing the upgrade (Primary node)".
When the upgrade has been completed, the tasks below need to be performed:
For the ETERNUS SF Manager Version 15.0B installed environment, perform the following procedure.
Edit the stxs_etcdir information within the AdvancedCopy Manager CCM environment setting file (/opt/FJSVccm/micc/sys/.install.sys) as follows:
Before | After |
|---|---|
stxs_etcdir=previousDir | stxs_etcdir=upgradedDir (*1) |
*1: Specify the value of stxs_etcdir set to the /opt/FJSVccm/noncluster/micc/sys/.install.sys file for upgradedDir.
Note
Do not change anything other than the stxs_etcdir line in the /opt/FJSVccm/micc/sys/.install.sys file.
The /opt/FJSVccm/noncluster/micc/sys/.install.sys file is for reference only, do not edit.
For the ETERNUS SF Manager Version 15.0B installed environment, perform the following procedure.
Edit the line starting with "System=" in /opt/FJSVswstf/cluster/swcluster.ini as follows:
System=GEN
Note
Do not change anything other than the line starting with "System=".
After performing "5.2.2.3 Tasks to be performed after the upgrade (Primary node)" and "5.2.2.5 Tasks to be performed after the upgrade (Secondary node)", perform the following procedure:
Start the cluster application (transaction) on the primary node.
Start the cluster application (transaction) to which ETERNUS SF Manager belongs.
Refer to the relevant cluster software manuals for information on starting the cluster application (transaction).
If Managed Server transactions exist in a clustered system, start the Managed Server transactions on the primary node for the target transactions.
Refer to the relevant cluster software manuals to start the Managed Server transactions.
If multiple Managed Server transactions exist, perform this procedure for each Managed Server transaction.
Start the local transactions on all the nodes.
Start the communication daemon for local transactions of AdvancedCopy Manager's manager.
Refer to "Starting and stopping the communication daemon" in the ETERNUS SF AdvancedCopy Manager Operation Guide relevant to the OS of the Management Server for this version for information on starting the daemon.
Reset the password of the repository access user.
Execute the stguserset command to reset the password for the repository access user.
Point
Even if the password has not changed, ensure that you reset the password.
See
Refer to "Change of password or deletion of the user who was specified as the repository access user" in the ETERNUS SF AdvancedCopy Manager Operation Guide relevant to the OS of the Management Server for this version for information on the procedure.
Change the server information.
To ensure data consistency, execute the stgxfwcmmodsrv command to change the server information.
When executing the stgxfwcmmodsrv command, specify the Management Server name for the -n option.
Note
For changing the server information, start a new window for command execution, and then perform the procedure on the window.
See
Refer to "stgxfwcmmodsrv (Server information change command)" in the ETERNUS SF AdvancedCopy Manager Operation Guide relevant to the OS of the Management Server for this version for information on the command.
If Managed Server transactions exist in a clustered system, change the server information of the Managed Server transactions.
To ensure data consistency, execute the stgxfwcmmodsrv command to change the server information.
When executing the stgxfwcmmodsrv command, specify the Managed Server name for the -n option.
This operation should be performed on the primary node for Management Server transactions.
If multiple Managed Server transactions exist, perform this procedure for each Managed Server transaction.
Note
For changing the server information, start a new window for command execution, and then perform the procedure on the window.
See
Refer to "stgxfwcmmodsrv (Server information change command)" in the ETERNUS SF AdvancedCopy Manager Operation Guide relevant to the OS of the Management Server for this version for information on the command.