This section explains the upgrading of managers.
When operating managers in clusters, transfer using upgrade installation cannot be performed. Perform the upgrade manually.
Point
When upgrading from manager operating in clusters, replace the parts referring to the earlier versions of "ServerView Resource Coordinator VE manuals" with the earlier versions of "ServerView Resource Coordinator VE manuals" for the following procedure.
Transferred Data
The following manager data is transferred:
Resource Orchestrator setting information (Setting information for the environment of the earlier version)
Certificates
System images and cloning images (Files in the image file storage folder)
Also, with transfer using upgrade installation the following data is also transferred:
Port number settings
Power consumption data
Batch files and script files for event-related functions
Data which is transferred during upgrade installation is created and stored in the following folder. Ensure that this folder is not deleted until after the upgrade is complete.
[Windows Manager]
32bit(x86) OS
Drive_name\Program Files\RCVE-upgradedata
64bit(x64) OS
Drive_name\Program Files (x86)\RCVE-upgradedata
System_drive\swrbawork
installation_ folder\RCXCFMG-upgradedata
installation_ folder\RCXCTMG-upgradedata
[Linux Manager]
/var/opt/RCVE-upgradedata
/var/opt/backupscwdir
/var/tmp/swrbawork
Note
The total disk space of the following folders plus 100M bytes is required under System_drive\swrbawork and /var/tmp/swrbawork.
[Windows Manager]
System_drive\SWRBADB
installation_ folder\SWRBAM
installation_ folder\IAPS
installation_ folder\SWOMGR
[Linux Managaer]
/var/opt/FJSVJMCMN
/var/opt/FJSVJOBSC
/var/opt/FJSVMJS
/var/opt/FJSVcmdba
/var/opt/FJSVcmdbi
/var/opt/FJSVcmdbm
/var/opt/FJSVejb
/var/opt/FJSVena
/var/opt/FJSVes
/var/opt/FJSVextp
/var/opt/FJSVftlo
/var/opt/FJSVfwseo
/var/opt/FJSVfwtco
/var/opt/FJSVihs
/var/opt/FJSVirep
/var/opt/FJSVirepc
/var/opt/FJSVisas
/var/opt/FJSVisgui
/var/opt/FJSVisjmx
/var/opt/FJSVisscs
/var/opt/FJSVj2ee
/var/opt/FJSVjmcal
/var/opt/FJSVjms
/var/opt/FJSVjmweb
/var/opt/FJSVjs2su
/var/opt/FJSVjs5
/var/opt/FJSVlnkbs
/var/opt/FJSVod
/var/opt/FJSVots
/var/opt/FJSVporb
/var/opt/FJSVshnsk
/var/opt/FJSVshs
/var/opt/FJSVssoac
/var/opt/FJSVssoaz
/var/opt/FJSVssocm
/var/opt/FJSVssofs
/var/opt/FJSVssosv
/var/opt/FJSVstem
/var/opt/FJSVsvmon
/var/opt/FJSVswaic
/var/opt/FJSVswnc
/var/opt/FJSVswrbac
/var/opt/FJSVswrbam
/var/opt/FJSVtd
/etc/opt/FJSVMJS
/etc/opt/FJSVcmdba
/etc/opt/FJSVcmdbm
/etc/opt/FJSVejb
/etc/opt/FJSVes
/etc/opt/FJSVextp
/etc/opt/FJSVftlo
/etc/opt/FJSVihs
/etc/opt/FJSVirep
/etc/opt/FJSVisas
/etc/opt/FJSVisgui
/etc/opt/FJSVisjmx
/etc/opt/FJSVisscs
/etc/opt/FJSVj2ee
/etc/opt/FJSVjms
/etc/opt/FJSVjs2su
/etc/opt/FJSVjs5
/etc/opt/FJSVlnkbs
/etc/opt/FJSVod
/etc/opt/FJSVots
/etc/opt/FJSVporb
/etc/opt/FJSVsclr
/etc/opt/FJSVshnsk
/etc/opt/FJSVshs
/etc/opt/FJSVssoac
/etc/opt/FJSVssoaz
/etc/opt/FJSVssofs
/etc/opt/FJSVssosv
/etc/opt/FJSVsvmon
/etc/opt/FJSVswaic
/etc/opt/FJSVswnc
/etc/opt/FJSVswrbac
/etc/opt/FJSVswrbam
/etc/opt/FJSVtd
Preparations
Perform the following preparations and checks before upgrading:
Check that the environment is one in which managers of this version can be operated.
For the operational environment, refer to "2.4 Software Environment" and "2.5 Hardware Environment" of the "Design Guide CE".
Take particular care regarding the memory capacity.
To enable recovery in case there is unexpected trouble during the upgrade process, please back up the admin server. For how to back up the admin server, refer to "Appendix E Backup and Restoration of Admin Servers" of the "ServerView Resource Orchestrator User's Guide" or "Appendix B Admin Server Backup and Restore" of the "ServerView Resource Coordinator VE Operation Guide".
As well as backing up the admin server, also back up (copy) the following information:
Port number settings
[Windows Manager]
Drive_name\WINDOWS\system32\drivers\etc\services
[Linux Manager]
/etc/services
Batch files and script files for event-related functions
[Windows Manager]
Installation_folder\SVROR\Manager\etc\trapop.bat
[Linux Manager]
/etc/opt/FJSVrcvmr/trapop.sh
Definition files
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data
When using GLS to perform redundancy of NICs for the admin LAN of managed servers, activate the admin LAN on the primary interface.
To confirm that the upgrade is complete, if there are registered VM hosts on which there are VM guests, check from the ROR console that all of the VM guests are displayed and record their information before upgrading.
When server switchover settings have been performed, it is not possible to upgrade when spare servers have been switched to. Restore any such servers before starting the upgrade. For how to restore, refer to the information about Server Switchover in the "ServerView Resource Coordinator VE Operation Guide".
When using ETERNUS SF Storage Cruiser Manager or ETERNUS SF AdvancedCopy Manager, please stop the service or demon using the following procedure.For details on how to stop the service, refer to the manual of the relevant product.
Please check that the following ports are not used. If they are being used, please contact Fujitsu technical staff.
7676
8015
8686
12001
23600
23601
23602
23700
28080
Upgrade using Upgrade Installation
When upgrading to this version from ROR V3.0.0, upgrade can be performed using upgrade installation. Perform the upgrade using the following procedure:
Note
Do not change the hardware settings or configurations of managers, agents, or any other devices until upgrading is completed.
When there are system images and cloning images, the same amount of disk space as necessary for the system images and cloning images is required on the admin server in order to temporarily copy the images during the upgrade. Before performing the upgrade, check the available disk space.
When performing an upgrade installation, please do not access the installation folder of the earlier version or any of the files and folders inside it using the command prompt, Explorer, or an editor.
While it is being accessed, attempts to perform upgrade installation will fail.
If upgrade installation fails, stop accessing the files or folders and then perform the upgrade installation again.
In the event that upgrade installation fails, please resolve the cause of the failure and perform upgrade installation again. If the problem cannot be resolved and upgrade installation fails again, please contact Fujitsu technical staff.
When stopping the upgrade and restoring the earlier version, please do so by restoring the information that was backed up during the preparations.
When performing restoration and a manager of this version or an earlier version has been installed, please uninstall it.
After restoration, please delete the folder containing the backed up assets. For how to restore the admin server, refer to the "ServerView Resource Orchestrator User's Guide" or the "ServerView Resource Coordinator VE Operation Guide".
Upgrade installation will delete patches that were applied to the earlier version.
[Linux Manager]
When the PATH variable has not been configured to enable execution of UpdateAdvisor (Middleware) commands from a user-defined location, performing upgrade installation will delete any patches that have been applied to the old version, but it will not delete product information or component information. Refer to the UpdateAdvisor (Middleware) manual and delete software and component information from the applied modification checklist.
When operating managers in clusters, transfer using upgrade installation cannot be performed. Perform the upgrade manually.
If used ports exist when performing an upgrade installation, the message "The specified port number Port Number selected for ServerView Resource Orchestrator is already used." will be displayed, and installation will fail. If this happens, please contact Fujitsu technical staff.
[Windows Manager]
The specified port number Port Number selected for ServerView Resource Orchestrator is already used.
[Linux Manager]
The specified port number Port Number selected for ServerView Resource Orchestrator is already used.
Upgrade Installation
[Windows Manager]
Refer to "2.1.2 Installation [Windows Manager]", and execute the Resource Orchestrator installer.
The Resource Orchestrator setup window will be displayed. Check the contents of the license agreement, etc. and then click <Next>.
The settings to be inherited from the earlier version will be displayed. Check them and click <Next>. Upgrade installation will begin.
[Linux Manager]
Refer to "2.1.3 Installation [Linux Manager]", and execute the Resource Orchestrator installer.
Check the contents of the license agreement, etc. and then enter "y".
The setting information that will be taken over from the earlier version will be displayed. Please check it and then enter "y". Upgrade installation will begin.
Restarting after Upgrade Installation is Finished [Windows Manager]
After upgrade installation is finished, restart the system in order to complete the upgrade.
Transfer of Resource Data on the Directory Server
In the following cases, resource information in the directory server is shifted to management information on this product. Please use the rcxadm authctl export command for the shift.
When you do the user management by the directory service with ROR CE of the previous version
When you operate the single sign-on with ROR VE of the previous version
User group information and group users
It is necessary that user information be registered both on the directory server and as Resource Orchestrator information with the same name. When Resource Orchestrator is logged in, authentication is performed by the directory service. User password is managed by the directory service.
Role definitions
Access range and roles
Transfer of configuration methods for overcommit functions
For ROR V3.1.0 and later, the configuration method for overcommit functions differ from those of earlier versions of Resource Orchestrator. Therefore the configuration method must be transferred from the earlier version.
When performing upgrade installation of an admin server that is ROR V2.3.0 or V3.0.0, execute the following command to transfer the configuration information.
[Windows Manager]
Installation_folder\SVROR\Manager\bin\rcxmigrate_oc
[Linux Manager]
/opt/FJSVrcvmr/bin/rcxmigrate_oc
For details on the rcxmigrate_oc command, refer to "5.2 rcxmigrate_oc" in the "Reference Guide (Command/XML) CE".
Note
If this step is omitted, overcommit cannot be set for VM pools in "Chapter 20 Resource Pool Operations" in the "User's Guide for Infrastructure Administrators (Resource Management) CE". In that case, edit overcommit definition files as in the case of the earlier versions.
For details, refer to "G.1.1 Overcommit Definition Files".
The manager's setup
When the upgrade installation is done from RCVE, ROR VE of the thisversion ROR VE to Cloud Edition of this version, the manager's setup is necessary.
Please do the upgrade installation on this product after setting up the manager when you do the upgrade installation from ROR CE of the previous version to ROR CE of this version that is not the setup of the manager.
It is necessary to confirm whether the single sign-on is set before the manager's setup is executed.
For setting Single Sign-On, refer to "Chapter 12 Installing and Defining Single Sign-On" in the "Design Guide CE".
For the manager's setup, refer to "2.1.4 Setup" for the manager's setup.
Registration of license
Please access the ROR console after installing the upgrade to ROR CE, and register the license of Cloud Edition.
For the registration of the license, refer to the setting of the license of "Chapter 5 License Setup and Confirmation".
It is not necessary to register the license when upgrading from ROR CE of the previous version to ROR CE of this version.
When it accesses the ROR console from the browser, the SSL communication is used.
when you replace the certificate used by the SSL communication from the test certificate set up by default with other certificates, refer to "Chapter 3 SSL Communication Environment Settings for the ROR Console"
Note
When using backup system images or collecting cloning images without upgrading agents, either reboot managed servers after the manager upgrade is completed, or restart the related services.
For restarting the related services, refer to "5.2 Agent" in the "ServerView Resource Coordinator VE Setup Guide".
Before upgrading, installation and configuration of Single Sign-On are required.
For details, refer to "Chapter 12 Installing and Defining Single Sign-On" in the "Design Guide CE".
Manual Upgrade
Upgrading from earlier version ROR managers in clustered operation to ROR CE is performed by exporting and importing system configuration files for pre-configuration.
Perform the upgrade using the following procedure:
See
For pre-configuration, refer to the following manuals:
"User's Guide Infrastructure Administrators (Resource Management) CE"
"Chapter 10 Pre-configuration for Registering and Changing Resources"
"Appendix B Format of CSV System Configuration Files"
Note
Do not change the hardware settings or configurations of managers, agents, or any other devices until upgrading is completed.
Set Maintenance Mode
Use the ROR console to place all managed servers into maintenance mode.
System Configuration File Export
Use the pre-configuration function of the earlier version and export the system configuration file in CSV format. During the export, do not perform any other operations with Resource Orchestrator.
For the export method, refer to the "ServerView Resource Coordinator VE Setup Guide".
Back up (copy) Assets to Transfer
Perform backup (copying) of the certificates of the earlier version.
Back up (copy) the following folders and directories:
[Windows Manager]
Installation_folder\SVROR\Manager\etc\opt\FJSVssmgr\current\certificate
Installation_folder\SVROR\Manager\etc\opt\FJSVrcxdm\certificate
Installation_folder\SVROR\Manager\sys\apache\conf\ssl.crt
Installation_folder\SVROR\Manager\sys\apache\conf\ssl.key
[Linux Manager]
/etc/opt/FJSVrcvmr/opt/FJSVssmgr/current/certificate
/etc/opt/FJSVrcvmr/sys/apache/conf/ssl.crt
/etc/opt/FJSVrcvmr/sys/apache/conf/ssl.key
Back up (copy) the folder containing the cloning images of the earlier version to a location other than the installation folder and the image file storage folder.
When using the default image file storage folder, back up (copy) the following folder or directory:
[Windows Manager]
Installation_folder\SVROR\ScwPro\depot\Cloneimg
[Linux Manager]
/var/opt/FJSVscw-deploysv/depot/CLONEIMG
When using a folder or directory other than the default, back up (copy) the "Cloneimg" folder or "CLONEIMG" directory used.
Back up (copy) the following informations.
Port number settings
[Windows]
Drive_name\WINDOWS\system32\drivers\etc\services
[Linux]
/etc/services
Batch files and script files for event-related functions
[Windows]
Installation_folder\SVROR\Manager\etc\trapop.bat
[Linux]
/etc/opt/FJSVrcvmr/trapop.sh
Note
Before making a backup (copy) of system images and cloning images, check the available disk space. For the disk space necessary for system images and cloning images, refer to the "ServerView Resource Coordinator VE Installation Guide". When there is no storage folder for system images and cloning images, this step is not necessary.
Note
User account information is deleted when managers are uninstalled. Refer to step 7. and perform reconfiguration from the ROR console.
Uninstallation of earlier version managers
Refer to the "ServerView Resource Coordinator VE Installation Guide" for the method for uninstalling the manager of the earlier version.
Note
Do not perform "Delete servers" as described in Preparations of the "ServerView Resource Coordinator VE Installation Guide". When managed servers using HBA address rename have been deleted, it is necessary to reboot managed servers after upgrading of the manager is completed.
User account information is deleted when managers are uninstalled. Refer to step 7. and perform reconfiguration from the RC console.
Installation of Managers of This Version
Install managers of this version.
For installation, refer to "2.1 Manager Installation".
Note
When installing managers, specify the same admin LAN as used for the earlier version on the [Admin LAN Selection] window.
After installing managers, use the following procedure to restore the certificates and image file storage folder backed up (copied) in step 3.
Stop the manager.
Return the image file storage folder backup (copy) to the folder specified during installation.
When using the default image file storage folder, restore to the following folder or directory:
[Windows Manager]
Installation_folder\SVROR\ScwPro\depot\Cloneimg
[Linux Manager]
/var/opt/FJSVscw-deploysv/depot/CLONEIMG
When using a folder other than the default, restore to the new folder.
When the image file storage folder was not backed up, this step is not necessary.
Restore the backed up (copied) certificates to the manager installation_folder.
Restore to the following folder or directory:
[Windows Manager]
Installation_folder\SVROR\Manager\etc\opt\FJSVssmgr\current\certificate
Installation_folder\SVROR\Manager\etc\opt\FJSVrcxdm\certificate
Installation_folder\SVROR\Manager\sys\apache\conf\ssl.crt
Installation_folder\SVROR\Manager\sys\apache\conf\ssl.key
[Linux Manager]
/etc/opt/FJSVrcvmr/opt/FJSVssmgr/current/certificate
/etc/opt/FJSVrcvmr/sys/apache/conf/ssl.crt
/etc/opt/FJSVrcvmr/sys/apache/conf/ssl.key
Restore the information that was backed up during preparations.
Port number settings
Change the port numbers based on the information that was backed up during preparations.
For details on how to change port numbers, refer to "6.2 Changing Port Numbers" in the "User's Guide for Infrastructure Administrator (Resource Management) CE".
When the port number has not been changed from the default, this step is not necessary.
Batch files and script files for event-related functions
Restore them by replacing the following file.
[Windows Manager]
Installation_folder\SVROR\Manager\etc\trapop.bat
[Linux Manager]
/etc/opt/FJSVrcvmr/trapop.sh
Start the manager.
For the methods for starting and stopping managers, refer to "2.1 Starting and Stopping the Manager" in the "Operation Guide CE".
User Account Settings
Using the information recorded during preparations, perform setting of user accounts using the ROR console.
For details on how to configure user accounts, refer to "Chapter 3 Configuring Users for Infrastructure Administrators" in the "User's Guide for Infrastructure Administrator (Resource Management) CE".
Edit System Configuration Files
Based on the environment created for the earlier version, edit the system configuration file (CSV format) exported in step 2.
Change the operation column of all resources to "new".
When upgrading from RCVE V2.2.2 or later, do not change the operation column of resources contained in the following sections to "new":
ServerAgent
ServerVMHost
Memo
For how to edit system configuration files (CVS format), refer to the "ServerView Resource Coordinator VE Setup Guide".
Note
When the spare server information is configured, use the following procedure to delete the spare server information.
In the [SpareServer] section, set [operation] as a hyphen ("-").
Creating an Environment of This Version
Import the system configuration file and create an environment of this version.
Use the following procedure to configure an environment of this version.
Import of the system configuration file
Import the edited system configuration file.
For the import method, refer to "10.2 Importing the System Configuration File" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Register the Agent
Using the information recorded during preparations, perform agent registration using the ROR console. Perform agent registration with the OS of the managed server booted.
For details on registering agents, refer to "Chapter 11 Installing Software and Registering Agents on VM Hosts".
After completing agent registration, use the ROR console to check that all physical OS's and VM hosts are displayed. When there are VM hosts (with VM guests) registered, check that all VM guests are displayed.
Spare Server Information Settings
Using the information recorded during preparations, perform registration of spare server information using the ROR console.
For registration of spare server information, refer to "18.2 Server Switchover Settings" of the "User's Guide VE".
Registration of Labels, Comments, and Contact Information
When label, comment, and contact information has been registered, change the contents of the operation column of the system configuration file (CSV format) that were changed to "new" in step 6. back to hyphens ("-"), and change the contents of the operation column of resources contained in the [Memo] section to "new".
For how to edit system configuration files (CVS format), refer to the "ServerView Resource Coordinator VE Setup Guide".
Import the edited system configuration file.
For the import method, refer to "10.2 Importing the System Configuration File" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Set Maintenance Mode
Using the information recorded during preparation, place the managed servers placed into maintenance mode into maintenance mode again.
For maintenance mode settings, refer to "Appendix C Maintenance Mode" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Transfer of Configuration Methods for Overcommit Functions
For ROR V3.1.0 and later, the configuration method for overcommit functions differ from those of earlier versions of Resource Orchestrator. Therefore the configuration method must be transferred from the earlier version.
When performing upgrade installation of an admin server that is ROR V2.3.0 or V3.0.0, execute the following command to transfer the configuration information.
[Windows Manager]
Installation_folder\SVROR\Manager\bin\rcxmigrate_oc
[Linux Manager]
/opt/FJSVrcvmr/bin/rcxmigrate_oc
For details on the rcxmigrate_oc command, refer to "5.2 rcxmigrate_oc" in the "Reference Guide (Command/XML) CE".
Note
If this step is omitted, overcommit cannot be set for VM pools in "Chapter 20 Resource Pool Operations" in the "User's Guide for Infrastructure Administrators (Resource Management) CE". In that case, edit overcommit definition files as in the case of the earlier versions.
For details, refer to "G.1.1 Overcommit Definition Files".
Note
When using backup system images or collecting cloning images without upgrading agents, either reboot managed servers after the manager upgrade is completed, or restart the related services.
For restarting the related services, refer to "5.2 Agent" in the "ServerView Resource Coordinator VE Setup Guide".
Before upgrading, installation and configuration of Single Sign-On are required.
For details, refer to "Chapter 12 Installing and Defining Single Sign-On" in the "Design Guide CE".
