1. Manuals
  2. Brands
  3. Fujitsu Manuals
  4. Storage
  5. ETERNUS SF Express V16.6
  6. Migration manual

Fujitsu ETERNUS SF Express V16.6 Migration Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
FUJITSU Storage
ETERNUS SF
Express V16.6 / Storage Cruiser V16.6 /
AdvancedCopy Manager V16.6
Migration Guide
B1FW-6000-07ENZ0(00)
December 2017

Advertisement

Table of Contents
loading

Related Manuals for Fujitsu ETERNUS SF Express V16.6

Summary of Contents for Fujitsu ETERNUS SF Express V16.6

  • Page 1 FUJITSU Storage ETERNUS SF Express V16.6 / Storage Cruiser V16.6 / AdvancedCopy Manager V16.6 Migration Guide B1FW-6000-07ENZ0(00) December 2017...
  • Page 2 This manual describes how to upgrade to this version from the previous version for the following products: FUJITSU Storage ETERNUS SF Express (hereafter abbreviated as "Express") FUJITSU Storage ETERNUS SF Storage Cruiser (hereafter abbreviated as "Storage Cruiser") FUJITSU Storage ETERNUS SF AdvancedCopy Manager (hereafter abbreviated as "AdvancedCopy Manager")
  • Page 3 Appendix A Operation for Previous Version Environment This appendix describes the operations performed in the environment of the previous version. Appendix B Installation parameter This appendix describes the install parameter file and the details of each install parameter. Appendix C Performing Upgrading This appendix describes the upgrading procedure.
  • Page 4 FUJITSU Storage ETERNUS DX8100 ETERNUS DX8000 series FUJITSU Storage ETERNUS DX8400 FUJITSU Storage ETERNUS DX8700 FUJITSU Storage ETERNUS DX60 S2 ETERNUS DX S2 series FUJITSU Storage ETERNUS DX80 S2 FUJITSU Storage ETERNUS DX90 S2 FUJITSU Storage ETERNUS DX410 S2...
  • Page 5 FUJITSU Storage ETERNUS SF Express / Storage Cruiser / AdvancedCopy Manager ETERNUS SF Glossary Glossary Besides the above-mentioned, each individual manual name in this document is listed with "FUJITSU Storage" omitted from it. Others In this manual, the following products are collectively described as "Windows Server 2008 or later".
  • Page 6 Windows Server 2012 Windows Server 2012 R2 Windows Server 2016 In this manual, the following products are collectively described as "Windows Server 2012 or later". Windows Server 2012 Windows Server 2012 R2 Windows Server 2016 In this manual, unless there is a special disclaimer, ETERNUS Disk storage system includes the ETERNUS AF All-Flash Arrays and the ETERNUS DX200F All-Flash Array.
  • Page 7 B1FW-6000-07ENZ2(00) Notes No part of this manual may be reproduced without permission. This manual is subject to change without advance notice. Copyright Copyright 2013-2017 FUJITSU LIMITED Update History Content of Update Updated Section Revision The information related to ETERNUS DX200F is described.
  • Page 8 Content of Update Updated Section Revision 10.1.1.3, 10.1.2.4, 10.1.2.5, 10.2.1.3, 10.2.2.4, 10.2.2.5 The upgrade procedure of the RHEL6 environment is added. 6.5.2, 7.5.4 The information related to Red Hat(R) Enterprise Linux(R) AS v.4 and 6.6, 7.6, 9.5, 9.5.1, 9.5.2, 9.5.8, Red Hat(R) Enterprise Linux(R) ES v.4 is deleted.
  • Page 9 Content of Update Updated Section Revision 10.4.2.3, 10.4.2.3.1, 11.2.3, 11.2.5, 11.3.4, 11.3.6 The explanation of upgrading from Version 16.2 is added. 7.1.2.4, 7.2.2.4, 10.1.2.4, 10.2.2.4, 10.3.2.4, 10.4.2.4 Information about the install parameter AdvancedCopy_Manager_ARCH B.1, B.2, C.2 is deleted. Information about the install parameter StartService is added. B.1, B.2, C.2 Description of the work required for migration from Version 16.0 or Chapter 2, 2.3.1, Chapter 3, 3.1.3.1,...
  • Page 10 Content of Update Updated Section Revision Information related to SUSE Linux Enterprise Server 12 for AMD64 & "Notation" in Preface Intel64 is added. Information related to the ETERNUS DX60 S4/DX100 S4/DX200 S4 is "Notation" in Preface added. In [Point] at the beginning of each chapter, the reference destination Chapter 5 - 10 related to the combination of the manager program and the agent program is changed.
  • Page 11 Related Products Related Manuals (*1) When to Read Explanation (Abbreviated) Cluster Environment This manual is common for Storage Cruiser and Setup Guide AdvancedCopy Manager. Migration Guide This manual is common for all products. During Operation Guide This manual is unique for each product. The following operation manuals are available: Express Operation Guide...
  • Page 12 Purpose Manual Main Contents How to Read Confirming the Release Notes New function overview Read if you want to know the updated updated contents from a Incompatibilities with contents previous version and if you previous version perform the upgrade. Fixed bugs Deciding if an Migration Guide Notes and cautions about the...
  • Page 13 Purpose Manual Main Contents How to Read Command reference AdvancedCopy Manager Operation Starting and stopping the Guide (for Windows) software AdvancedCopy Manager Operation Data backup/restore inside Guide (for Solaris) the storage system AdvancedCopy Manager Operation Necessary tasks after an Guide (for Linux) architectural modification of the system as well as product AdvancedCopy Manager Operation...

  • Page 14: Table Of Contents

    Contents Chapter 1 Overview..................................... 1 1.1 Upgrade Patterns..................................1 1.2 What Is Upgrade Installation..............................2 1.3 Products Which Can Be Upgraded with Upgrade Installation..................... 3 1.4 Notes on Upgrade..................................4 Chapter 2 Upgrade from Express Version 14.x............................. 6 2.1 Preparing for Upgrade................................6 2.1.1 Backing Up Operational Environment of Previous Version....................
  • Page 15 3.2.3.1 Restoring Operational Environment from Previous Version..................18 3.2.3.2 Importing Configuration Information......................... 19 3.2.3.3 Redefining Operational Environment.........................19 3.2.3.4 Deleting Backup Data..............................20 3.2.3.5 Uninstalling Symfoware............................. 20 3.2.4 Resuming Operation................................. 20 Chapter 4 Upgrade from Express Version 16.x........................... 22 4.1 Upgrading Express (for Windows)............................22 4.1.1 Preparing for Upgrade..............................
  • Page 16 6.1.1.3.1 Restoring Environment from Previous Version.....................44 6.1.1.3.2 Importing Configuration Information........................45 6.1.1.3.3 Redefining Operational Environment........................45 6.1.1.3.4 Change Associated Software..........................46 6.1.1.3.5 Deleting Backup Data............................46 6.1.1.3.6 Uninstalling Symfoware............................47 6.1.1.4 Resuming Operation..............................47 6.1.2 Upgrading on Clustered Systems............................47 6.1.2.1 Manual Backing Up Operational Environment......................
  • Page 17 6.5 Upgrading Storage Cruiser's Agent (for Linux)......................... 82 6.5.1 Preparing for Upgrade..............................82 6.5.1.1 Backing Up Operational Environment of Previous Version..................83 6.5.2 Performing Upgrade................................. 83 6.6 Upgrading Storage Cruiser's Agent (for HP-UX, AIX).........................84 Chapter 7 Upgrade from Storage Cruiser Version 16.x........................
  • Page 18 7.5.3.1 Performing Upgrade with Silent Installation Procedure....................116 7.5.3.2 Confirming Results of Upgrade with Silent Installation.................... 117 7.5.4 Tasks to Be Performed After Upgrade..........................117 7.6 Upgrading Storage Cruiser's Agent (for HP-UX, AIX).......................117 Chapter 8 Upgrade from AdvancedCopy Manager Version 14.x....................... 119 8.1 Upgrading AdvancedCopy Manager's Manager........................
  • Page 19 9.1 Upgrading AdvancedCopy Manager's Manager (for Windows)....................136 9.1.1 Upgrading on Non-clustered Systems..........................136 9.1.1.1 Preparing for Upgrade..............................136 9.1.1.1.1 Backing Up Operational Environment of Previous Version.................136 9.1.1.1.2 Checking for Available Disk Space........................137 9.1.1.1.3 Uninstalling Incompatible Software........................137 9.1.1.1.4 Estimating Database Size..........................
  • Page 20 9.3.2.2 Performing Upgrade (Primary Node)........................169 9.3.2.3 Tasks to Be Performed After Upgrade (Primary Node)....................172 9.3.2.4 Performing Upgrade (Secondary Node)........................173 9.3.2.5 Tasks to Be Performed After Upgrade (Secondary Node)..................173 9.3.2.6 Starting Managed Server Transactions........................173 9.4 Upgrading AdvancedCopy Manager's Agent (for Solaris, Linux).....................174 9.4.1 Upgrading on Non-clustered Systems..........................
  • Page 21 9.7.2.2 Performing Upgrade (Primary Node)........................198 9.7.2.3 Performing Upgrade (Secondary Node)........................198 9.7.2.4 Tasks to Be Performed After Upgrade (Primary Node)....................198 9.7.2.5 Tasks to Be Performed After Upgrade (Secondary Node)..................199 9.7.2.6 Start CCM Server Transactions...........................200 9.7.3 Resuming Operation............................... 200 Chapter 10 Upgrade from AdvancedCopy Manager Version 16.x.....................
  • Page 22 10.4.1 Upgrading on Non-clustered Systems........................... 231 10.4.1.1 Preparing for Upgrade............................231 10.4.1.2 Performing Upgrade...............................233 10.4.1.3 Upgrade with Silent Installation Tasks........................234 10.4.1.3.1 Performing Upgrade with Silent Installation Procedure...................234 10.4.1.3.2 Confirming Results of Upgrade with Silent Installation..................235 10.4.1.4 Tasks to Be Performed After Upgrade........................
  • Page 23 11.1.2 In Case of Problem During Installation of This Version....................253 11.2 In Case of Problem During Upgrade from Version 15.x......................254 11.2.1 In Case of Problem During Upgrade of ETERNUS SF Manager (for Windows, Solaris, Linux).......... 254 11.2.2 In Case of Problem During Upgrade of Storage Cruiser's Agent (for Windows)..............
  • Page 24 A.27 Backup of Manager Operation Environment (for Solaris, Linux)..................309 A.28 Backup of Solaris/Linux Version Manager Operation Environment (for Cluster Environment)..........311 A.29 Restoring of Manager Operation Environment (for Windows)..................... 311 A.30 Restoring of Windows Version Manager Operation Environment (for Cluster Environment)..........

  • Page 25: Chapter 1 Overview

    Chapter 1 Overview This chapter is an overview of the upgrade process from a previous version to this version for Express, Storage Cruiser, and AdvancedCopy Manager. 1.1 Upgrade Patterns This section explains the system configuration before upgrade and after upgrade. Point This version product combinations obey to the following rules: Express cannot be combined with Storage Cruiser in a same system environment.

  • Page 26: What Is Upgrade Installation

    Combination of Products Express Storage Cruiser AdvancedCopy AdvancedCopy Reference Manager Manager Copy Control Module "Chapter 8 Upgrade from AdvancedCopy Manager Version 14.x" When upgrading from AdvancedCopy Manager Version 15.x: "Chapter 9 Upgrade from AdvancedCopy Manager Version 15.x" When upgrading from AdvancedCopy Manager Version 16.x: "Chapter Upgrade...

  • Page 27: Products Which Can Be Upgraded With Upgrade Installation

    1.3 Products Which Can Be Upgraded with Upgrade Installation The products which can be upgraded with the Upgrade Installation are as follows. For Windows Products Which Can Use Upgrade Installation Product After Upgrade ETERNUS SF Express Version 14.x ETERNUS SF Express Version 16.6 ETERNUS SF Express Version 15.x ETERNUS SF Express Version 16.x ETERNUS SF Storage Cruiser Version 14.x (*1)

  • Page 28: Notes On Upgrade

    It is not possible to use the Upgrade Installation provided in this manual. Uninstall the previous version product and install this version product. Afterwards, perform as new all necessary setup and customization operations for this version. 1.4 Notes on Upgrade Operating Systems The operating system version on the server where the upgrade is performed must be supported by the version of the product that is installed.
  • Page 29 When automatic mount (autofs) is used for DVD-ROM, specify the iso9660 file system for the /etc/fstab file. Also, for RHEL5 (Intel64), specify "exec" for the mount option. The following is a description example of the /etc/fstab file for RHEL5 (Intel64). /dev/cdrom /mnt iso9660 exec...

  • Page 30: Chapter 2 Upgrade From Express Version 14.X

    Chapter 2 Upgrade from Express Version 14.x To upgrade Express Version 14.x to this version, install the ETERNUS SF Manager. Point The Upgrade Installation is available for Express. If upgrading Express, the following information cannot be imported from the previous version: Event log history Login/Logout history Configuration modification history...

  • Page 31: Checking For Available Disk Space

    Server Type Reference Storage Management Server which also Perform the steps of "A.1 Backing Up Repository Data (for Windows)", and serves as a Storage Server then perform the steps of "A.3 Backing Up Management Information (for Windows)". If AdvancedCopy Manager Copy Control Module is installed, back up the AdvancedCopy Manager Copy Control Module operational environment of the previous version.

  • Page 32: Performing Upgrade

    2.2 Performing Upgrade Refer to "C.1 Procedures for Upgrade Installation of Manager Feature of Express / Storage Cruiser / AdvancedCopy Manager Version 14.x and 15.x (for Windows)" to perform the upgrade. Note the following points when you upgrade: When requested to restart the computer, click No. If Yes is clicked, the upgrade is interrupted.

  • Page 33: Setting Up User Account

    programDir\Common\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"...
  • Page 34 Log in to Web Console. On the global navigation tab, click Server. To register the server, click Register under Server on the Action pane. If the server is registered successfully, the server is displayed in the server list of the Main pane. After checking the target server checkbox on the Main pane, click Reload Conf.

  • Page 35: Uninstalling Symfoware

    Point When the ETERNUS Disk storage system was registered by specifying a nonexistent drive letter or device name to the access volume (previously called "access path") in the previous version, re-register its ETERNUS Disk storage system as a remote device. Perform the following operations with Web Console to reload the server information.

  • Page 36: Chapter 3 Upgrade From Express Version 15.X

    Chapter 3 Upgrade from Express Version 15.x To upgrade Express Version 15.x to this version, install the ETERNUS SF Manager. Point The following information cannot be imported from the previous version: Operation History Events Login/Logout history Threshold Monitoring Alarms It is possible to perform an Upgrade Installation with existing Advanced Copy and Remote Advanced Copy sessions. Regardless of whether there are Advanced Copy sessions or not, the upgrade procedure is the same.

  • Page 37: Checking For Available Disk Space

    Stop the ETERNUS SF Manager service Execute the following batch file: $INS_DIR\Common\bin\Stop_ESFservice.bat The $INS_DIR is the program directory specified at the ETERNUS SF Manager installation. Implement backup of the previous version. Execute the following batch file. For backupDir, specify the directory in which to store the backup data with an absolute path.

  • Page 38: Preparing For Uninstallation

    Refer to "Before Installation" in "Installation of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for this version for details. 3.1.1.5 Preparing for Uninstallation Refer to "A.7 Unsetting Up Database" to perform the repository database unsetup of the previous version: 3.1.2 Performing Upgrade Refer to "C.1 Procedures for Upgrade Installation of Manager Feature of Express / Storage Cruiser / AdvancedCopy Manager Version 14.x...

  • Page 39: Importing Configuration Information

    The $INS_DIR is the program directory specified at the ETERNUS SF Manager installation. 3.1.3.2 Importing Configuration Information Import the configuration information from the previous version by executing the esfadm devconf import command using Administrator privileges. Check that the managed devices and servers can be accessed before executing the esfadm devconf import command.

  • Page 40: Upgrading Express (For Linux)

    Note If operating Web Console from the same web browser as before the upgrade, delete the web browser's cache prior to operation. Information After upgrading to this version, when changing the SNMP communication protocol used for fault management from SNMPv1 to SNMPv3, refer to the following section in the chapter "Maintenance"...

  • Page 41: Checking For Available Disk Space

    function with an absolute path. When the performance management function is not being used, it is unnecessary to specify a directory for the tmpDir. # /mnt/dvd/Manager_unix/vuptools/esfpreinst.sh backupDir [tmpDir] When the backup fails, after confirming the output error message and removing the cause of the failure, execute the command again.

  • Page 42: Confirming Port Number For Communication Service

    Refer to "Before Installation" in "Installation of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for this version for information on tuning. 3.2.1.6 Confirming Port Number for Communication Service Ensure the new ports are available before starting the upgrade. Refer to "Before Installation"...

  • Page 43: Importing Configuration Information

    absolute path. When the files related to the performance management function is not backed up, it is unnecessary to specify a directory for the tmpDir. # /mnt/dvd/Manager_unix/vuptools/esfpostinst.sh backupDir [tmpDir] When the restore fails, after confirming the output error message and removing the cause of the failure, execute the command again.

  • Page 44: Deleting Backup Data

    3.2.3.4 Deleting Backup Data Once normal operation has been confirmed after the upgrade, the backup data in the backup destination directory created in step 5 "3.2.1.1 Backing Up Operational Environment of Previous Version" maybe deleted. 3.2.3.5 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.
  • Page 45 However, when you change the SELinux setting to "enforcing" mode during the upgrade, refer to the following section in the chapter "Setup of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for this version and restart the operation after the installation of the SELinux policy module for snmptrapd.

  • Page 46: Chapter 4 Upgrade From Express Version 16.X

    Chapter 4 Upgrade from Express Version 16.x To upgrade Express Version 16.x to this version, install the ETERNUS SF Manager. 4.1 Upgrading Express (for Windows) 4.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.

  • Page 47: Tasks To Be Performed After Upgrade

    Point If the Upgrade Installation has ended in an error, refer to "11.3.1 In Case of Problem During Upgrade of ETERNUS SF Manager (for Windows)" and return the system to a normal state. 4.1.3 Tasks to Be Performed After Upgrade The tasks below need to be performed.

  • Page 48: Upgrading Express (For Linux)

    In the pre-upgrade environment, the patch for Problem Report Number PH09090 has already been applied to the Management Server. The storage device that is in use is the ETERNUS DX60 S3/DX100 S3/DX200 S3 or the ETERNUS DX200F, whose firmware version is V10L60 or later. If the above conditions are not satisfied and you use the new supported function from this version level, perform the following operations with Web Console to reload the server information.

  • Page 49: Performing 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.

  • Page 50: Resuming Operation

    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)
  • Page 51 In the pre-upgrade environment, the patch for Problem Report Number PH09090 has already been applied to the Management Server. The storage device that is in use is the ETERNUS DX60 S3/DX100 S3/DX200 S3 or the ETERNUS DX200F, whose firmware version is V10L60 or later. If the above conditions are not satisfied and you use the new supported function from this version level, perform the following operations with Web Console to reload the server information.

  • Page 52: Chapter 5 Upgrade From Storage Cruiser Version 14.X

    Chapter 5 Upgrade from Storage Cruiser Version 14.x Point For Storage Cruiser programs, the Upgrade Installation can be performed for the Storage Cruiser's manager only. For upgrading the Storage Cruiser's agent, perform uninstallation and then perform a new installation of this version. Refer to "5.2 Upgrading Storage Cruiser's Agent"...
  • Page 53 Performance monitoring If the performance monitoring was performed with the previous version, refer to the following information related to the performance monitoring with the GUI client of the previous version and record the configuration information of the previous version. Interval that obtains performance information (in seconds) Performance monitoring target (only for ETERNUS Disk storage system.

  • Page 54: Checking For Available Disk Space

    > esflm backup backupFileName Backup of license database was performed successfully 5.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".

  • Page 55: Preparing For Uninstallation

    Refer to "Before Installation" in "Installation of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for this version for information on port numbers. 5.1.1.7 Preparing for Uninstallation If AdvancedCopy Manager is installed, before starting the upgrade, the following preparation is necessary before uninstalling the previous version.

  • Page 56: Performing Upgrade (For Solaris, Linux)

    5.1.3 Performing Upgrade (for Solaris, Linux) Refer to "C.2 Procedures for Upgrade Installation of Manager Feature of Express / Storage Cruiser / AdvancedCopy Manager Version 14.x and 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.

  • Page 57: Importing Configuration Information

    If AdvancedCopy Manager and/or AdvancedCopy Manager Copy Control Module was installed, restore the definition of the license information. Restore the license management database of ETERNUS SF License Manager by executing the esflm restore command. Refer to the ETERNUS SF Installation and Setup Guide for this version for information on the command. Example of executing the command is shown below.

  • Page 58: Setting Account Information For Access To Eternus Disk Storage System

    5.1.4.5 Setting Account Information for Access to ETERNUS Disk Storage System Set the account information, user name and password to access the ETERNUS Disk storage system. Refer to "Set/Change Information of Account That Can Access ETERNUS Disk Storage System" in the ETERNUS SF Web Console Guide for information on setup.
  • Page 59 Refer to the following sections in the ETERNUS SF Web Console Guide for this version for details on the above operations: "Register Server" "Change Server Information" "Reload Server Configuration Information" Reconfiguring the iSCSI HBA information If iSCSI was defined before the upgrade, based on the information that was backed up in step 1 of "5.1.1.1 Backing Up Operational Environment of Previous Version", perform the following procedure:...

  • Page 60: Uninstalling Symfoware

    Reconfiguring the AdvancedCopy Manager Copy Control Module configuration information To use the AdvancedCopy Manager Copy Control Module, set the device information again in accordance with the following procedure: Refer to "Command References" in the ETERNUS SF AdvancedCopy Manager Operation Guide for Copy Control Module for this version for information on the commands.
  • Page 61 The procedures to uninstall Symfoware are stated below. For Windows Uninstall Symfoware from the Add or Remove Programs or Programs and Features page. If both Symfoware Server and Symfoware Client are installed, uninstall Symfoware Client first. For Solaris or Linux Start the uninstaller of Symfoware to delete the Symfoware package.

  • Page 62: Resuming Operation

    5.1.5 Resuming Operation When the tasks described above have been performed, the upgrade of the Storage Cruiser's manager is complete. Restart the Storage Cruiser operation. Point When upgrading as well as changing the setting in SELinux to "enforcing" in the Linux environment, install the SELinux policy module for snmptrapd and then restart the operation.
  • Page 63 Install this version of the Storage Cruiser's agent. Refer to "Installation of Storage Cruiser's Agent" in the ETERNUS SF Installation and Setup Guide for this version for information on installation. Set up this version of the Storage Cruiser's agent. For Windows No actions are necessary.
  • Page 64 On the Main pane, check the target server checkbox. On the Action pane, click Reload Conf. under Server. - 40 -...

  • Page 65: Chapter 6 Upgrade From Storage Cruiser Version 15.X

    Chapter 6 Upgrade from Storage Cruiser Version 15.x To upgrade Storage Cruiser Version 15.x to this version, install the ETERNUS SF Manager. Point In the version level of the Storage Cruiser, there are conditions for the combination of manager and agent. Upgrade your version, in order to fulfill the combination that is described in "Notes on Combining Different Versions"...
  • Page 66 VMware vCenter Server configuration information If VMware vCenter Server was registered in the Storage Cruiser's manager of the previous version, record the configuration information of the previous version with the following procedure: Log in to Web Console. On the global navigation tab, click Server. On the Category pane, click Correlation.

  • Page 67: Checking For Available Disk Space

    Move the files (tmpDir) related to the performance management function to the same logical drive as the drive on which the product of the previous version is installed. In the case of backup to a different logical drive, it may take time to perform backup and restore.

  • Page 68: Tasks To Be Performed After Upgrade

    6.1.1.3 Tasks to Be Performed After Upgrade 6.1.1.3.1 Restoring Environment from Previous Version With the following procedure, restore the operation environment of the previous version of the Storage Cruiser's manager. Note that if step 1 and step 2 have already been performed, perform from step 3. Information About the notation in procedure Directory Name...

  • Page 69: Importing Configuration Information

    Customization Definition files $ENV_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\polling\pollingService.xml Restart the service of ETERNUS SF Manager Execute the following batch file: $INS_DIR\Common\bin\Start_ESFservice.bat 6.1.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.

  • Page 70: Change Associated Software

    If the following software was being used with the previous version, it is necessary to update these to a version that supports this version. ETERNUS VASA Provider Fujitsu ETERNUS Storage Systems Monitoring Pack Note If operating Web Console from the same web browser as before the upgrade, delete the web browser's cache prior to operation.

  • Page 71: Uninstalling Symfoware

    6.1.1.3.6 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. Uninstall Symfoware from the Add or Remove Programs or Programs and Features page.

  • Page 72: Preparing For Upgrade

    Record the IP address and the port number of VMware vCenter Server that are displayed in the Main pane. Hyper-V host configuration information If the Hyper-V hosts were registered in the Storage Cruiser's manager of the previous version, record the configuration information of the previous version with the following procedure: Log in to Web Console.
  • Page 73 Select "AdvancedCopy Manager COM Service" and then click Stop. On the primary node, perform a backup of the operating environment of the previous version of the Storage Cruiser's manager. Refer to "A.33 Capacity Necessary for Backup of Previous Version" for information on the capacity required to perform a backup. Log on to the server using Administrator privileges.
  • Page 74 Estimating the database size A database is necessary for this version of Storage Cruiser. The database size must be estimated before starting the upgrade. Refer to "Before Installation" in "Installation of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for this version for details.

  • Page 75: Performing Upgrade (Primary Node)

    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 ETERNUS SF Installation and Setup Guide for the relevant previous version for information on the required disk space. 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.

  • Page 76: Tasks To Be Performed After Upgrade (Primary Node)

    6.1.2.5 Tasks to Be Performed After Upgrade (Primary Node) The tasks below need to be performed on the primary node. Stop the ETERNUS SF Manager services. Use the Failover Cluster Manager to stop the transactions of ETERNUS SF Manager. However, the shared disk for shared data of ETERNUS SF Manager must be online. Restore the operation environment of the previous version of the Storage Cruiser's manager.
  • Page 77 <Drive of shared disk for shared data of Managed Server transactions>:\etc\opt\swstorage\clsetup.ini <Drive of shared disk for shared data of Managed Server transactions>:\etc\opt\swstorage\etc\swstg.ini Change the version information within each file, as follows. Descriptive Contents of Version Information Upgrade Patterns Before After Version 15.0B to 16.6 Version=V15.0 Version 15.1 to 16.6...

  • Page 78: Tasks To Be Performed After Upgrade (Secondary Node)

    It is necessary to reinstall a version of the ETERNUS VASA Provider that supports this version. If the Fujitsu ETERNUS Storage Systems Monitoring Pack was being used with the previous version It is necessary to reinstall a version of the Fujitsu ETERNUS Storage Systems Monitoring Pack that supports this version. 6.1.2.6 Tasks to Be Performed After Upgrade (Secondary Node) The tasks below need to be performed on the secondary node.

  • Page 79: Starting Eternus Sf Manager

    It is necessary to reinstall a version of the ETERNUS VASA Provider that supports this version. If the Fujitsu ETERNUS Storage Systems Monitoring Pack was being used with the previous version It is necessary to reinstall a version of the Fujitsu ETERNUS Storage Systems Monitoring Pack that supports this version. 6.1.2.7...

  • Page 80: Redefining Operational Environment

    Information After upgrading to this version, when changing the SNMP communication protocol used for fault management from SNMPv1 to SNMPv3, refer to "Changing SNMP Communication Protocol of Management Server" in the ETERNUS SF Storage Cruiser Operation Guide for this version and configure your operational environment. 6.1.2.8 Redefining Operational Environment Re-registering the server information...

  • Page 81: Upgrading Storage Cruiser's Manager (For Solaris, Linux)

    On the global navigation tab, click Server. On the Category pane, click Correlation. The items of the Category pane change into the items concerning the correlation management. On the Category pane, click End to End View (Hyper-V). On the Main pane, check the target server checkbox to register as a Hyper-V host. On the Action pane, click Register/Reload under Hyper-V Host.

  • Page 82: Checking For Available Disk Space

    Insert the DVD-ROM "ETERNUS SF SC/ACM Mediapack for Solaris (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.

  • Page 83: Estimating Database Size

    Refer to "Operating Environment of ETERNUS SF Manager" in the ETERNUS SF 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 Storage Cruiser. The database size must be estimated before starting the upgrade. Refer to "Before Installation"...

  • Page 84: Tasks To Be Performed After 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 Storage Cruiser's manager.

  • Page 85: Importing Configuration Information

    If the polling service setting file is customized in the environment of the previous version, it is necessary to customize this version as well. Save the polling service setting file that is stored in the following directory to an arbitrary location. After that, refer to "Polling Service Setting File"...

  • Page 86: Deleting Backup Data

    On the Server List screen, check whether "AdvancedCopy Manager" is displayed in the Function Level column of the registered server. If it is displayed, what you have to do is finished at this step. If it is not displayed, go to step 3. On the Server List screen, after checking the checkbox of the server using AdvancedCopy Manager, click Modify under Server on the Action pane.

  • Page 87: Upgrading On Clustered Systems

    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".

  • Page 88: Preparing For Upgrade

    Interval that obtains performance information (in seconds) Performance monitoring target (only for ETERNUS Disk storage system. Minimum LUN_V, Maximum LUN_V) VMware vCenter Server configuration information If VMware vCenter Server was registered in the Storage Cruiser's manager of the previous version, record the configuration information of the previous version with the following procedure: Log in to Web Console.
  • Page 89 On the primary node, perform a backup of the operating environment of the previous version of the Storage Cruiser's manager. Refer to "A.33 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.
  • Page 90 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 ETERNUS SF Installation and Setup Guide for the relevant previous version for information on the required disk space. 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.
  • Page 91 Insert the DVD-ROM "ETERNUS SF SC/ACM Mediapack for Solaris (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.
  • Page 92 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 ETERNUS SF Installation and Setup Guide for the relevant previous version for information on the required disk space. 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.

  • Page 93: Performing Upgrade (Primary Node)

    In cases when Managed Server transactions coexist, do not release the configurations of these Managed Server transactions. 6.2.2.3 Performing Upgrade (Primary Node) Refer to "C.2 Procedures for Upgrade Installation of Manager Feature of Express / Storage Cruiser / AdvancedCopy Manager Version 14.x and 15.x (for Solaris, Linux)"to perform the upgrade.
  • Page 94 Descriptive Contents of Version Information Upgrade Patterns Before After Version 15.0B to 16.6 Version=V15.0 Version 15.1 to 16.6 Version=V15.1 Version=V16.6 Version 15.2 to 16.6 Version=V15.2 Version 15.3 to 16.6 Version=V15.3 Note Do not change anything other than the version information. Restore the operation environment of the previous version of the Storage Cruiser's manager.
  • Page 95 Save the SNMP Trap XML definition file that is stored in the following directory to an arbitrary location. After that, refer to "SNMP Trap XML Definition File" in the ETERNUS SF Storage Cruiser Operation Guide and customize the SNMP Trap XML definition file. For the contents of the customization, refer to the SNMP Trap XML definition file which was saved to the arbitrary location.
  • Page 96 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"...

  • Page 97: Tasks To Be Performed After Upgrade (Secondary Node)

    [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 the Solaris environment). Delete after confirming that this package function is used only by ETERNUS SF Manager. # pkgrm FSUNiconv 6.2.2.6 Tasks to Be Performed After Upgrade (Secondary Node)
  • Page 98 Unmount the DVD-ROM. Example: # umount /mnt/dvd Eject the DVD-ROM. 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.

  • Page 99: Starting Managed Server Transactions

    As required, perform the SNMP Trap configuration (for Linux only). Only when the FJSVswstt package is installed using the procedure described in the step 15 of "6.2.2.2 Preparing for Upgrade", perform the operation described in the following section in "Setup of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for this version.

  • Page 100: Resuming Operation

    Note Information related to the captured capacity before the upgrade is not displayed on the Dashboard. Confirm with the Capacity Graph screen of Thin Provisioning Pool. Re-registering the VMware vCenter Server configuration information If VMware vCenter Server was registered in the Storage Cruiser's manager of the previous version, re-register VMware vCenter Server with the following procedure: Log in to Web Console.

  • Page 101: Performing Upgrade

    Log on to the server using Administrator privileges. Insert the DVD-ROM "ETERNUS SF SC/ACM/Express Mediapack (Agent Program and Manual)" 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.
  • Page 102 The following window is displayed. Click Storage Cruiser installation. The following dialog box is displayed. Click Yes. - 78 -...

  • Page 103: Tasks To Be Performed After Upgrade

    When the upgrade is completed, the following installation wizard page is displayed. The upgrade process is completed. Click Finish. Eject the DVDROM. 6.3.3 Tasks to Be Performed After Upgrade Perform the following procedure: Note that in these tasks, in addition to operations with the Managed Server, there are operations to execute from Web Console. Point When performing an upgrade of Storage Cruiser's manager at the same time, perform the following procedures after completing the upgrade of Storage Cruiser's manager.

  • Page 104: Upgrading Storage Cruiser's Agent (For Solaris)

    Activate the Storage Cruiser Agent Service. Open the Service Control Manager and activate the ETERNUS SF Storage Cruiser Agent Service. Perform the following operations with Web Console to reload the server information. On the global navigation tab, click Server. The registered server list is displayed in the Main pane. On the Main pane, check the target server checkbox.

  • Page 105: Performing Upgrade

    The following message is displayed. To continue, enter "y". To discontinue, enter "n" or "q". ETERNUS SF Storage Cruiser 16.6 Copyright FUJITSU LIMITED 2013-2017 This program will upgrade "ETERNUS SF Storage Cruiser" Agent on your system. Do you want to continue the upgrade of this package? [y,n,?,q] If "y"...

  • Page 106: Tasks To Be Performed After Upgrade

    Installing Storage System Agent for ETERNUS SF as <FJSVssage> Upgrade of <FJSVssage> was successful. INFO : "ETERNUS SF Storage Cruiser" Agent was upgraded successfully. If the upgrade fails, the following message is displayed. ERROR : not privileged ERROR : "ETERNUS SF Storage Cruiser" Agent cannot be installed in non-global zone. ERROR : Upgrading FJSVssage was failed.

  • Page 107: Backing Up Operational Environment Of Previous Version

    The following message is displayed. To continue, enter "y". To discontinue, enter "n" or "q". ETERNUS SF Storage Cruiser 16.6 Copyright FUJITSU LIMITED 2013-2017 This program will upgrade "ETERNUS SF Storage Cruiser" Agent on your system. Do you want to continue the upgrade of this package? [y,n,?,q] If "y"...

  • Page 108: Upgrading Storage Cruiser's Agent (For Hp-Ux, Aix)

    INFO : Starting Upgrade of ETERNUS SF Storage Cruiser ... INFO : Upgrade of <FJSVssage> was successful. INFO : ETERNUS SF Storage Cruiser Agent was upgraded successfully. If the upgrade fails, the following message is displayed. ERROR : not privileged INFO : Upgrade is terminated.
  • Page 109 Set up the Storage Cruiser's agent. Refer to "Setup of Storage Cruiser's Agent" in the ETERNUS SF Installation and Setup Guide for this version for details. Restore the Storage Cruiser's agent settings information that was backed up in step 1. Copy the file of No.

  • Page 110: Chapter 7 Upgrade From Storage Cruiser Version 16.X

    Chapter 7 Upgrade from Storage Cruiser Version 16.x To upgrade Storage Cruiser Version 16.x to this version, install the ETERNUS SF Manager. Point In the version level of the Storage Cruiser, there are conditions for the combination of manager and agent. Upgrade your version, in order to fulfill the combination that is described in "Notes on Combining Different Versions"...

  • Page 111: Performing Upgrade

    When using the ETERNUS SF SNMP Trap Service, stop the SNMP Trap function. With the Windows services screen, stop the ETERNUS SF SNMP Trap Service. Note In an environment where other software using SNMP Traps such as Systemwalker Centric Manager and ServerView Resource Orchestrator coexists on a target server, if you stop the ETERNUS SF SNMP Trap Service, other software using SNMP Traps cannot perform the fault monitoring.

  • Page 112: Upgrading On Clustered Systems

    If the Storage Cruiser's agent has been installed, start the service of the Storage Cruiser's agent. Refer to "Starting and Stopping Agent" in the ETERNUS SF Storage Cruiser Operation Guide for information on how to start the service. Execute the following batch to restart the ETERNUS SF Manager services. $INS_DIR\Common\bin\Start_ESFservice.bat $INS_DIR means "Program Directory"...
  • Page 113 The available capacity of the specified disk (C:) is insufficient. Please execute it again after increasing the disk area. Check that the ETERNUS SF Manager services are stopped on the secondary node. If not stopped, use the Failover Cluster Manager on the secondary node to stop the transactions of ETERNUS SF Manager. When using the ETERNUS SF SNMP Trap Service, on the secondary node, stop the SNMP Trap function.

  • Page 114: Performing Upgrade (Primary Node)

    In all of the nodes in which the Storage Cruiser's agent has been installed, stop the service of the Storage Cruiser's agent. Refer to "Starting and Stopping Agent" in the ETERNUS SF Storage Cruiser Operation Guide for information on how to stop the service. Stop the local transactions on all the nodes, perform the following procedure: With the Windows services screen, start the AdvancedCopy Manager COM Service.

  • Page 115: Performing Upgrade (Secondary Node)

    For srcDir, specify the directory on the local disk from which to set the link. For dstDir, specify the directory on the shared disk to which the link is to be set. Refer to "C.3 Procedures for Upgrade Installation of Manager Feature of Express / Storage Cruiser / AdvancedCopy Manager Version 16.x (for Windows)"...
  • Page 116 Descriptive Contents of Version Information Upgrade Patterns Before After Version 16.1 to 16.6 Version=V16.1 Version 16.2 to 16.6 Version=V16.2 Version 16.3 to 16.6 Version=V16.3 Version 16.4 to 16.6 Version=V16.4 Version 16.5 to 16.6 Version=V16.5 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 Managed Server transactions shared data, on the primary node for a target service.

  • Page 117: Tasks To Be Performed After Upgrade (Secondary Node)

    Trap XML definition file. For the contents of the customization, refer to the SNMP Trap XML definition file which was saved to the arbitrary location. Directory of Location of Customization Definition files $ENV_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\snmpth $ENV_DIR is the "Environment Directory" of when ETERNUS SF Manager has been installed to a new environment. If the polling service setting file is customized in the environment of the previous version, it is necessary to customize this version as well.

  • Page 118: Resuming Operation

    If Managed Server transactions coexist in a clustered system, start the Managed Server transactions in the primary node for a target transaction. Use the Failover Cluster Manager to start the Managed Server transactions. If multiple Managed Server transactions exist, apply this procedure for each Managed Server transaction. In all of the nodes in which the Storage Cruiser's agent has been installed, start the service of the Storage Cruiser's agent.

  • Page 119: Upgrading Storage Cruiser's Manager (For Solaris, Linux)

    Refer to "Reload ETERNUS Disk Storage System Configuration Information" in the ETERNUS SF Web Console Guide for this version for information on reloading the configuration information. Upgrading Performance Management When using the performance management function of NAS volume and NAS system after the upgrade, it is required to restart the performance management function.

  • Page 120: Performing Upgrade

    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.
  • Page 121 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".

  • Page 122: Upgrading On Clustered Systems

    As required, perform the SNMP Trap configuration (for Linux only). Only when the FJSVswstt package is installed using the procedure described in the step 4 of "7.2.1.1 Preparing for Upgrade", perform the operation described in the following section in "Setup of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for this version.

  • Page 123: Performing Upgrade (Primary Node)

    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.

  • Page 124: Performing Upgrade (Secondary Node)

    Unmount the shared disk for shared data of ETERNUS SF Manager. 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.2.3 Performing Upgrade (Secondary Node) Mount the shared disk for shared data of ETERNUS SF Manager.
  • Page 125 [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"...

  • Page 126: Tasks To Be Performed After Upgrade (Secondary Node)

    Descriptive Contents of Version Information Upgrade Patterns Before After Version 16.4 to 16.6 Version=V16.4 Version 16.5 to 16.6 Version=V16.5 Note Do not change anything other than the version information. Recover the activation suspension script of Management Server tasks saved during "7.2.2.1 Preparing for Upgrade".
  • Page 127 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. Confirm that other products are not utilizing the Symfoware.

  • Page 128: Starting Managed Server Transactions

    Perform the kernel parameter tuning. Refer to "Before Installation" in "Installation of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for this version for information on tuning. Check the cluster application (transaction) is stopped. If not stopped, refer to the relevant cluster software manuals for information on stopping it. 7.2.2.6 Starting Managed Server Transactions After performing...

  • Page 129: Upgrading Storage Cruiser's Agent (For Windows)

    On the global navigation tab, click Storage. The registered ETERNUS Disk storage systems are displayed in the Main pane. On the Main pane, check the target ETERNUS Disk storage system checkbox. On the Action pane, click Reload Conf. under Storage. Refer to "Reload ETERNUS Disk Storage System Configuration Information"...

  • Page 130: Backing Up Operational Environment Of Previous Version

    7.3.1.1 Backing Up Operational Environment of Previous Version For recovery in case the upgrade fails, perform a backup of the operating environment of the previous version of the Storage Cruiser's agent. The procedure is shown below: Log on to the server using Administrator privileges. Insert the DVD-ROM "ETERNUS SF SC/ACM/Express Mediapack (Agent Program and Manual)"...
  • Page 131 The following window is displayed. Click Storage Cruiser installation. The following dialog box is displayed. Click Yes. - 107 -...

  • Page 132: Upgrade With Silent Installation Tasks

    When the upgrade is completed, the following installation wizard page is displayed. The upgrade process is completed. Click Finish. Eject the DVDROM. The Storage Cruiser's agent upgrade is completed. Refer to "7.3.4 Tasks to Be Performed After Upgrade" to set up the Storage Cruiser's agent. Point If the upgrade was terminated abnormally, refer to "11.3.3 In Case of Problem During Upgrade of Storage Cruiser's Agent (for...

  • Page 133: Confirming Results Of Upgrade With Silent Installation

    Execute the following silent installation command. For installLogFile, specify the file in which to output installation log with an absolute path. It is optional to specify for installLogFile. dvdromDrive:\Agent_windows\Storage_Cruiser\windows_x86\scagtsilentinstall.bat [-l <installLogFile>] Point If nothing is specified for installLogFile, an install log file named " scagtsilentinstall.log" is created in the working directory specified by the environment variable TEMP.
  • Page 134 Point When performing an upgrade of Storage Cruiser's manager at the same time, perform the following procedures after completing the upgrade of Storage Cruiser's manager. Restore of the Storage Cruiser's Agent Configured Information Where there has been customization of "Correlation.ini Parameter" of the ETERNUS SF Storage Cruiser Operation Guide, restore the Storage Cruiser Agent Settings information.

  • Page 135: Upgrading Storage Cruiser's Agent (For Solaris)

    Point Once normal operation has been confirmed after the upgrade of the Storage Cruiser's agent, the backup data in the backup destination directory created in step 5 of "7.3.1.1 Backing Up Operational Environment of Previous Version" maybe deleted. 7.4 Upgrading Storage Cruiser's Agent (for Solaris) Point For Performing Upgrade in Single-user Mode Check that the local file system is already mounted before the installation.

  • Page 136: Performing Upgrade

    The following message is displayed. To continue, enter "y". To discontinue, enter "n" or "q". ETERNUS SF Storage Cruiser 16.6 Copyright FUJITSU LIMITED 2013-2017 This program will upgrade "ETERNUS SF Storage Cruiser" Agent on your system. Do you want to continue the upgrade of this package? [y,n,?,q] If "y"...

  • Page 137: Upgrade With Silent Installation Tasks

    The Storage Cruiser's agent upgrade is completed. Refer to "7.4.4 Tasks to Be Performed After Upgrade" to set up the Storage Cruiser's agent. Point If the upgrade was terminated abnormally, refer to "11.3.4 In Case of Problem During Upgrade of Storage Cruiser's Agent (for Solaris, Linux)"...

  • Page 138: Tasks To Be Performed After Upgrade

    The installation result can be viewed in the install log file, too. Open the install log file to see "ResultCode" in the ResponseResult section. In "ResultCode" is written the return value from the silent installation command. Point If the upgrade was terminated abnormally, refer to "11.3.4 In Case of Problem During Upgrade of Storage Cruiser's Agent (for Solaris, Linux)"...

  • Page 139: Performing Upgrade

    The following message is displayed. To continue, enter "y". To discontinue, enter "n" or "q". ETERNUS SF Storage Cruiser 16.6 Copyright FUJITSU LIMITED 2013-2017 This program will upgrade "ETERNUS SF Storage Cruiser" Agent on your system. Do you want to continue the upgrade of this package? [y,n,?,q] If "y"...

  • Page 140: Upgrade With Silent Installation Tasks

    Eject the DVD-ROM. # cd / # umount dvdromMountPoint The Storage Cruiser's agent upgrade is completed. Refer to "7.5.4 Tasks to Be Performed After Upgrade" to set up the Storage Cruiser's agent. 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.

  • Page 141: Confirming Results Of Upgrade With Silent Installation

    During an update, it is not possible to specify an installation parameter file for the command. In the case that a file has been specified, the command terminates in an error. 7.5.3.2 Confirming Results of Upgrade with Silent Installation Check the return value from the silent installation command. If necessary, check the install log file. However, if the return value from the silent installation command is 3 or 9, an install log file is not created.
  • Page 142 Install this version of the Storage Cruiser's agent. Refer to "Installation of Storage Cruiser's Agent" in the ETERNUS SF Installation and Setup Guide for this version for details. Set up the Storage Cruiser's agent. Refer to "Setup of Storage Cruiser's Agent" in the ETERNUS SF Installation and Setup Guide for this version for details. Restore the Storage Cruiser's agent settings information that was backed up in step 1.

  • Page 143: Chapter 8 Upgrade From Advancedcopy Manager Version 14.X

    Chapter 8 Upgrade from AdvancedCopy Manager Version 14.x If performing an upgrade to a system environment using Agent-based operation model, perform the upgrade in the following sequence. AdvancedCopy Manager's manager AdvancedCopy Manager's agent Point For AdvancedCopy Manager programs, the Upgrade Installation can be performed for the AdvancedCopy Manager's manager and AdvancedCopy Manager Copy Control Module.

  • Page 144: Checking For Available Disk Space

    Server Type Reference Storage Management Server Windows Perform the steps of "A.1 Backing Up Repository Data (for which also serves as a Storage Windows)", and then perform the steps of "A.3 Backing Up Server Management Information (for Windows)". Solaris, Perform the steps of "A.2 Backing Up Repository Data (for Solaris, Linux Linux)", and then perform the steps of...

  • Page 145: Tuning Kernel Parameters (For Solaris, Linux)

    Refer to "Before Installation" in "Installation of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for this version for details. 8.1.1.5 Tuning Kernel Parameters (for Solaris, Linux) 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.

  • Page 146: Performing Upgrade (For Solaris, Linux)

    When requested to restart the computer, click No. If Yes is clicked, the upgrade is interrupted. When re-executing the installation after a restart of the computer, the installation is treated as new one. When the uninstallation completes successfully, the Uninstallation was completed successfully page may be displayed. Although the instruction on the page indicates the deletion of files and folders, do not delete files and folders when performing the upgrade.

  • Page 147: Importing Configuration Information

    Restore the AdvancedCopy Manager operational environment. Refer to the following table to restore the operational environment. For the operational environment restore, start a new window for command execution, and then perform the procedure on the window. Server Type Reference Management Server Windows "A.9 Restoring Repository Data (for Windows)"...

  • Page 148: Setting Up User Account

    8.1.4.3 Setting Up User Account Set up a user account in order to use the ETERNUS SF Manager functions. Refer to "Setting Up User Account" in the ETERNUS SF Installation and Setup Guide for this version for information on setup. 8.1.4.4 Setting Up Web Console If firewalls are used between the PC on which Web Console is launched and the Management Server, perform firewall settings to allow...

  • Page 149: Uninstalling Symfoware

    Admin User : **** Access Volume : X: Remove all of the registered ETERNUS Disk storage system by executing the acarray remove command. C:\>C:\ETERNUS_SF\CCM\bin\acarray remove -a ET01 Successful completion. Re-register all of the ETERNUS Disk storage systems that were removed in step 3 by executing the acarray add command. C:\>C:\ETERNUS_SF\CCM\bin\acarray add -a ET01 -ip 192.0.2.10 -user **** -password **** -path Successful completion.

  • Page 150: Resuming Operation

    [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"...

  • Page 151: Backing Up Management Information

    8.2.2 Backing Up Management Information Refer to the following sections to back up the management information on the Managed Server. OS Type of Managed Server Reference Windows A.3 Backing Up Management Information (for Windows) Solaris, A.4 Backing Up Management Information (for Solaris, Linux) Linux HP-UX, A.5 Backing Up Management Information (for HP-UX, AIX)

  • Page 152: Installing This Version

    8.2.5 Installing This Version Install the AdvancedCopy Manager's agent of this version, and setup the operating environment. About Installation For non-clustered systems: Refer to "Installation of AdvancedCopy Manager's Agent" in the ETERNUS SF Installation and Setup Guide for this version to install the AdvancedCopy Manager's agent.

  • Page 153: Changing Server Information

    Refer to "Command References" in the ETERNUS SF AdvancedCopy Manager Operation Guide relevant to the OS of the Management Server for information on the command. 8.2.7 Changing Server Information To ensure data consistency, execute Web Console or the stgxfwcmmodsrv command to change the server information. The stgxfwcmmodsrv command must be executed on the Management Server.

  • Page 154: Updating Version Information

    8.2.10 Updating Version Information If not using cluster operation, and moreover, if the restoration of repository data has already been performed with the restoration of the replication management list, execute Web Console or the stgxfwcmmodsrv command to update the version information for the Managed Server.

  • Page 155: Backing Up Environment Setting Files

    Estimating the database size estimation is necessary. Using the information provided above, select the appropriate program to install. 8.3.1.2 Backing Up Environment Setting Files Back up the operational environment for the previous version. Refer to "A.6 Backing Up Environment Setting Files"...

  • Page 156: Performing Upgrade (For Windows)

    Refer to "Before Installation" in "Installation of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for this version for details. 8.3.2 Performing Upgrade (for Windows) Refer to "C.1 Procedures for Upgrade Installation of Manager Feature of Express / Storage Cruiser / AdvancedCopy Manager Version 14.x and 15.x (for Windows)"...

  • Page 157: Reconfiguring Device Information

    8.3.4.2 Reconfiguring Device Information The following procedure is required to reconfigure the ETERNUS Disk storage system information. Refer to "Command References" in the ETERNUS SF AdvancedCopy Manager Operation Guide for Copy Control Module for this version for information on the commands. Confirm the registered ETERNUS Disk storage system by executing the acarray list command.

  • Page 158: Uninstalling Symfoware

    8.3.4.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. For Windows Uninstall Symfoware from the Add or Remove Programs or Programs and Features page.

  • Page 159: Resuming Operation

    When FSUNiconv package is installed, delete it (only in the Solaris environment). Delete after confirming that this package function is used only by ETERNUS SF Manager. # pkgrm FSUNiconv 8.3.5 Resuming Operation When the tasks described above have been performed, the upgrade of AdvancedCopy Manager Copy Control Module is complete. The task below is the reconstruction of the managed environment in AdvancedCopy Manager.

  • Page 160: Chapter 9 Upgrade From Advancedcopy Manager Version 15.X

    Chapter 9 Upgrade from AdvancedCopy Manager Version 15.x To upgrade AdvancedCopy Manager's manager to this version, install the ETERNUS SF Manager. If performing an upgrade to a system environment using Agent-based operation model, perform the upgrade in the following sequence: AdvancedCopy Manager's manager AdvancedCopy Manager's agent Point...
  • Page 161 Stop the ETERNUS SF Manager service. Execute the following batch file. $INS_DIR\Common\bin\Stop_ESFservice.bat The $INS_DIR is the program directory specified at the ETERNUS SF Manager installation. Implement backup of the previous version. Execute the following batch file. For backupDir, specify the directory in which to store the backup data with an absolute path. In the tmpDir, specify a directory in which to temporarily place the files related to the performance management function of Storage Cruiser with an absolute path.
  • Page 162 Refer to "Before Installation" in "Installation of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for this version for details. 9.1.1.1.5 Preparing for Uninstallation Refer to "A.7 Unsetting Up Database" to unsetup the repository database of the previous version: 9.1.1.2 Performing Upgrade Refer to...
  • Page 163 If the following related software was being used with the previous version, it is necessary to update these to a version that supports this version. ETERNUS VASA Provider Fujitsu ETERNUS Storage Systems Monitoring Pack Note If operating Web Console from the same web browser as before the upgrade, delete the web browser's cache prior to operation.
  • Page 164 Point It is recommended that you back up the system before starting the upgrade. If a failure occurs during the upgrade, you cannot restore the environment to the pre-installation status (rollback). When returning back to the state before installation of the upgrade, recover (restore) the system from the backup. Log on to the server using Administrator privileges.
  • Page 165 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. dvdromDrive:\Manager_windows\vuptools\esfpreinst_cluster.bat backupDir [tmpDir] -primary When the backup fails, after confirming the output error message and removing the cause of the failure, execute the batch file again.
  • Page 166 On the secondary node, perform a backup of the operating environment of the previous version of the AdvancedCopy Manager's manager. The capacity required for performing this backup is 10 MB. Log on to the server using Administrator privileges. If already logged on as the Administrator privileges, this step is unnecessary. Insert the DVD-ROM "ETERNUS SF SC/ACM/Express Mediapack for Windows (Manager Program) (1/2)"...

  • Page 167: Performing Upgrade (Primary Node)

    Refer to "Operating Environment of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for this version for information on the incompatible software. Performing the cluster unsetup Refer to "Uninstallation of ETERNUS SF Manager" in "Deletion of Cluster Environment for Management Server Transactions" in the ETERNUS SF Storage Cruiser Installation Guide for the relevant previous version to delete the service resources, the cluster resources and unnecessary resources.
  • Page 168 If Managed Server transactions coexist in the clustered system, edit the environment setting files for AdvancedCopy Manager on the shared disk for Managed Server transactions shared data. On the primary node for target transactions, edit the following files: <Drive of shared disk for shared data of Managed Server transactions>:\etc\opt\swstorage\clsetup.ini <Drive of shared disk for shared data of Managed Server transactions>:\etc\opt\swstorage\etc\swstg.ini Change the version information within each file, as follows: Descriptive Contents of Version Information...

  • Page 169: Tasks To Be Performed After Upgrade (Secondary Node)

    It is necessary to reinstall a version of the ETERNUS VASA Provider that supports this version. If the Fujitsu ETERNUS Storage Systems Monitoring Pack was being used with the previous version It is necessary to reinstall a version of the Fujitsu ETERNUS Storage Systems Monitoring Pack that supports this version. 9.1.2.5 Tasks to Be Performed After Upgrade (Secondary Node) The tasks below need to be performed on the secondary node.
  • Page 170 It is necessary to reinstall a version of the ETERNUS VASA Provider that supports this version. If the Fujitsu ETERNUS Storage Systems Monitoring Pack was being used with the previous version It is necessary to reinstall a version of the Fujitsu ETERNUS Storage Systems Monitoring Pack that supports this version. 9.1.2.6...
  • Page 171 If Managed Server transactions coexist in a clustered system, start the Managed Server transactions in the primary node for a target transaction. Use the Failover Cluster Manager to start the Managed Server transactions. If multiple Managed Server transactions exist, apply this procedure for each Managed Server transaction. Start the local transactions on all the nodes, perform the following procedure: Select Control Panel >...
  • Page 172 Cruiser with an absolute path. When the performance management function is not being used, it is unnecessary to specify a directory for the tmpDir. # /mnt/dvd/Manager_unix/vuptools/esfpreinst.sh backupDir [tmpDir] When the backup fails, after confirming the output error message and removing the cause of the failure, execute the command again.
  • Page 173 Refer to "Before Installation" in "Installation of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for this version for information on tuning. 9.2.1.1.6 Confirming Port Number for Communication Service Therefore, ensure the new ports are available before starting the upgrade. Refer to "Before Installation"...
  • Page 174 When the restore fails, after confirming the output error message and removing the cause of the failure, execute the command again. Point Spaces and the characters " / ` * ? \ $ [ ] , % ! { } are not supported for directory names. The number of characters in a directory name must be up to 220.
  • Page 175 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".
  • Page 176 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 it (transaction). Stop the cluster application (transaction) on the primary node.
  • Page 177 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. Change to a directory other than the DVD-ROM.
  • Page 178 Refer to "Before Installation" in "Installation of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for this version for information on port numbers. Perform the kernel parameter tuning on the primary node. Therefore, perform the necessary kernel parameter tuning before starting the upgrade. Refer to "Before Installation"...
  • Page 179 Unmount the DVD-ROM. Example: # umount /mnt/dvd Eject the DVD-ROM. 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".
  • Page 180 Note Do not uninstall the ETERNUS SF Manager. In cases when Managed Server transactions coexist, do not release the configurations of these Managed Server transactions. 9.2.2.2 Performing Upgrade (Primary Node) Refer to "C.2 Procedures for Upgrade Installation of Manager Feature of Express / Storage Cruiser / AdvancedCopy Manager Version 14.x and 15.x (for Solaris, Linux)"...
  • Page 181 Descriptive Contents of Version Information Upgrade Patterns Before After Version 15.0B to 16.6 Version=V15.0 Version 15.1 to 16.6 Version=V15.1 Version=V16.6 Version 15.2 to 16.6 Version=V15.2 Version 15.3 to 16.6 Version=V15.3 Note Do not change anything other than the version information. Restore the operation environment of the previous version of the AdvancedCopy Manager's manager.
  • Page 182 In cases when Managed Server transactions coexist in the cluster system, change the server information of the Managed Server transactions. To ensure data consistency, use the stgxfwcmmodsrv command to change the server information. When executing the stgxfwcmmodsrv command, specify the Management Server name for the -n option. /opt/FJSVswstf/bin/stgxfwcmmodsrv -n serverName This operation should be performed on the primary node for Management Server transactions.
  • Page 183 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 ",".
  • Page 184 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. # /mnt/dvd/Manager_unix/vuptools/esfpostinst_cluster.sh backupDir [tmpDir] -secondary When the restore fails, after confirming the output error message and removing the cause of the failure, execute the command again.
  • Page 185 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"...
  • Page 186 9.3 Upgrading AdvancedCopy Manager's Agent (for Windows) This section describes the upgrade procedure for the AdvancedCopy Manager's agent for Windows Server 2008 or later. 9.3.1 Upgrading on Non-clustered Systems 9.3.1.1 Preparing for Upgrade Log on to the server using Administrator privileges. If the Storage Cruiser's agent has been installed, stop the service of the Storage Cruiser's agent.
  • Page 187 dvdromDrive:\Agent_windows\AdvancedCopy_Manager\agent\windows_x64\esfacmapreinst.bat backupDir When the backup fails, after confirming the output error message and removing the cause of the failure, execute the batch file again. Point The characters " | : * ? / . < > % & ^ ; ! are not supported for directory names. If the directory name contains any spaces, they should be surrounded by double quote characters.
  • Page 188 The following window is displayed. For the Upgrade Installation, this window is not used. Click Exit. Start the following installation wizard corresponding to the architecture of AdvancedCopy Manager's agent checked in preparing for the upgrade: For 32 bit version: dvdromDrive:\Agent_windows\AdvancedCopy_Manager\agent\windows_x86\setup.exe For 64 bit version: dvdromDrive:\Agent_windows\AdvancedCopy_Manager\agent\windows_x64\setup.exe The following steps are explained using screen examples when the installation wizard of the 32 bit version agent is started.
  • Page 189 The installation wizard page is displayed. Click Next. Read the terms and conditions of the License Agreement page. If the conditions are agreeable, click Yes. - 165 -...
  • Page 190 Check the settings information in the Start Copying Files page, and then click Next. Copying of the program is started. The following installation wizard page is displayed. The upgrade process is completed. Click Finish. Eject the DVD-ROM. - 166 -...
  • Page 191 9.3.1.3 Tasks to Be Performed After Upgrade The tasks below need to be performed. Note that in these tasks, in addition to operations with the Managed Server, there are operations to execute from the Management Server and Web Console. If the Storage Cruiser's agent has been installed, start the service of the Storage Cruiser's agent. Refer to "Starting and Stopping Agent"...
  • Page 192 9.3.2 Upgrading on Clustered Systems 9.3.2.1 Preparing for Upgrade Log on to the server using Administrator privileges. Check that Managed Server transactions are stopped on the secondary node. If not stopped, use the Failover Cluster Manager to stop Managed Server transactions on the secondary node. If multiple Managed Server transactions exist, perform this procedure on each secondary node for Managed Server transactions.
  • Page 193 Start the command prompt with "Run as administrator". Implement backup of the previous version. Execute the following batch file. For backupDir, specify the directory in which to store the backup data with an absolute path. [When using the 32 bit version Agent] dvdromDrive:\Agent_windows\AdvancedCopy_Manager\agent\windows_x86\esfacmapreinst.bat backupDir [When using the 64 bit version Agent]...
  • Page 194 The following window is displayed. For the Upgrade Installation, this window is not used. Click Exit. Start the following installation wizard corresponding to the architecture of AdvancedCopy Manager's agent checked in preparing for the upgrade: For 32 bit version: dvdromDrive:\Agent_windows\AdvancedCopy_Manager\agent\windows_x86\setup.exe For 64 bit version: dvdromDrive:\Agent_windows\AdvancedCopy_Manager\agent\windows_x64\setup.exe The following steps are explained using screen examples when the installation wizard of the 32 bit version agent is started.
  • Page 195 The following installation wizard page is displayed. Click Next. Read the terms and conditions of the License Agreement page. If the conditions are agreeable, click Yes. - 171 -...
  • Page 196 Check the settings information in the Start Copying Files page, and then click Next. Copying of the program is started. The following installation wizard page is displayed. The upgrade process is completed. Click Finish. Eject the DVD-ROM. 9.3.2.3 Tasks to Be Performed After Upgrade (Primary Node) If multiple Managed Server transactions exist, use this procedure in each primary node for Managed Server transaction.
  • Page 197 Edit the following environment setting files for Managed Server transaction on the shared disk for shared data: <Drive of shared disk for shared data of Managed Server transaction>:\etc\opt\swstorage\clsetup.ini <Drive of shared disk for shared data of Managed Server transaction>:\etc\opt\swstorage\etc\swstg.ini Change the version information within each file, as follows: Descriptive Contents of Version Information Upgrade Patterns Before...
  • Page 198 When the Management Server OS is Windows programDir\ACM\bin\stgxfwcmmodsrv -n serverName When the Management Server OS is Solaris or Linux /opt/FJSVswstf/bin/stgxfwcmmodsrv -n serverName If multiple Managed Server transactions exist, perform this procedure for each Managed Server transaction. In addition, if there is any node that is running local transactions, perform this procedure on the relevant node. Note For changing the server information, start a new window for command execution, and then perform the procedure on the window.
  • Page 199 Execute the following command to stop the daemon of AdvancedCopy Manager's agent. # /opt/swstorage/bin/stopacm Implement backup of the previous version. For recovery in case the upgrade fails, perform a backup of the operating environment of the previous version of the AdvancedCopy Manager's agent.
  • Page 200 [When using the RHEL5 x64 Edition Agent] # dvdromMountPoint/Agent_unix/AdvancedCopy_Manager/rhel5_x64/esfacmapreinst.sh backupDir [When using the RHEL6 Agent] # dvdromMountPoint/Agent_unix/AdvancedCopy_Manager/rhel6_x86/esfacmapreinst.sh backupDir [When using the Solaris Agent] # dvdromMountPoint/Agent_unix/AdvancedCopy_Manager/Solaris/esfacmapreinst.sh backupDir When the backup fails, after confirming the output error message and removing the cause of the failure, execute the shell script again.
  • Page 201 +-----------------------------------------------------------+ ETERNUS SF AdvancedCopy Manager 16.6 Copyright FUJITSU LIMITED 2013-2017 +-----------------------------------------------------------+ Welcome to Setup. This program will install "AdvancedCopy Manager" on your system. A confirmation message is displayed before uninstalling the previous version. To uninstall the previous version and proceed with the new installation, enter "y".
  • Page 202 Refer to "Command References" in the ETERNUS SF AdvancedCopy Manager Operation Guide relevant to the OS of the Management Server for information on the command. Perform the following operations with Web Console to reload the server information. On the global navigation tab, click Server. The registered server list is displayed in the Main pane.
  • Page 203 On the primary node and the secondary node, implement backup of the previous version. In cases when there are multiple Managed Server transactions, in each primary node of the Managed Server transactions, switch the shared disk for the shared data of the Managed Server transactions online. Information The capacity required for performing the backup is the total value of the following: Fixed configuration directory and Modifying configuration directory of "For Solaris environment"...
  • Page 204 # dvdromMountPoint/Agent_unix/AdvancedCopy_Manager/rhel5_x86/esfacmapreinst.sh backupDir [When using the RHEL5 x64 Edition Agent] # dvdromMountPoint/Agent_unix/AdvancedCopy_Manager/rhel5_x64/esfacmapreinst.sh backupDir [When using the RHEL6 Agent] # dvdromMountPoint/Agent_unix/AdvancedCopy_Manager/rhel6_x86/esfacmapreinst.sh backupDir [When using the Solaris Agent] # dvdromMountPoint/Agent_unix/AdvancedCopy_Manager/Solaris/esfacmapreinst.sh backupDir When the backup fails, after confirming the output error message and removing the cause of the failure, execute the shell script again.
  • Page 205 Installer is preparing for installation... +-----------------------------------------------------------+ ETERNUS SF AdvancedCopy Manager 16.6 Copyright FUJITSU LIMITED 2013-2017 +-----------------------------------------------------------+ Welcome to Setup. This program will install "AdvancedCopy Manager" on your system. A confirmation message is displayed before uninstalling the previous version. To uninstall the previous version and proceed with the new installation, enter "y".
  • Page 206 Descriptive Contents of Version Information Upgrade Patterns Before After Version 15.0B to 16.6 Version=V15.0 Version 15.1 to 16.6 Version=V15.1 Version=V16.6 Version 15.2 to 16.6 Version=V15.2 Version 15.3 to 16.6 Version=V15.3 Note Do not change anything other than the version information. For the ETERNUS SF Manager Version 15.0B installed environment, perform the following procedure.
  • Page 207 Perform the following command to start the local transactions on all the nodes. # /opt/swstorage/bin/startacm To ensure data consistency, with the Management Server, execute the stgxfwcmmodsrv command to change the server information. When executing the stgxfwcmmodsrv command, specify the Managed Server name for the -n option. When the Management Server OS is Windows programDir\ACM\bin\stgxfwcmmodsrv -n serverName When the Management Server OS is Solaris or Linux...
  • Page 208 9.5.7 Restoring Management Information 9.5.8 Updating Version Information 9.5.1 Backing Up Repository Data Refer to the following sections to back up the repository data on the Management Server (only when the Managed Server is operated in a clustered system). OS Type of Management Server Reference Windows A.1 Backing Up Repository Data (for Windows)
  • Page 209 Setting Up Operating Environment For non-clustered systems: Refer to "Setup of AdvancedCopy Manager's Agent" in the ETERNUS SF Installation and Setup Guide for this version to setup the AdvancedCopy Manager's agent. Afterwards, start the AdvancedCopy Manager's agent on the Managed Server. Refer to "Starting and Stopping Daemons" or "Starting and Stopping Services"...
  • Page 210 Refer to "Command References" in the ETERNUS SF AdvancedCopy Manager Operation Guide relevant to the OS of the Management Server for information on the command. 9.5.7 Restoring Management Information Refer to "A.13 Restoring Management Information (for HP-UX, AIX)" to restore the management information on the Managed Server. 9.5.8 Updating Version Information If not using clustered systems, and moreover, if the restoration of repository data has already been performed with the restoration of the replication management list, execute Web Console or the stgxfwcmmodsrv command to update the version information for the...
  • Page 211 9.6.1 Upgrading on Non-clustered Systems 9.6.1.1 Preparing for Upgrade Point It is recommended that you back up the system before starting the upgrade. If a failure occurs during the upgrade, you cannot restore the environment to the pre-installation status (rollback). When returning back to the state before installation of the upgrade, recover (restore) the system from the backup.
  • Page 212 For installing the AdvancedCopy Manager Copy Control Module: "Operating Environment of AdvancedCopy Manager CCM" Required Disk Space for Previous Version The space required to install previous version of the ETERNUS SF Manager or the AdvancedCopy Manager Copy Control Module. Refer to the following locations in the ETERNUS SF Installation and Setup Guide for the relevant previous version for information on the required disk space.
  • Page 213 9.6.2 Upgrading on Clustered Systems The following values are used in the description: Value Description $INS_DIR "Program Directory" specified at the AdvancedCopy Manager CCM installation. 9.6.2.1 Preparing for Upgrade Point It is recommended that you back up the system before starting the upgrade. If a failure occurs during the upgrade, you cannot restore the environment to the pre-installation status (rollback).
  • Page 214 Required Disk Space for New Version The space required to install this version of the ETERNUS SF Manager or AdvancedCopy Manager Copy Control Module. Refer to the following locations in the ETERNUS SF Installation and Setup Guide for this version for information on the required disk space.
  • Page 215 For using the AdvancedCopy Manager Copy Control Module in ETERNUS SF Manager: "Operating Environment of ETERNUS SF Manager" For installing the AdvancedCopy Manager Copy Control Module: "Operating Environment of AdvancedCopy Manager CCM" Required Disk Space for Previous Version The space required to install previous version of the ETERNUS SF Manager or AdvancedCopy Manager Copy Control Module. Refer to the following locations in the ETERNUS SF Installation and Setup Guide for the relevant previous version for information on the required disk space.
  • Page 216 Stop the CCM Server transactions Use the Failover Cluster Manager to stop the transactions to which the AdvancedCopy Manager CCM. However, the shared disk for shared data of the AdvancedCopy Manager CCM must be online. Restore the operation environment of the previous version of the AdvancedCopy Manager Copy Control Module. Note that if step a and step b have already been performed, perform from step c.

  • Page 217: Start Ccm Server Transactions

    Eject the DVD-ROM. 9.6.2.6 Start CCM Server Transactions Start the CCM Server transactions. Use the Failover Cluster Manager on the primary node to start the transactions of AdvancedCopy Manager CCM. Point Once normal operation has been confirmed after the upgrade, the backup data in the backup destination directory created in step 4- c and step 6-c of "9.6.2.1 Preparing for Upgrade"...
  • Page 218 Point Spaces and the characters " / ` * ? \ $ [ ] , % ! { } are not supported for directory name. The number of characters in a directory name must be up to 220. 9.7.1.1.2 Checking for Available Disk Space Ensure that there is enough available disk space on the server where the upgrade is performed.
  • Page 219 Mount the DVD-ROM. Example: # mount /mnt/dvd Implement restoration of the previous version. Execute the following command. For backupDir, specify the directory in which the backup data is stored with an absolute path. # /mnt/dvd/Manager_unix/vuptools/esfccmpostinst.sh backupDir When the restore fails, after confirming the output error message and removing the cause of the failure, execute the command again.
  • Page 220 Insert the DVD-ROM "ETERNUS SF SC/ACM Mediapack for Solaris (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.
  • Page 221 When installing and using the AdvancedCopy Manager Copy Control Module Program "Operating environment of the AdvancedCopy Manager CCM" On the secondary node, perform a backup of the operating environment of the previous version of the AdvancedCopy Manager Copy Control Module. The capacity required for performing this backup is 10 MB.
  • Page 222 Required Disk Space for Previous Version The space required to install previous version of the ETERNUS SF Manager or AdvancedCopy Manager Copy Control Module. Refer to the following locations in the ETERNUS SF Installation and Setup Guide for the relevant previous version for information on the required disk space.
  • Page 223 Restore the operation environment of the previous version of the AdvancedCopy Manager Copy Control Module. Note that if step a through step c have already been performed, perform from step d. Login to the server on which to perform the tasks. Perform operations after logging in with root (superuser). Insert the DVD-ROM "ETERNUS SF SC/ACM Mediapack for Solaris (Manager Program) (2/2)"...
  • Page 224 Implement restoration of the previous version. Execute the following batch file. For backupDir, specify the directory in which the backup data is stored with an absolute path. # /mnt/dvd/Manager_unix/vuptools/esfccmpostinst_cluster.sh backupDir -secondary When the restore fails, after confirming the output error message and removing the cause of the failure, execute the batch again Point Spaces and the characters "...
  • Page 225 Chapter 10 Upgrade from AdvancedCopy Manager Version 16.x To upgrade AdvancedCopy Manager's manager to this version, install the ETERNUS SF Manager. If performing an upgrade to a system environment using Agent-based operation model, perform the upgrade in the following sequence. AdvancedCopy Manager's manager AdvancedCopy Manager's agent For the upgrade, there is a method where the upgrade is performed in an interactive format and a method where the upgrade is...
  • Page 226 Execute the following batch to stop the ETERNUS SF Manager services. $INS_DIR\Common\bin\Stop_ESFservice.bat $INS_DIR means "Program Directory" specified at the ETERNUS SF Manager installation. When using the ETERNUS VASA Provider, stop the Provider function. With the Windows services screen, stop the ETERNUS Information Provider. When using the ETERNUS SF SNMP Trap Service, stop the SNMP Trap function.
  • Page 227 Point When ETERNUS SF Manager has been recovered to normal state by performing the task described in "11.3.1 In Case of Problem During Upgrade of ETERNUS SF Manager (for Windows)", to ensure data consistency, execute the stgxfwcmmodsrv command to perform the server information change processing.
  • Page 228 When using the ETERNUS VASA Provider, on the secondary node, confirm that the ETERNUS VASA Provider service has been stopped. If not stopped, use the Failover Cluster Manager on the secondary node to stop the transactions of the ETERNUS VASA Provider. Ensure that there is enough available disk space (400 MB) on the server where the upgrade is performed on the primary node.
  • Page 229 Make a copy on any directory that is other than the directory which is the destination of the installation of AdvancedCopy Manager CCM. The saved file is used in tasks after the upgrade. Recover the original environment configurations file (sys.properties) of the AdvancedCopy Manager CCM. Overwrite the original environment configurations file onto the file of the copying destination.
  • Page 230 <Drive of shared disk for shared data of ETERNUS SF Manager>:\etc\opt\swstorage\clsetup.ini <Drive of shared disk for shared data of ETERNUS SF Manager >:\etc\opt\swstorage\etc\swstg.ini Change the version information within each file, as follows. Descriptive Contents of Version Information Upgrade Patterns Before After Version 16.0 to 16.6 Version=V16.0...
  • Page 231 When the operation divides shared disk for shared data use and the shared disk for repository use, the resources of the shared disk for repository use are deleted. 10.1.2.5 Tasks to Be Performed After Upgrade (Secondary Node) The tasks below need to be performed on the secondary node. In the version level of this ETERNUS SF Manager, Symfoware is not used.
  • Page 232 Point When ETERNUS SF Manager has been recovered to normal state by performing the task described in "11.3.1 In Case of Problem During Upgrade of ETERNUS SF Manager (for Windows)", to ensure data consistency, execute the stgxfwcmmodsrv command to perform the server information change processing.
  • Page 233 10.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.
  • Page 234 The following message is displayed after the Symfoware uninstallation is completed normally. Uninstallation of "Symfoware Server Enterprise Edition" is ended normally. Perform the kernel parameter tuning. Refer to "Before Installation" in "Installation of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for this version for information on tuning.
  • Page 235 On the primary node, stop the cluster application (transaction) to which ETERNUS SF Manager belongs. Refer to the relevant cluster software manuals for information on stopping it. However, the shared disk for shared data of ETERNUS SF Manager must be mounted. If Managed Server transactions coexist in a clustered system, perform the following.
  • Page 236 10.2.2.4 Tasks to Be Performed After Upgrade (Primary Node) The tasks below need to be performed on the primary node. The shared disk for shared data of ETERNUS SF Manager must be mounted. 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.
  • Page 237 Descriptive Contents of Version Information Upgrade Patterns Before After Version 16.0 to 16.6 Version=V16.0 Version 16.1 to 16.6 Version=V16.1 Version 16.2 to 16.6 Version=V16.2 Version=V16.6 Version 16.3 to 16.6 Version=V16.3 Version 16.4 to 16.6 Version=V16.4 Version 16.5 to 16.6 Version=V16.5 Note Do not change anything other than the version information.
  • Page 238 10.2.2.5 Tasks to Be Performed After Upgrade (Secondary Node) The tasks below need to be performed on the secondary node. 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.
  • Page 239 Refer to "Before Installation" in "Installation of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for this version for information on tuning. Check that the cluster application (transaction) has stopped. If not stopped, stop the cluster application (transaction) to which ETERNUS SF Manager belongs. Refer to the relevant cluster software manuals for information on stopping it (transaction).
  • Page 240 If the Storage Cruiser's agent has been installed, stop the service of the Storage Cruiser's agent. Refer to "Starting and Stopping Agent" in the ETERNUS SF Storage Cruiser Operation Guide for information on how to stop the service. Stop the service of AdvancedCopy Manager's agent. With the Windows services screen, stop the AdvancedCopy Manager COM Service.
  • Page 241 10.3.1.2 Performing Upgrade Note that if step 1 and step 2 have already been performed, perform from step 3. Note Although the initial screen of the installer is displayed during these steps, this is not used in the Upgrade Installation. Be sure to click Exit and end the screen.
  • Page 242 The following steps are explained using screen examples when the installation wizard of the 32 bit version agent is started. The following dialog box is displayed. Click Yes. The installation wizard page is displayed. Click Next. - 218 -...
  • Page 243 Read the terms and conditions of the License Agreement page. If the conditions are agreeable, click Yes. Check the settings information in the Start Copying Files page, and then click Next. - 219 -...
  • Page 244 Copying of the program is started. The following installation wizard page is displayed. The upgrade process is completed. Click Finish. Eject the DVD-ROM. When the tasks described above have been performed, the upgrade of the AdvancedCopy Manager's agent is complete. Refer to "10.3.1.4 Tasks to Be Performed After Upgrade"...
  • Page 245 For installLogFile, specify the file in which to output installation log with an absolute path. It is optional to specify for installLogFile. [When using the 32 bit version Agent] dvdromDrive:\Agent_windows\AdvancedCopy_Manager\agent\windows_x86\acmagtsilentinstall.bat [-l < installLogFile >] [When using the 64 bit version Agent] dvdromDrive:\Agent_windows\AdvancedCopy_Manager\agent\windows_x64\acmagtsilentinstall.bat [-l <...
  • Page 246 If the Storage Cruiser's agent has been installed, start the service of the Storage Cruiser's agent. Refer to "Starting and Stopping Agent" in the ETERNUS SF Storage Cruiser Operation Guide for information on how to start the service. Starting the service of AdvancedCopy Manager's agent With the Windows services screen, start the AdvancedCopy Manager COM Service.
  • Page 247 Log on to the server using Administrator privileges. Check that Managed Server transactions are stopped on the secondary node. If not stopped, use the Failover Cluster Manager to stop Managed Server transactions on the secondary node. If multiple Managed Server transactions exist, perform this procedure on each secondary node for Managed Server transactions. Stop the Managed Server transaction on the primary node.
  • Page 248 dvdromDrive:\Agent_windows\AdvancedCopy_Manager\agent\windows_x86\esfacmapreinst.bat backupDir [When using the 64 bit version Agent] dvdromDrive:\Agent_windows\AdvancedCopy_Manager\agent\windows_x64\esfacmapreinst.bat backupDir When the backup fails, after confirming the output error message and removing the cause of the failure, execute the batch file again. Point The characters " | : * ? / . < > % & ^ ; ! are not supported for directory names. If the directory name contains any spaces, they should be surrounded by double quote characters.
  • Page 249 The following window is displayed. For the Upgrade Installation, this window is not used. Click Exit. Start the following installation wizard corresponding to the architecture of AdvancedCopy Manager's agent checked in preparing for the upgrade: For 32 bit version: dvdromDrive:\Agent_windows\AdvancedCopy_Manager\agent\windows_x86\setup.exe For 64 bit version: dvdromDrive:\Agent_windows\AdvancedCopy_Manager\agent\windows_x64\setup.exe The following steps are explained using screen examples when the installation wizard of the 32 bit version agent is started.
  • Page 250 The following installation wizard page is displayed. Click Next. Read the terms and conditions of the License Agreement page. If the conditions are agreeable, click Yes. - 226 -...
  • Page 251 Check the settings information in the Start Copying Files page, and then click Next. Copying of the program is started. The following installation wizard page is displayed. The upgrade process is completed. Click Finish. Eject the DVD-ROM. When the tasks described above have been performed, the upgrade of the AdvancedCopy Manager's agent is complete. When the upgrade of the primary node has been completed, refer to "10.3.2.4 Tasks to Be Performed After Upgrade (Primary Node)"...
  • Page 252 When the upgrade of the secondary node has been completed, refer to "10.3.2.7 Tasks to Be Performed After Upgrade (Secondary Node) " and set up the AdvancedCopy Manager's agent of the secondary node. Point If the Upgrade Installation has ended in an error, refer to "11.3.5 In Case of Problem During Upgrade of AdvancedCopy Manager's Agent (for Windows)"...
  • Page 253 Note If an invalid option is specified, its corresponding error message is output in the install log file and the process exits. No error message is output in the command prompt or screen. Do not execute multiplexly the command for silent installation. If it is multiplexly executed, the command executed after that terminates abnormally.
  • Page 254 10.3.2.5 Performing Upgrade (Secondary Node) Perform the upgrade for the secondary node. The upgrade procedure is the same as that for the primary node. Refer to "10.3.2.2 Performing Upgrade (Primary Node)". Point If this secondary node acts as a primary node for other Managed Server transactions, it is upgraded as a primary node, so this procedure is not needed.
  • Page 255 Note For changing the server information, start a new window for command execution, and then perform the procedure on the window. Refer to "Command References" in the ETERNUS SF AdvancedCopy Manager Operation Guide relevant to the OS of the Management Server for information on the command. Perform the following operations with Web Console to reload the server information.
  • Page 256 Fixed configuration directory and Modifying configuration directory of "For Solaris environment" or "For Linux environment" under "Required disk space for installation" in the ETERNUS SF Installation and Setup Guide "For Solaris, Linux, HP-UX or AIX environment" under "Required disk space for operation" in the ETERNUS SF Installation and Setup Guide The procedure is shown below: Insert the DVD-ROM "ETERNUS SF SC/ACM/Express Mediapack for Windows (Agent Program and Manual)"...
  • Page 257 # dvdromMountPoint/Agent_unix/AdvancedCopy_Manager/sles12_x86/esfacmapreinst.sh backupDir [When using the Solaris Agent] # dvdromMountPoint/Agent_unix/AdvancedCopy_Manager/Solaris/esfacmapreinst.sh backupDir When the backup fails, after confirming the output error message and removing the cause of the failure, execute the shell script again. 10.4.1.2 Performing Upgrade 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.
  • Page 258 ETERNUS SF AdvancedCopy Manager 16.6 Copyright FUJITSU LIMITED 2013-2017 +-----------------------------------------------------------+ Welcome to Setup. This program will install "AdvancedCopy Manager" on your system. A confirmation message is displayed before uninstalling the previous version. To uninstall the previous version and proceed with the new installation, enter "y".
  • Page 259 In command example, the device name of the DVD-ROM drive is mounted as /dev/cdrom. The device name of the DVD-ROM drive may differ depending on the device. Install the AdvancedCopy Manager's agent. Execute the following commands for the silent installation to install the AdvancedCopy Manager's agent. For installLogFile, specify the file in which to output installation log with an absolute path.
  • Page 260 The installation result can be viewed in the install log file, too. Open the install log file to see "ResultCode" in the ResponseResult section. In "ResultCode" is written the return value from the silent installation command. Point If the upgrade was terminated abnormally, refer to "11.3.6 In Case of Problem During Upgrade of AdvancedCopy Manager's Agent (for Solaris, Linux)"...
  • Page 261 10.4.2 Upgrading on Clustered Systems 10.4.2.1 Preparing for Upgrade Point It is recommended that you back up the following resources 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.
  • Page 262 Mount the DVD-ROM. Example for Solaris # mount -F hsfs -o ro /dev/dsk/c0t4d0s0 dvdromMountPoint In command example, the device name of the DVD-ROM drive is mounted as /dev/dsk/c0t4d0s0. The device name of the DVD-ROM drive may differ depending on the device. Example for RHEL5/RHEL6/RHEL7 # mount -t iso9660 -r /dev/cdrom dvdromMountPoint In command example, the device name of the DVD-ROM drive is mounted as /dev/cdrom.
  • Page 263 Red Hat Enterprise Linux 6 (for Intel64) Red Hat Enterprise Linux 7 (for Intel64) dvdromMountPoint/Agent_unix/AdvancedCopy_Manager/rhel7_x86 The installation information is displayed. swsetup: Installer is preparing for installation... +-----------------------------------------------------------+ ETERNUS SF AdvancedCopy Manager 16.6 Copyright FUJITSU LIMITED 2013-2017 +-----------------------------------------------------------+ - 239 -...
  • Page 264 Welcome to Setup. This program will install "AdvancedCopy Manager" on your system. A confirmation message is displayed before uninstalling the previous version. To uninstall the previous version and proceed with the new installation, enter "y". To cancel the installation, enter "q". Press Enter. An old version is installed in this system.
  • Page 265 Install the AdvancedCopy Manager's agent. Execute the following commands for the silent installation to install the AdvancedCopy Manager's agent. For installLogFile, specify the file in which to output installation log with an absolute path. It is optional to specify for installLogFile. # environmentDir /acmagtsilentinstall.sh [-l <installLogFile>] The environmentDir is as follows.
  • Page 266 Point If the upgrade was terminated abnormally, refer to "11.3.6 In Case of Problem During Upgrade of AdvancedCopy Manager's Agent (for Solaris, Linux)" to recover the system to the normal state. 10.4.2.4 Tasks to Be Performed After Upgrade (Primary Node) The tasks below need to be performed.
  • Page 267 Point If this secondary node acts as a primary node for other Managed Server transactions, it is upgraded as a primary node, so this procedure is not needed. 10.4.2.7 Tasks to Be Performed After Upgrade (Secondary Node) No operation is required after upgrade at the secondary node. 10.4.2.8 Starting Managed Server Transactions Perform the following procedure:...
  • Page 268 Point Once normal operation has been confirmed after the upgrade of the AdvancedCopy Manager's agent, the backup data in the backup destination directory created in step 5-d of "10.4.2.1 Preparing for Upgrade" maybe deleted. 10.5 Upgrading AdvancedCopy Manager's agent (for HP-UX, AIX) This section describes the upgrade procedure for AdvancedCopy Manager's agent.
  • Page 269 Refer to "Deletion of Cluster Environment for Managed Server Transactions" in the ETERNUS SF Cluster Environment Setup Guide for the previous version for information on the unsetup of cluster settings. 10.5.4 Installing This Version Install the AdvancedCopy Manager's agent of this version, and setup the operating environment. About Installation For non-clustered systems Refer to "Installation of AdvancedCopy Manager's Agent"...
  • Page 270 Note For restoration of the repository data, start a new window for command execution, and then perform the procedure on the window. Refer to "Command References" in the ETERNUS SF AdvancedCopy Manager Operation Guide relevant to the OS of the Management Server for information on the command.
  • Page 271 On the global navigation tab, click Server. The registered server list is displayed in the Main pane. On the Main pane, check the target server checkbox. If the target server is a VM guest, check the checkbox of the VM host where the VM guest exists. On the Action pane, click Reload Conf.
  • Page 272 Point If the Upgrade Installation has ended in an error, refer to "11.3.1 In Case of Problem During Upgrade of ETERNUS SF Manager (for Windows)" and return the system to a normal state. 10.6.2 Upgrading on Clustered Systems 10.6.2.1 Preparing for Upgrade Point It is recommended that you back up the following resources before starting the upgrade.
  • Page 273 Recover the original environment configurations file (sys.properties) of the AdvancedCopy Manager CCM. Overwrite the original environment configurations file onto the file of the copying destination. Original Environment Configurations File Copying Destination File $INS_DIR\CCM\noncluster\sys\sys.properties $INS_DIR\CCM\sys\sys.properties Save the general script for the AdvancedCopy Manager CCM. In corresponding previous version of "Preparing General Scripts for AdvancedCopy Manager CCM"...

  • Page 274: Upgrading Advancedcopy Manager Copy Control Module (For Solaris, Linux)

    When the upgrade has been completed, the shared disk for shared data of AdvancedCopy Manager Copy Control Module must be offline. Afterwards, it must be online on the primary node. 10.6.2.6 Start CCM Server Transactions When the upgrade has been completed, start the CCM Server transactions. Use the Failover Cluster Manager on the primary node to start the transactions of AdvancedCopy Manager CCM.

  • Page 275: Performing Upgrade (Primary Node)

    Point It is recommended that you back up the following resources 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.

  • Page 276: Tasks To Be Performed After Upgrade (Primary Node)

    Refer to "C.8 Procedures for Upgrade Installation of AdvancedCopy Manager Copy Control Module Version 16.x (for Solaris, Linux)" and perform the Upgrade Installation. The shared disk for shared data of AdvancedCopy Manager Copy Control Module must be unmounted. 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.

  • Page 277: Chapter 11 Collecting Troubleshooting Information

    Control Module AdvancedCopy Manager Operator's Guide for Copy Control Module When no error message is displayed, refer to the following manuals for the previous version, to collect the troubleshooting information and then contact Fujitsu Technical Support. Target for Upgrade Reference Express "Trouble analysis"...

  • Page 278: In Case Of Problem During Upgrade From Version 15.X

    Solaris, Linux) The workaround is stated in the procedures for upgrade in this document. Confirm the individual procedures for upgrading. If the problem persists, refer to the following manuals, to collect the troubleshooting information and then contact Fujitsu Technical Support.

  • Page 279: In Case Of Problem During Upgrade Of Storage Cruiser's Agent (For Windows)

    If the problem persists, refer to "Collecting Troubleshooting Information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the troubleshooting information and then contact Fujitsu Technical Support. 11.2.3 In Case of Problem During Upgrade of Storage Cruiser's Agent (for Solaris, Linux) The system can be recovered to the same status as Upgrade Installation completed normally.

  • Page 280: In Case Of Problem During Upgrade Of Advancedcopy Manager's Agent (For Windows)

    If the problem persists, refer to "Collecting Troubleshooting Information" in the ETERNUS SF AdvancedCopy Manager Operation Guide to collect the troubleshooting information and then contact Fujitsu Technical Support. 11.2.5 In Case of Problem During Upgrade of AdvancedCopy Manager's Agent (for Solaris, Linux) The system can be restore to the same status as Upgrade Installation completed normally.
  • Page 281 Information After executing the swunsetup command, when reinstalling AdvancedCopy Manager's agent in other directory, make sure that the directory of the package listed in "Program Components of AdvancedCopy Manager's Agent" in this version of the ETERNUS SF Installation and Setup Guide is not left. Even if the swunsetup command is executed, the directory of the package listed in "Program Components of AdvancedCopy Manager's Agent"...

  • Page 282: In Case Of Problem During Uninstallation Of Previous Version Of Storage Cruiser's Agent Or Advancedcopy Manager's Agent

    AdvancedCopy Manager AdvancedCopy Manager Copy Control Module When no error message is displayed, refer to the following manuals for the previous version, to collect the troubleshooting information and then contact Fujitsu Technical Support. Target for Upgrade Reference Express "Trouble analysis" in the ETERNUS SF Express Operation Guide Storage Cruiser "Troubleshooting information"...

  • Page 283: In Case Of Problem During Upgrade From Version 16.X

    AdvancedCopy Manager AdvancedCopy Manager Copy Control Module When no error message is displayed, refer to the following manuals for this version, to collect the troubleshooting information and then contact Fujitsu Technical Support. Target for Upgrade Reference Express "Collecting Troubleshooting Information" in the ETERNUS SF Express...
  • Page 284 If this message is output, malfunction of the system is possible. Contact your Fujitsu Technical Support. Note This command backs up the data of the previous version to an installation destination directory and uninstalls the ETERNUS SF Manager program.

  • Page 285: In Case Of Problem During Upgrade Of Eternus Sf Manager (For Solaris, Linux)

    Linux) The workaround is stated in the procedures for upgrade in this document. Confirm the individual procedures for upgrading. If the problem persists, refer to the manual below, to collect the troubleshooting information and then contact Fujitsu Technical Support. Target for Upgrade...
  • Page 286 If registry deletion fails, a critical impact may be given on the system. It is recommended that you back up the registry beforehand. Delete the following registries by Registry Editor: [32 bit operating system] HKEY_CLASSES_ROOT\Installer\Products\472B5B2AC92C5C44682AC58BE99AA69B HKEY_LOCAL_MACHINE\SOFTWARE\Fujitsu\ETERNUS-SSC\Agent HKEY_LOCAL_MACHINE\SOFTWARE\Fujitsu\Install\ETERNUS-SSC\AgentLevel HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData \S-1-5-18\Products\472B5B2AC92C5C44682AC58BE99AA69B HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{A2B5B274-...

  • Page 287: In Case Of Problem During Upgrade Of Storage Cruiser's Agent (For Solaris, Linux)

    Point Installer creates a hidden directory. Select the "Show hidden files, folders and drives" radio button on the View tab for Folder and Search options in Explorer, and hidden directories are displayed. Delete service name Delete the service name. Delete the line when the following lines exist in the %SystemRoot%\system32\drivers\etc\services file. sscruisera Install Storage Cruiser's agent.
  • Page 288 If deleting the registry fails, a critical impact may be given to the system. It is recommended that you back up the registry beforehand. Delete the following registries by Registry Editor: [When AdvancedCopy Manager's agent is a 32 bit version on 32 bit operating system:] HKEY_CLASSES_ROOT\Installer\Products\F8087B8841D72AB4F9C6DCD4966C1565 HKEY_LOCAL_MACHINE\SOFTWARE\Fujitsu\AdvancedCopy Manager HKEY_LOCAL_MACHINE\SOFTWARE\Fujitsu\Install\AdvancedCopy Manager HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData \S-1-5-18\Products\F8087B8841D72AB4F9C6DCD4966C1565 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall...
  • Page 289 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Fujitsu\Install\AdvancedCopy Manager HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall \{88B7808F-7D14-4BA2-9F6C-CD4D69C65156} HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall \InstallShield_{88B7808F-7D14-4BA2-9F6C-CD4D69C65156} [When AdvancedCopy Manager's agent is a 64 bit version on 64 bit operating system:] HKEY_CLASSES_ROOT\Installer\Products\F8087B8841D72AB4F9C6DCD4966C1565 HKEY_LOCAL_MACHINE\SOFTWARE\Fujitsu\AdvancedCopy Manager HKEY_LOCAL_MACHINE\SOFTWARE\Fujitsu\Install\AdvancedCopy Manager HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData \S-1-5-18\Products\F8087B8841D72AB4F9C6DCD4966C1565 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall \{88B7808F-7D14-4BA2-9F6C-CD4D69C65156} HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall \InstallShield_{88B7808F-7D14-4BA2-9F6C-CD4D69C65156} Delete AdvancedCopy Manager installed directories. Delete the program directory, environment configuration directory and working directory when Advanced Copy Manager's agent was installed.

  • Page 290: In Case Of Problem During Upgrade Of Advancedcopy Manager's Agent (For Windows)

    AdvancedCopy Manager AdvancedCopy Manager Copy Control Module When no error message is displayed, refer to the following manuals for the previous version, to collect the troubleshooting information and then contact your Fujitsu Technical Support. Target for Upgrade Reference Express "Collecting Troubleshooting Information" in the ETERNUS SF Express...

  • Page 291: In Case Of Problem During Installation Of This Version Of Storage Cruiser's Agent Or Advancedcopy Manager's Agent

    AdvancedCopy Manager AdvancedCopy Manager Copy Control Module When no error message is displayed, refer to the following manuals for this version, to collect the troubleshooting information and then contact your Fujitsu Technical Support. Target for Upgrade Reference Express "Collecting Troubleshooting Information" in the ETERNUS SF Express...

  • Page 292: Chapter 12 Configuration Import

    Chapter 12 Configuration Import This chapter describes the configuration import. 12.1 Command References 12.1.1 esfadm devconf import (Configuration Import Command) NAME esfadm devconf import - import the configuration information from the previous version SYNOPSIS Windows Environment $INS_DIR\Common\bin\esfadm devconf import -all ($INS_DIR is the program directory specified at the ETERNUS SF Manager installation.) Solaris or Linux Environment /opt/FJSVesfcm/bin/esfadm devconf import -all...

  • Page 293: Esfadm Devconf Importstatus (Configuration Import Status Display Command)

    Operation is not possible on the targeted devices during the command execution. When the removed devices are registered in the configuration information at the previous version, the import of configuration information for their devices fails. In this case, the action is unnecessary. Import time for a storage device is approximately 10 minutes.
  • Page 294 Title Displayed Contents IP ADDRESS IP address of the device When the CATEGORY is "tierpolicy", "-" is displayed. REGISTER MODE Device registration mode Auto : Automatic registration Manual : Manual registration When the CATEGORY is "tierpolicy", "-" is displayed. STATUS Import status for the migration target resource Wait : Paused Execute : Executing...

  • Page 295: What To Do When Error Occurs

    12.2 What to Do When Error Occurs The results of the import process are output in the Operation History of Web Console. To try and import again the devices for which the import process has failed, re-execute the esfadm devconf import command after taking appropriate action for the message of Operation History.

  • Page 296: Appendix A Operation For Previous Version Environment

    Appendix A Operation for Previous Version Environment Backing Up Repository Data (for Windows) Save the repository data to the specified directory all at once. Perform this operation on the Management Server (Storage Management Server). Pre-Upgrade Environment Is Version 16.0 or Earlier Note Create a directory in which data is saved in advance.
  • Page 297 The following screen is displayed. Enter a backup directory and click OK. The following screen is displayed. Check that the displayed information is correct and click Start. The following screen is displayed after the process is completed. Click Close. Click Close displayed in step 3 to complete the DB maintenance. Click Exit displayed in step 2 to complete the DB backup.
  • Page 298 Information Notation in Procedure: File Name / Directory Name Explanation $BAK_FILE Backup file name for which an absolute path is specified $INS_DIR "Program Directory" specified at the ETERNUS SF Manager installation The procedure is shown below: Stop the ETERNUS SF Express Tomcat service. Open Service Control Manager to stop the following service.
  • Page 299 Database backup //////////////////////////////////////////////////////////////////// +----------------------------------------------------------------+ All of the stored data will be saved in an external file. [Notes] Prepare a directory for storing the data to be saved. +----------------------------------------------------------------+ Do you want to continue with processing? [y/n] ==> y The following message is displayed. Enter the absolute path name of the directory for storing the data to be saved.
  • Page 300 Backup of DB data is complete. ================================================================== Database backup ended normally. Check that the backup of database has been completed successfully. Make sure that the file with ".unl" extension is created in the specified directory. Pre-Upgrade Environment Is Version 16.1 or Later Note Create a directory in which data is saved in advance.
  • Page 301 If Backup Operation Has Been Done Check the data size of the backup management list under the following directory: If the Managed Server is in a non-cluster environment environmentDir\etc\backup\data If the Managed Server is in a cluster environment <Drive letter of shared disk for shared data for AdvancedCopy Manager>:\etc\opt\swstorage\etc\backup\data If you were backing up Symfoware databases, also check the file sizes in the target directory for output of the recovery control file.

  • Page 302: Backing Up Repository Data (For Windows)

    File for Save File Name Pre-processing and post- environmentDir\etc\backup\scripts\OpcBackupPre.js processing scripts for backup environmentDir\etc\backup\scripts\OpcBackupPost.js management function environmentDir\etc\backup\scripts\OpcRestorePre.js environmentDir\etc\backup\scripts\OpcRestorePost.js Transaction volume locking environmentDir\etc\backup\data\BTRANLOCK.INI specification file for backups Backup volume locking environmentDir\etc\backup\data\BBACKLOCK.INI specification file for backups Backup-restored volume environmentDir\etc\backup\data\RDSTLOCK.INI locking specification file For Clustered Systems File for Save File Name...
  • Page 303 Save pre-processing and post-processing scripts and specification files. Save the following files by using the copy command: Pre-processing and post-processing scripts for replication management function Copy source volume locking specification file Copy destination volume locking specification file Timeout value setting file for the concurrent suspend function Information The volume locking specification files might not exist according to the environment.

  • Page 304: Backing Up Management Information (For Solaris, Linux)

    File for Save File Name Drive letter map file environmentDir\etc\repl\data\EXDMAP.INI Device definition file environmentDir\etc\eternus_hardope.def Backing Up Management Information (for Solaris, Linux) Save the management information which exists in the Managed Server (Storage Server). If Backup Operation Has Been Done Check the data size of the backup management list under the following directory: If the Managed Server is in a non-cluster environment /etc/opt/FJSVswsts/data If the Managed Server is in a cluster environment...

  • Page 305: Backing Up Management Information (For Hp-Ux, Aix)

    File for Save File Name Pre-processing and post-processing /etc/opt/FJSVswsts/logicalNodeName/sh/OpcBackup.pre scripts for backup management /etc/opt/FJSVswsts/logicalNodeName/sh/OpcBackup.post function /etc/opt/FJSVswsts/logicalNodeName/sh/OpcRestore.pre /etc/opt/FJSVswsts/logicalNodeName/sh/OpcRestore.post If Replication Operation Has Been Done Save the replication management list. The replication management list is stored in the repository on the Management Server (Storage Management Server). For this reason, if the repository data has been saved when migrating the Management Server, this step is not required.
  • Page 306 If the Managed Server is in a cluster environment /etc/opt/FJSVswsts/logicalNodeName/data Save the backup management list. Specify the directory which can store the data size checked in step 1 and execute the following command: # /opt/FJSVswsts/bin/swstresback saveDir Refer to the manuals according to the previous operating environment's version for information on the command. In the case of Version 14.2 or earlier "swstresback (Resource backup command)"...

  • Page 307: Backing Up Environment Setting Files

    For Non-clustered Systems File for Save File Name Pre-processing and post-processing /etc/opt/FJSVswsrp/sh/RepSrc.pre scripts for replication management /etc/opt/FJSVswsrp/sh/RepDst.pre function /etc/opt/FJSVswsrp/sh/RepSrc.post /etc/opt/FJSVswsrp/sh/RepDst.post Timeout value setting file for the /etc/opt/FJSVswsrp/data/DEFAULT/check.ini concurrent suspend function For Clustered Systems File for Save File Name Pre-processing and post-processing /etc/opt/FJSVswsrp/logicalNodeName/sh/RepSrc.pre scripts for replication management /etc/opt/FJSVswsrp/logicalNodeName/sh/RepDst.pre...
  • Page 308 File Name Remarks $ENV_DIR\CCM\etc\stxcvolinf $TMP_DIR\CCM\var\micc\database\DeviceRegList.xml $ENV_DIR is the "Environment Directory" as specified during AdvancedCopy Manager CCM installation. $TMP_DIR is the "Work Directory" as specified during AdvancedCopy Manager CCM installation. For Solaris or Linux [AdvancedCopy Manager Copy Control Module Version 14.2 or earlier] File Name Remarks /etc/opt/FJSVccm/db/eternus.xml...

  • Page 309: Unsetting Up Database

    File Name Remarks environment" in the ETERNUS SF $INS_DIR\sys\sys.properties Operation Guide for Copy Control Module. $INS_DIR\noncluster\micc\sys\.install.sys $INS_DIR\noncluster\bin\.stxc_install.sys $INS_DIR\noncluster\sys\sys.properties $SHARE_DL is the drive letter of the shared disk for AdvancedCopy Manager CCM shared data. $SHARE_TOP is the directory that contains "Environment Directory" and "Work Directory" of the shared disk for AdvancedCopy Manager CCM shared data.
  • Page 310 Login to the server where the database unsetup is performed. For installing AdvancedCopy Manager of the previous version, login to the server as the user that has been specified when setting the database information. If you login to the server with another user, this operation may fail. Click Start >...

  • Page 311: Cancelling Repository Settings

    Cancelling Repository Settings Delete the database and its environment to cancel the repository configurations. Note Perform this operation as a root user. When the Management Server (Storage Management Server) is operated on the clustered system, the repository configurations are cancelled by deleting the Management Server transaction. Therefore, it is unnecessary to carry out this operation. Perform this operation with the locale specified when you installed the Management Server.

  • Page 312: Restoring Repository Data (For Windows)

    Clearing of database will start. (replication management) ================================================================== Tables have been deleted. (replication management) ================================================================== Clearing of database is complete. (replication management) ================================================================== ================================================================== The replication management has been deleted. ================================================================== ================================================================== Clearing of database environment is complete. ================================================================== ================================================================== The basic section has been deleted.

  • Page 313: Restoring Repository Data (For Solaris, Linux)

    A.10 Restoring Repository Data (for Solaris, Linux) Restore the repository data from the specified directory. Perform this operation on the Management Server. The procedure is shown below: Restore the repository data. Execute the stgrepocnv command to recover the migration target repository data to the current version repository. # /opt/FJSVswstf/bin/stgrepocnv -d saveDir Refer to "Command References"...
  • Page 314 File for Restoration Full Path Name for Restoration Destination device.ini <shared disk>:\etc\opt\swstorage\etc\device.ini Restore the backup management list. Specify the directory saved in "A.3 Backing Up Management Information (for Windows)" and execute the following command: For Management Server Which Also Serves as Managed Server C:\>...
  • Page 315 File for Restoration Full Path Name for Restoration Destination Transaction volume locking <shared disk>:\etc\opt\swstorage\etc\backup\data\BTRANLOCK.INI specification file for backups Backup volume locking <shared disk>:\etc\opt\swstorage\etc\backup\data\BBACKLOCK.INI specification file for backups Backup-restored volume locking <shared disk>:\etc\opt\swstorage\etc\backup\data\RDSTLOCK.INI specification file Note Do not restore pre-processing and post-processing scripts for backup management function by using copy command. The sample of pre-processing and post-processing scripts may be changed when upgrading a version.
  • Page 316 Restore specification files. Restore the following files saved in "A.3 Backing Up Management Information (for Windows)" by executing the copy command: Copy source volume locking specification file Copy destination volume locking specification file Timeout value setting file for the concurrent suspend function Information The volume locking specification files might not exist according to the environment.

  • Page 317: Restoring Management Information (For Solaris, Linux)

    File for Restoration Full Path Name for Restoration Destination Drive letter map file environmentDir\etc\repl\data\EXDMAP.INI Device definition file environmentDir\etc\eternus_hardope.def A.12 Restoring Management Information (for Solaris, Linux) Restore the management information which exists in the Managed Server. Note Caution about AdvancedCopy Manager's Agent in Linux Environment For environments in which udev devices exist, prioritize and use the following udev device names after upgrade.

  • Page 318: Restoring Management Information (For Hp-Ux, Aix)

    If Replication Operation Has Been Done Restore the replication management list. The replication management list is stored in the repository on the Management Server. Execute the following command. # /opt/FJSVswsrp/bin/swsrprecoverres -r Refer to "Command References" in the ETERNUS SF AdvancedCopy Manager Operation Guide for this version for information on the command.
  • Page 319 If using a different format device name before and after upgrade: Before upgrading, set the device format executing the stgxfwcmsetmode command, and then delete the definition for the backup management and replication management. After that, set the device format used after upgrading executing the stgxfwcmsetmode command, and then fetch the device information and redefine the backup management and replication management.

  • Page 320: Restoring Environment Setting Files

    Restore specification files. Restore the following files saved in "A.5 Backing Up Management Information (for HP-UX, AIX)" by executing the cp command: Timeout value setting file for the concurrent suspend function For Non-clustered Systems File for Restoration Full Path Name for Restoration Destination Timeout value setting file for the /etc/opt/FJSVswsrp/data/DEFAULT/check.ini concurrent suspend function...
  • Page 321 File Name Remarks /etc/opt/FJSVccm/accc/etc/stxcvolinf Copy the files which are saved in "A.6 Backing Up Environment Setting Files" to the following files and directories: For Windows File Name Remarks $ENV_DIR\CCM\etc\db\eternus.xml All files under $ENV_DIR\CCM\etc\db\cg directory $ENV_DIR\CCM\etc\prop\user.properties Only when files were backed up. $ENV_DIR\CCM\etc\stxc.alias $ENV_DIR\CCM\etc\stxc_ext.alias $ENV_DIR\CCM\etc\stxcvolinf...

  • Page 322: Backing Up Common Control Repository (For Windows)

    $SHARE_TOP is the directory that contains "Environment Directory" and "Work Directory" of the shared disk for AdvancedCopy Manager CCM shared data. For Solaris or Linux File Name Remarks All files under $SHARE_MNT/etc/opt/FJSVccm/db/cg directory $SHARE_MNT/etc/opt/FJSVccm/prop/user.properties Only when files exist. $SHARE_MNT/etc/opt/FJSVccm/accc/etc/stxc.alias $SHARE_MNT/etc/opt/FJSVccm/accc/etc/stxc_ext.alias $SHARE_MNT/etc/opt/FJSVccm/accc/etc/stxcvolinf $SHARE_MNT is the mount point of the shared disk for AdvancedCopy Manager CCM shared data.

  • Page 323: Backing Up Common Control Repository (For Solaris, Linux)

    Information Notation in Procedure: Directory Name Explanation $BAK_DIR Backup destination directory. $INS_DIR "Program Directory" specified at the ETERNUS SF Manager installation. Stop the ETERNUS SF Express Tomcat service. Open Service Control Manager to stop the following service. ETERNUS SF Manager Tomcat Service Create backup data.

  • Page 324: Backing Up License Management Database (For Windows)

    From a user with OS Administrator privilege, execute the following command to create backup data. If you did not change the port number, specify 15432 for portNumber. If you did change the port number, specify the changed port number for portNumber. The file name of the created backup data is backupFileName.

  • Page 325: Restoring Common Control Repository (For Windows)

    From a user with OS Administrator privilege, execute the following command to create backup data. The file name of the created backup data is backupFileName. /opt/FJSVesflm/bin/esflm backup $BAK_DIR/LM/backupFileName A.19 Restoring Common Control Repository (for Windows) Restore the common control repository. Information Notation in Procedure: Directory Name...

  • Page 326: Restoring Common Control Repository (For Solaris, Linux)

    A.20 Restoring Common Control Repository (for Solaris, Linux) Restore the common control repository. Information Notation in Procedure: Directory Name Explanation $BAK_DIR Backup destination directory. Stop the ETERNUS SF Manager Web service. Execute the following shell script to stop the service. /opt/FJSVesfcm/bin/stop-webservice.sh Restore the backup data.

  • Page 327: Restoring License Management Database (For Solaris, Linux)

    Information Notation in Procedure Directory Name Explanation $BAK_DIR Backup destination directory. $INS_DIR "Program Directory" specified at the ETERNUS SF Manager installation. Execute the following command with administrator privileges for the operating system. The backupFileName is the file name specified when the backup data was created. $INS_DIR\LM\bin\esflm restore $BAK_DIR\LM\backupFileName A.22 Restoring License Management Database (for Solaris, Linux)
  • Page 328 Backup the administration information of the disk array. Using Explorer, create the following backup directories: $BAK_DIR\ESC\Manager\etc\opt\FJSVssmgr\current $BAK_DIR\ESC\Manager\var\opt\FJSVssmgr\current\opencimom\logr Copy the subdirectories and files belonging to the following directory from their backup directory. Copy Source Directory Backup Destination Directory $INS_DIR\Storage Cruiser\Manager\var\opt\FJSVssmgr $BAK_DIR\ESC\Manager\var\opt\FJSVssmgr\current \current\opencimom\logr \opencimom\logr Copy the following file of the backup source to the directory of the backup destination.

  • Page 329: Restoring Of Express Operational Environment

    Backup Source Files Backup Destination Directory $INS_DIR\AdvancedCopy Manager Copy Control Module\etc $BAK_DIR\CCM\etc \stxcvlolinf $INS_DIR\AdvancedCopy Manager Copy Control Module\etc $BAK_DIR\CCM\etc\db \db\eternus.xml $INS_DIR\AdvancedCopy Manager Copy Control Module\etc $BAK_DIR\CCM\etc\prop \prop\user.properties $INS_DIR\AdvancedCopy Manager Copy Control Module\var $BAK_DIR\CCM\var\micc\database \micc\database\DeviceRegList.xml A.24 Restoring of Express Operational Environment Follow the procedure below to restore the environment for the Express's manager.
  • Page 330 Copy Source Directory Copy Destination Directory $BAK_DIR\ESC\Manager\var\opt\FJSVssmgr\current\perf $TMP_DIR\ESC\Manager\var\opt\FJSVssmgr\current \perf Restore the other files which can be customized. This restoration is unnecessary for the files or the directories which have not been backed up. Using Explorer or a similar program, copy the following files from the backup locations. Copy Source File Copy Destination Directory $BAK_DIR\ESC\Manager\etc\opt\FJSVssmgr\current...

  • Page 331: Backup Of Manager Operation Environment (For Windows)

    A.25 Backup of Manager Operation Environment (for Windows) Follow the procedure below to back up the environment for the Storage Cruiser's manager. Information Notation in Procedure Directory Name Explanation $BAK_DIR Backup destination directory. $INS_DIR The "Program Directory" when the manager was installed $ENV_DIR The "Environment Directory"...
  • Page 332 Copy Source Directory Copy Destination Directory $TMP_DIR\Manager\var\opt\FJSVssmgr\current\perf $BAK_DIR\ESC\Manager\var\opt\FJSVssmgr\current \perf Back up the other files which can be customized. It is unnecessary to back up the files or the directories which are not existed. Create the following backup directories in Explorer or a similar program. $BAK_DIR\ESC\Manager\etc\opt\FJSVssmgr\current $BAK_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\eventmail Using Explorer or a similar program, copy the following files to their backup locations.

  • Page 333: Backup Of Windows Version Manager Operation Environment (For Cluster Environment)

    If customizing the polling service setting file pollingService.xml, follow the step below to back it up. Create the following backup directory in Explorer or a similar program. $BAK_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\polling Using Explorer or a similar program, copy the following file to its backup location. Copy Source File Copy Destination Directory $ENV_DIR\Manager\etc\opt\FJSVssmgr\current\polling...
  • Page 334 cp -Rp /var/opt/FJSVssmgr/current/opencimom/logr/* $BAK_DIR/var/opt/FJSVssmgr/current/opencimom/ logr/ Back up the files related to the performance management function. This step can be skipped if you are not using the performance management function. Backup is not required if there are no subdirectories or files. Note If a pile of files related to the performance management function exists, calculate the backup time according to the amount of files.

  • Page 335: Backup Of Solaris/Linux Version Manager Operation Environment (For Cluster Environment)

    Back up the polling service setting file. This step can be skipped if you are not customizing the polling service setting file. If you have customized the polling service setting file pollingService.xml, back up this file using the step shown below. Create the directories for the backup data.
  • Page 336 Copy Source Directory Copy Destination Directory $BAK_DIR\ESC\Manager\var\opt\FJSVssmgr\current $TMP_DIR\ESC\Manager\var\opt\FJSVssmgr \opencimom\logr \current\opencimom\logr Restore the files related to the performance management function. This step can be skipped if you are not using the performance management function or the files related to the performance management function are not backed up.

  • Page 337: Restoring Of Windows Version Manager Operation Environment (For Cluster Environment)

    Refer to "perf.conf Parameter" in the ETERNUS SF Storage Cruiser Operation Guide for details of customizing the parameter of the perf.conf file. Restore the other files which can be customized. This restoration is unnecessary for the files or the directories which have not been backed up. Using Explorer or a similar program, copy the following files from the backup locations.

  • Page 338: Restoring Of Manager Operation Environment (For Solaris, Linux)

    Stop all cluster services to which the Manager belongs. Refer to "Cluster Transaction and Local Transaction" in the ETERNUS SF Cluster Environment Setup Guide for details of cluster transaction. Mount the shared disk on the primary node. Perform steps step 2 to 7 of "A.29 Restoring of Manager Operation Environment (for Windows)"...
  • Page 339 cp -p $BAK_DIR/etc/opt/FJSVssmgr/current/perf.conf /etc/opt/FJSVssmgr/current/ cp -Rp $BAK_DIR/var/opt/FJSVssmgr/current/perf/* /var/opt/FJSVssmgr/current/perf/ After copying, edit perf.conf(performance management definition file). What is edited is as follows: MONITORING_SIZE The number of devices whose performance is being monitored is specified in decimal format. Set the MONITORING_SIZE parameter to 0 (zero). MONITORING_NUMBER The information for the device whose performance is being monitored and the valid/invalid values for threshold monitoring are set up.

  • Page 340: Restoring Of Solaris/Linux Version Manager Operation Environment (For Cluster Environment)

    Restore the device polling setting files. This restoration is unnecessary for the files which have not been backed up. Copy the files from the backup location. cp -p $BAK_DIR/etc/opt/FJSVssmgr/current/devicepolling/*.xml /etc/opt/FJSVssmgr/current/ devicepolling/ Customization of the Polling Service Setting file is executed again. This restoration is unnecessary for the files which have not been backed up.
  • Page 341 In cases other than those listed above Capacity (MB) = 0 - 317 -...

  • Page 342: Appendix B Installation Parameter

    Appendix B Installation parameter This appendix explains the installation parameter file and the details of each installation parameter. Installation Parameter File (for ETERNUS SF Manager) The sample of the installation parameter file is provided on the DVD-ROM "ETERNUS SF SC/ACM Mediapack for Solaris (Manager Program) (2/2)"...
  • Page 343 Note Only LF is permitted for linefeed code. Do not use CR+LF or CR. Do not use double-byte character such as double-byte space. Installation Parameters (for ETERNUS SF Manager) The explanation of the installation parameters described below: Parameter Name Description Default Value When installing ETERNUS SF Manager, Installation_function...

  • Page 344: Installation Parameter File (For Advancedcopy Manager Copy Control Module)

    When you use both the IPv4 and IPv6 addresses with the Management Server: Set the IPv4 address used. The following operations are executed after the Upgrade Installation is completed and the IPv6 address is added as the IP address of the Management Server. Create a server information change instruction file on the Management Server.

  • Page 345: Appendix C Performing Upgrading

    Appendix C Performing Upgrading Procedures for Upgrade Installation of Manager Feature of Express / Storage Cruiser / AdvancedCopy Manager Version 14.x and 15.x (for Windows) There are two methods of performing the upgrade, as follows: Default installation The following configuration is used without the need to input any values. Installation destination The "systemDrive:\ETERNUS_SF"...
  • Page 346 The following window is displayed. Click Manager installation. To cancel the upgrade at this point, click Exit. The following dialog box is displayed. Select the appropriate language and click OK. The language selected in this dialog box is used during installation and uninstallation. The following progress bar is displayed.
  • Page 347 The installation wizard page is displayed. Click Next. Read the terms and conditions of the License Agreement page. If the conditions are agreeable, select [I accept the terms of the license agreement] and then click Next. - 323 -...
  • Page 348 Select the features and options to install from the Install option page. Confirm the IP address of the Management Server that is displayed and perform a customized installation if it is necessary to make changes. Feature selection Select [ETERNUS SF Manager is installed.]. Option selection Select the desired options according to the following information.
  • Page 349 Specify the installation directory in the Installation Destination page. If installing to a directory other than the default directory, click Browse and change the install destination. After designating all of the directories, click Next. Point Spaces and the characters " | : * ? / . < > , % & ^ = ! ; # ' @ ( ) + are not supported for directory names. The number of characters in a directory name must be between 4 and 70.
  • Page 350 Specify the port number for the services in the Port Registration page. Port number The default values are displayed. If necessary, enter alternative port numbers suitable for your environment. Values between 1024 and 65,535 are valid. To change the port number of Internal Port 5, edit the %SystemRoot%\system32\drivers\etc\services file by manual and define the unused port number under the following service name and in the range of 1024 - 65535.
  • Page 351 Execute the stgxfwcmmodsrv command with the -f option. programDir\ACM\bin\stgxfwcmmodsrv -f serverInformationChangeInstructionFileName When you use both the IPv4 and IPv6 addresses with the Management Server: Set the IPv4 address used. The following operations are executed after the Upgrade Installation is completed and the IPv6 address is added as the IP address of the Management Server.
  • Page 352 Check the settings information in the Start Copying Files page. If the settings are correct, click Next. To change a setting, click Back. The following dialog box is displayed. To proceed with the uninstallation, click Yes. If the previous program version is Version 14.x, the uninstallation page is displayed by clicking Yes. Uninstall the previous program version according to the instructions on the page.

  • Page 353: Solaris, Linux)

    The following installation wizard page is displayed. The upgrade process is completed. Click Finish. Eject the DVD-ROM. The upgrade is complete above. Return to the section where this item was referenced to continue tasks. Procedures for Upgrade Installation of Manager Feature of Express / Storage Cruiser / AdvancedCopy Manager Version 14.x and 15.x (for Solaris, Linux) There are two methods of performing the upgrade, as follows:...
  • Page 354 Used Port Service Service Name Installation Parameter Name Number esfmanagertomcat2 28009/tcp Internal_port_2 esfmanagertomcat3 28443/tcp Internal_port_3 sscruiserm 24916/tcp Internal_port_4 astm 24917/tcp Internal_port_5 Custom installation The upgrade is performed by manually entering the configuration information into the interface (communication service port number and so on). Define the installation information in the installation parameter file.
  • Page 355 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.
  • Page 356 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.

  • Page 357: Performing Upgrade

    Communications_service_1: 1226 Communications_service_2: 4917 Repository_service: 15432 Internal_port_1: 28005 Internal_port_2: 28009 Internal_port_3: 28443 Internal_port_4: 24916 Internal_port_5: 24917 Management_server_IP_address: esfpostgres_UID: StartService: no Do you want to continue the installation? [y,q]: A confirmation message is displayed before uninstalling the previous version. To uninstall the previous version and proceed with the new installation, enter "y".
  • Page 358 The following initial screen is displayed. Click on Manager installation. If you abort the Upgrade Installation, click Exit. Read the terms and conditions of the License Agreement page. If the conditions are agreeable, select [I accept the terms of the license agreement] and then click Next. - 334 -...
  • Page 359 The following screen is displayed. Click Yes. If you abort the Upgrade Installation, click No. The system configuration is updated. Wait for the configuration update process to complete. The following installation wizard page is displayed. The upgrade process is completed. Click Finish. Eject the DVD-ROM.
  • Page 360 Execute the following silent installation command. For installLogFile, specify the file in which to output installation log with an absolute path. It is optional to specify for installLogFile. <dvdromDrive>:\Manager_windows\esfsilentinstall.bat -eula agreed [-l <installLogFile>] Point The -eula option is specified to agree to licensing. Only when "agreed" is specified for option parameter is installation enabled.
  • Page 361 90 days from the date of delivery to you. Your sole and excl usive remedy and the entire liability of Fujitsu under this Condition of Use will be, at F ujitsu's option,replacement of the Media or refund of the money paid by you for the Media.
  • Page 362 Change to a directory other than the DVD-ROM. Example: # cd Unmount the DVD-ROM. Example: # umount /mnt/dvd Remove the DVD-ROM used for the Upgrade Installation from the device. The upgrade is complete above. Return to the section where this item was referenced to continue tasks. C.4.2 Performing Upgrade with Silent Installation Procedure The procedure of the silent upgrade installation are as listed below.

  • Page 363: Procedures For Upgrade Installation Of Advancedcopy Manager Copy Control Module Version 14.X And 15.X (For Windows)

    On completion of installation, a command prompt is displayed. Remove the DVD-ROM media used for installation out of the device. Example: # umount /mnt/dvd Eject the DVD-ROM. Confirming the Results of the Silent Upgrade Installation Check the return value from the silent installation command. If necessary, check the install log file. However, if the return value from the silent installation command is 3 or 9, an install log file is not created.
  • Page 364 The following window is displayed. Click Manager installation. To cancel the upgrade at this point, click Exit. The following dialog box is displayed. Select the appropriate language and click OK. The language selected in this dialog box is used during installation and uninstallation. The following progress bar is displayed.
  • Page 365 The installation wizard page is displayed. Click Next. Read the terms and conditions of the License Agreement page. If the conditions are agreeable, select [I accept the terms of the license agreement] and then click Next. - 341 -...
  • Page 366 Select the features and options to install from the Install option page. Feature selection Select [AdvancedCopy Manager Copy Control Module is installed.]. Option selection Select the desired options according to the following information. Install option Explanation Default Changing values in the Installation Destination page is optional. In this case, step 9 can be skipped.
  • Page 367 Specify the installation directory in the Installation Destination page. If installing to a directory other than the default directory, click Browse and change the install destination. After designating all of the directories, click Next. Point Spaces and the characters " | : * ? / . < > , % & ^ = ! ; # ' @ ( ) + are not supported for directory names. The number of characters in a directory name must be between 4 and 70.
  • Page 368 Check the settings information in the Start Copying Files page. If the settings are correct, click Next. To change a setting, click Back. The following dialog box is displayed. To proceed with the uninstallation, click Yes. When the uninstallation is completed, the copying of the files for the new version is started. During this process, the file copy completion status is displayed in the Setup Status page.

  • Page 369: Procedures For Upgrade Installation Of Advancedcopy Manager Copy Control Module Version 14.X And 15.X (For Solaris, Linux)345

    The following installation wizard page is displayed. The upgrade process is completed. Click Finish. The upgrade is complete above. Return to the section where this item was referenced to continue tasks. Procedures for Upgrade Installation of AdvancedCopy Manager Copy Control Module Version 14.x and 15.x (for Solaris, Linux) There are two methods of performing the upgrade, as follows.
  • Page 370 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.
  • Page 371 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.

  • Page 372: Procedures For Upgrade Installation Of Advancedcopy Manager Copy Control Module Version 16.X (For Windows)

    A confirmation message is displayed before uninstalling the previous version. To uninstall the previous version and proceed with the new installation, enter "y". To cancel the installation, enter "q". Press Enter. An old version is installed in this system. Do you want to remove old version from this system? [y,q]: Point For confirmation of uninstallation of the previous version, enter "y"...
  • Page 373 The following window is displayed. Click Manager installation. To cancel the upgrade at this point, click Exit. Read the terms and conditions of the License Agreement page. If the conditions are agreeable, select [I accept the terms of the license agreement] and then click Next. - 349 -...
  • Page 374 The following screen is displayed. Click Yes. If you abort the Upgrade Installation, click No. The system configuration is updated. Wait for the configuration update process to complete. The following installation wizard page is displayed. The upgrade process is completed. Click Finish. Eject the DVD-ROM.

  • Page 375: Procedures For Upgrade Installation Of Advancedcopy Manager Copy Control Module Version 16.X (For Solaris, Linux)

    Execute the following silent installation command. For installLogFile, specify the file in which to output installation log with an absolute path. It is optional to specify for installLogFile. <dvdromDrive>:\Manager_windows\esfsilentinstall_ccm.bat -eula agreed [-l <installLogFile>] Point The -eula option is specified to agree to licensing. Only when "agreed" is specified for option parameter is installation enabled.
  • Page 376 90 days from the date of delivery to you. Your sole and excl usive remedy and the entire liability of Fujitsu under this Condition of Use will be, at F ujitsu's option,replacement of the Media or refund of the money paid by you for the Media.
  • Page 377 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 Remove the DVD-ROM used for the Upgrade Installation from the device. The upgrade is complete above.
  • Page 378 Do not execute multiplexly the command for silent installation. If it is multiplexly executed, the command executed after that terminates abnormally. At this time, an install log file is not created. On completion of installation, a command prompt is displayed. Remove the DVD-ROM media used for installation out of the device.

This manual is also suitable for:

Eternus sf storage cruiser v16.6Eternus sf advancedcopy manager v16.6

Table of Contents