D.2 Manager

This section explains the upgrading of managers.

When operating managers in clusters, transfer using upgrade installation cannot be performed. Perform "Transfer of the Manager Using Re-installation or the Pre-configuration Function".

Point

In the following procedure, please understand that sections referring to the manuals of an earlier version of ServerView Resource Coordinator VE are actually referring to the manuals of an earlier version of ServerView Resource Orchestrator.
When maintaining compatibility with earlier versions, refer to "2.1.1 Maintaining Compatibility with Earlier Versions" in the "Release Notes", and change each setting.

[Windows Manager]

When upgrading an environment configured using ServerView Resource Coordinator VE to this version of FUJITSU Software ServerView Resource Orchestrator Virtual Edition, replace the "Installation_folder\SVROR\Manager" used in Resource Orchestrator manuals with "Installation_folder\Manager".

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, except for system images and cloning images, is created and stored in the following folder.
For system images and cloning images, the installation folder of the earlier version is used.
Ensure that the folder is not deleted until after the upgrade is complete.
After the upgrade is complete, the following folder may remain. In that case, check that Resource Orchestrator is operating correctly and then manually delete the folder.

[Windows Manager]
32-bit (x86) OS
Drive_name\Program Files\RCVE-upgradedata
64-bit (x64) OS
Drive_name\Program Files (x86)\RCVE-upgradedata

[Linux Manager]
/var/opt/RCVE-upgradedata
/var/opt/backupscwdir

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 "6.1 Software Environment" and "6.2 Hardware Environment" in the "Overview".
Take particular care regarding the memory capacity.
To enable recovery in case there is unexpected trouble during the upgrade process, please back up the system.
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 the settings for restarting of managers have been changed, check and record the settings, referring to "Restarting Managers" in "Appendix A Notes on Operating ServerView Resource Orchestrator" in the "Operation Guide VE".

Upgrade using Upgrade Installation

When upgrading to this version, 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 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.
To revert to the status before an upgrade was performed, restore the system that was backed up in the preparation stage.
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 transfer using re-installation or the pre-configuration function.
When the path of the installation folder before the upgrade is 46 characters or longer, transfer using upgrade installation is not possible. Perform transfer using re-installation or the pre-configuration function.
When the settings for restarting of managers have been changed, reconfigure the settings after the completion of the upgrade installation, based on the information which was recorded during preparation. For details, refer to "Restarting Managers" in "Appendix A Notes on Operating ServerView Resource Orchestrator" in the "Operation Guide VE".

Upgrade Installation
[Windows Manager]
Refer to steps 1 to 5 in the installation section in "2.1.1.6 Installation", 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] or enter "y".
The settings to be inherited from the earlier version will be displayed. After checking them, click [Confirm] or enter "y".
Upgrade installation will begin.
[Linux Manager]
Refer to steps 1 to 7 in the installation section in "2.1.2.6 Installation", 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
After upgrade installation is finished, restart the system in order to complete the upgrade.
Registration of license
When performing upgrade installation from the following products to Virtual Edition, it is necessary to register the license.
- RCVE
Access the ROR console, and register the license of Virtual Edition.
For the registration of the license, refer to the setting of the license of "Chapter 4 License Setup and Confirmation".

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 managed servers and the related services, refer to "5.2 Agent" in the "ServerView Resource Coordinator VE Setup Guide".

After the upgrade is complete, check that Resource Orchestrator is operating correctly, and then manually delete the folder that was used to back up the transferred data.
For the folder created to back up the transferred data, refer to "Transferred Data".

Transfer of the Manager Using Re-installation or the Pre-configuration Function

In the following cases, import system configuration files (import) and export system configuration files (export) using pre-configuration.

Transfer from RCVE manager to this version of ROR VE
Transfer of a cluster operated using RCVE manager to this version of ROR VE manager
Transfer of a cluster operated using ROR VE manager to this version of ROR VE manager
When the path of the installation folder before transfer is 46 characters or longer

Use the following procedure to perform "Transfer of the Manager Using Re-installation or the Pre-configuration Function".

See

For pre-configuration, refer to the following manuals:

[RCVE]

"Chapter 7 Pre-configuration" in the "ServerView Resource Coordinator VE Setup Guide"
"Appendix D Format of CSV System Configuration Files" in the "ServerView Resource Coordinator VE Setup Guide"

