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

When maintaining compatibility with earlier versions, refer to "G.1 Maintaining Compatibility with Earlier Versions", and change each setting.

[Windows Manager]

When upgrading an environment configured using an earlier version of ServerView Resource Coordinator to this version of ServerView Resource Coordinator Cloud 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 is created and stored in the following folder. Ensure that the folder is not deleted until after the upgrade is complete.

[Windows Manager]
32-bit (x86) OS
Drive_name\Program Files\RCVE-upgradedata
64-bit (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

Note

The total disk space of the following folders plus 100 MB 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 Manager]

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

If ETERNUS SF Storage Cruiser Manager or ETERNUS SF AdvancedCopy Manager is installed, stop the service or daemon for each of them (the service starts even if a license has not been registered). Refer to the manuals for information on how to stop the services and daemons.
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
Stop the BMC BladeLogic Server Automation service if it is in use. Refer to "Required Software Preparation and Checks" in "2.1.1 Preparations" for information on how to stop the service.

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 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 restore the system that was backed up during the preparations and then perform upgrade installation again.
If the problem cannot be resolved and upgrade installation fails again, please contact Fujitsu technical staff.
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.
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.
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.

Upgrade Installation
[Windows Manager]
Refer to steps 1. to 5 and Point in the installation section in "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 steps 1. to 11 and Point in the installation section in "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
After upgrade installation is finished, restart the system in order to complete the upgrade.
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".
Configure a Single Sign-On Environment
When performing upgrade installation from the following products to Cloud Edition, configuration of a "Single Sign-On environment" is necessary.
- Earlier version of ROR
- Earlier version of ROR Express
- Earlier version of ROR VE
- This version of ROR Express
- This version of ROR VE
After this step, refer to "12.5 Updating from Earlier Versions" in the "Design Guide CE", and configure a Single Sign-On environment.
When upgrading from ROR V3.0.0 to Cloud Edition this procedure is not necessary.

Transfer of L-Server templates of ROR V2.3.0

When performing upgrade installation of an admin server that is ROR V2.3.0, execute the following command to transfer the physical L-Server templates.

Check the physical L-Server templates which are necessary to transfer.

It is neccssary to transfer the template which has Physical for TYPE and '-' for NICS.

For details on the rcxadm template command, refer to "8.1 rcxadm template" in the "Reference Guide (Command/XML) CE".

[Windows Manager]
Installation_folder\SVROR\Manager\bin\rcxadm template list

[Linux Manager]
/opt/FJSVrcvmr/bin/rcxadm template list

NAME                TYPE        SPEC/MODEL          DISKS               NICS
----                ----        ----------          -----               ----
sample_large        Virtual     2.0GHz,2,4.0GB      40.0GB,40.0GB       2
sample_medium       Virtual     2.0GHz,1,2.0GB      40.0GB              1
sample_physical     Physical    "PRIMERGY BX922 S2" 40.0GB              -
sample_small        Virtual     1.0GHz,1,1.0GB      20.0GB              1

Export the physical L-Server template which is necessary to transfer
The following is an example of sample_physical.
You can use an arbitrary file name for samplefile.xml.
[Windows Manager]
Installation_folder\SVROR\Manager\bin\rcxadm template export -name sample_physical -file samplefile.xml
[Linux Manager]
/opt/FJSVrcvmr/bin/rcxadm template export -name sample_physical -file samplefile.xml

Edit the file exported in step b. Set more than 1 for NumOfNIC (the following example is 2).

If NICs tag does not exist, add NICs tag.
If a NIC tag and a NICIndex tag are output, no corrective action is necessary.

<LServerTemplate name='sample_physical' label='sample of physical template' id='xxxxxx'>
  <ServerType>Physical</ServerType>
  <Model>PRIMERGY BX922 S2</Model>
  <Disks>
    <Disk type='FC'>
      <DiskIndex>0</DiskIndex>
      <DiskSize>40.0</DiskSize>
    </Disk>
  </Disks>
  <NICs>
    <NumOfNIC>2</NumOfNIC>
  </NICs>
  <Policy>
    <Redundancy>None</Redundancy>
  </Policy>
</LServerTemplate>

Note

If you edit and save a UTF-8 text file using Windows Notepad, the Byte Order Mark (BOM) is stored in the first three bytes of the file, and the information specified on the first line of the file will not be analyzed correctly. When using Notepad, specify the information from the second line.

Overwrite the template by importing the edited file.
[Windows Manager]
Installation_folder\SVROR\Manager\bin\rcxadm import -file samplefile.xml -force
[Linux Manager]
/opt/FJSVrcvmr/bin/rcxadm import -file samplefile.xml -force

Check that more than 1 is displayed for NICS in the transferred physical L-Server template.

[Windows Manager]
Installation_folder\SVROR\Manager\bin\rcxadm template list

[Linux Manager]
/opt/FJSVrcvmr/bin/rcxadm template list

NAME                TYPE        SPEC/MODEL             DISKS               NICS
----                ----        ----------             -----               ----
sample_large        Virtual     2.0GHz,2,4.0GB         40.0GB,40.0GB       2
sample_medium       Virtual     2.0GHz,1,2.0GB         40.0GB              1
sample_physical     Physical    "PRIMERGY BX922 S2"    40.0GB              2
sample_small        Virtual     1.0GHz,1,1.0GB         20.0GB              1

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

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 CE
Transfer of a cluster operated using RCVE manager to this version of ROR CE manager
Transfer of a cluster operated using ROR VE manager to this version of ROR CE 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 Orchestrator 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 V3.0 Virtual Edition User's Guide"
"Appendix D 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
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 Orchestrator Setup Guide"
[ROR VE V3.0.0]
- "Chapter 6 Pre-configuration" in the "ServerView Resource Orchestrator V3.0 Virtual Edition User's Guide"
Back up (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 back up (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 Orchestrator 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".
Note
When installing managers, specify the same admin LAN as used for the RCVE manager 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.
1. Stop the manager.
  For the method for stopping managers, refer to "2.1 Starting and Stopping the Manager" in the "Operation Guide CE".
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 "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]
    Installation_folder\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 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 manager, edit the system configuration file (CSV format) exported in step 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 for Infrastructure Administrators (Resource Management) CE".
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 "10.2 Importing the System Configuration File" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
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 11 Installing Software and Registering Agents on VM Hosts".
  After completing agent registration, use the ROR console to check that all 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 Server Switchover Settings" 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 step 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 for Infrastructure Administrators (Resource Management) CE".
  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 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 for Infrastructure Administrators (Resource Management) CE".
Manager Setup
It is necessary to confirm whether Single Sign-On has been configured before performing setup of the manager.
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".
After completing transfer of a manager of this version of ROR CE using the pre-configuration function, setup of the manager is necessary.
Registration of license
Access the ROR console, 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".
Use SSL communications when accessing the ROR console from a browser.
When changing the certificate used for SSL communication from the test certificate set up by default to another certificate, 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 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 an Agent" in the "Operation Guide CE".