[ROR VE V3.0.0]

"Chapter 6 Pre-configuration" in the "ServerView Resource Orchestrator Virtual Edition V3.0.0 User's Guide"
"Appendix A Format of CSV System Configuration Files" in the "ServerView Resource Orchestrator Virtual Edition V3.0.0 User's Guide"

Also, when transferring the manager using the pre-configuration function, perform the following preparations and checks.

To confirm that transfer using the pre-configuration function 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.
When server switchover settings have been performed, it is not possible to transfer using the pre-configuration function when spare servers have been switched to. Perform restoration before starting transfer using the pre-configuration function.
For the restoration method, refer to the following manuals:
[RCVE]
- "Chapter 10 Server Switchover" in the "ServerView Resource Coordinator VE Operation Guide"
[ROR VE V3.0.0]
- "Chapter 10 Server Switchover" in the "ServerView Resource Orchestrator Virtual Edition V3.0.0 Operation Guide"
The following information will not be transferred. Reconfiguration is necessary when performing transfer using the pre-configuration function.
Record the following configuration information from the RC console or the ROR Console.
- User account information
- Registration status of the agent of each managed server, and maintenance mode settings
- Spare server settings
- Agent registration information of OVM for SPARC guest domains
Power consumption data
When monitoring of power consumption is being performed, collected power consumption data will not be transferred.
When the power consumption data is necessary, export it in CSV format.
For the export method, refer to the following manuals:
[RCVE]
- "13.2 Exporting Power Consumption Data" in the "ServerView Resource Coordinator VE Operation Guide"
[ROR VE V3.0.0]
- "13.2 Exporting Power Consumption Data" in the "ServerView Resource Orchestrator Virtual Edition V3.0.0 Operation Guide"

Note

Do not change the settings of the manager, agents, or any other hardware devices, or their configuration, until transfer using the pre-configuration function is complete.

Set Maintenance Mode
From the RC console of the RCVE manager, or the ROR console of ROR VE, place all managed servers into maintenance mode.
System Configuration File Export
Use the pre-configuration function to export a 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 following manuals:
[RCVE]
- "Chapter 7 Pre-configuration" in the "ServerView Resource Coordinator VE Setup Guide"
[ROR VE V3.0.0]
- "Chapter 6 Pre-configuration" in the "ServerView Resource Orchestrator Virtual Edition V3.0.0 User's Guide"
Backup (copy) Assets to Transfer
1. Back up (copy) certificates.
  Back up (copy) the following folders and directories:
  - RCVE Windows Manager
    Installation_folder\Manager\etc\opt\FJSVssmgr\current\certificate
    Installation_folder\Manager\etc\opt\FJSVrcxdm\certificate
    Installation_folder\Manager\sys\apache\conf\ssl.crt
    Installation_folder\Manager\sys\apache\conf\ssl.key
  - ROR VE 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
  - RCVE and ROR VE 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
2. Back up (copy) the folder containing the collected system images and cloning images 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:
  - RCVE Windows Manager
    Installation_folder\ScwPro\depot\Cloneimg
  - ROR VE Windows Manager
    Installation_folder\SVROR\ScwPro\depot\Cloneimg
  - RCVE and ROR VE 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.
3. Back up (copy) the following file.
  - Port Number Settings
    [Windows Manager]
    System_drive\WINDOWS\system32\drivers\etc\services
    [Linux Manager]
    /etc/services
  - Batch Files and Script Files for Event-related Functions
    RCVE Windows Manager
    Installation_folder\Manager\etc\trapop.bat
    ROR VE Windows Manager
    Installation_folder\SVROR\Manager\etc\trapop.bat
    Linux Manager
    /etc/opt/FJSVrcvmr/trapop.sh
Note
- When operating managers in clusters, the above folders or directories are stored on the shared disk. Check if files, folders, or directories stored in the above locations are correctly backed up (copied).
  The backup (copy) storage target can be set to be stored in a folder or directory on the shared disk other than "RCoordinator" or "SVROR" which are created during setup of the manager cluster service.
- When operating managers in clusters, the backup (copy) of folders or directories should be executed on the primary node.
- 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 following manuals:
  [RCVE]
  - "1.1.2.5 Dynamic Disk Space" in the "ServerView Resource Coordinator VE Installation Guide"
  [ROR VE V3.0.0]
  - "1.4.2.5 Dynamic Disk Space" in the "ServerView Resource Orchestrator Virtual Edition V3.0.0 Setup Guide"
  When there is no storage folder for system images and cloning images, this step is not necessary.
Uninstall Earlier Products or Managers of Earlier Versions
Refer to the "ServerView Resource Coordinator VE Installation Guide" or the "ServerView Resource Orchestrator Virtual Edition V3.0.0 Installation Guide", and uninstall the manager.
When operating managers in clusters, refer to the following manuals, delete the cluster service and uninstall the manager.
[RCVE]
- "Appendix B Manager Cluster Operation Settings and Deletion" in the "ServerView Resource Coordinator VE Installation Guide"
[ROR VE V3.0.0]
- "Appendix B Manager Cluster Operation Settings and Deletion" in the "ServerView Resource Orchestrator Virtual Edition V3.0.0 Installation Guide"
Note
- Do not perform "Delete servers" as given in the Preparations in the "ServerView Resource Coordinator VE Installation Guide" or the "ServerView Resource Orchestrator Virtual Edition V3.0.0 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 6 and perform reconfiguration from the ROR console.
Installation of Managers of This Version
Install managers of this version.
For installation, refer to "2.1 Manager Installation".
When operating managers in cluster environments, refer to "Appendix C Manager Cluster Operation Settings and Deletion", uninstall the manager and then configure the cluster services.
Note
- When installing managers, specify the same admin LAN as used for the RCVE manager on the [Admin LAN Selection] window.
- When the settings for restarting of managers have been changed, reconfigure the settings after the manager is installed, based on the information which was recorded during preparation. For details, refer to "Restarting Managers" in "Appendix A Notes on Operating ServerView Resource Orchestrator" in the "Operation Guide VE".
After installing managers, use the following procedure to restore the certificates and image file storage folder backed up (copied) in step 3.
1. Stop the manager.
  For the method for stopping managers, refer to "2.1 Starting and Stopping Managers" in the "Operation Guide VE".
2. 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\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.
3. 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
4. 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 "8.2 Changing Port Numbers" in the "User's Guide VE".
    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]
    /etc/opt/FJSVrcvmr/trapop.sh
5. Start the manager.
  For the methods for starting and stopping managers, refer to "2.1 Starting and Stopping Managers" in the "Operation Guide VE".
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 5 Managing User Accounts" in the "User's Guide VE".
Registration of license
Access the ROR console, and register the license of Virtual Edition.
For the registration of the license, refer to the setting of the license of "Chapter 4 License Setup and Confirmation".
Edit System Configuration Files
Based on the environment created for the RCVE manager, edit the system configuration file (CSV format) exported in 2.
Change the operation column of all resources to "new".
For how to edit system configuration files (CSV format), refer to "Appendix B Format of CSV System Configuration Files" in the "User's Guide VE".
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.
1. Import of the system configuration file
  Import the edited system configuration file.
  For the import method, refer to "12.2 Importing the System Configuration File" in the "User's Guide VE".
2. 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 7 Installing Software and Registering Agents on Managed Servers".
  After completing agent registration, use the ROR console to check that all physical OSs and VM hosts are displayed. When there are VM hosts (with VM guests) registered, check that all VM guests are displayed.
3. 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 Settings for Server Switchover" in the "User's Guide VE".
4. 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 7 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 (CSV format), refer to "Appendix B Format of CSV System Configuration Files" in the "User's Guide VE".
  Import the edited system configuration file.
  For the import method, refer to "12.2 Importing the System Configuration File" in the "User's Guide VE".
Set Maintenance Mode
Using the information recorded during preparation, place the managed serves placed into maintenance mode before the transfer using the pre-configuration function into maintenance mode again.
For maintenance mode settings, refer to "Appendix C Maintenance Mode" in the "User's Guide VE".

Note

When using backup system images or collecting cloning images without upgrading agents, either reboot managed servers after reinstallation of the manager or transfer using the pre-configuration function is completed, or restart the related services.

For restarting the Related Services, refer to "2.2 Starting and Stopping Agents" in the "Operation Guide VE".