Top
ServerView Resource Orchestrator Cloud Edition V3.2.0 Setup Guide
FUJITSU Software
Appendix C Upgrading from Earlier Versions > C.2 Manager
PreviousNext

C.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 "2.3.1 Maintaining Compatibility with Earlier Versions" in the "Release Notes", and change each setting.

[Windows Manager]

  • When upgrading an environment configured using an earlier version of ServerView Resource Coordinator to this version of FUJITSU Software ServerView Resource Orchestrator 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:

Also, with transfer using upgrade installation the following data is also transferred:

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]
Drive_name\Program Files (x86)\RCVE-upgradedata
installation_ folder\CE-upgrade
installation_ folder\CE-upgradedata

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


Preparations

Perform the following preparations and checks before upgrading:

[Windows Manager]


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 upgrade installation, do not close the installation window until the installation is complete.

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

  • When performing an upgrade installation, check that port number 80 is not listed in the "services" file. If it is listed, perform the following before starting the upgrade installation.

    • Disable any services in the "services" file that use port 80.

  1. Upgrade Installation

    [Windows Manager]

    Refer to steps 1 to 6 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 12 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.

  2. Transfer of Configuration Methods for the Dashboard (System Conditions) [Windows Manager]

    Only perform this procedure when performing an upgrade installation in an environment configured using an earlier version of ROR CE.

    When the upgrade installation is complete, perform the following procedure before restarting the server.

    1. Delete the "Vnnnn" section from the file names of the two files below, and then copy them to the destination folder.
      There are files with the same names in the destination folder, so overwrite them.

      • Source files:

        Installation_folder\CE-upgradedata\SQCM\data\sqc_backup\remoteAccountVnnnn.txt
        Installation_folder\CE-upgradedata\SQCM\data\sqc_backup\remoteAgentVnnnn.txt

      * Note: Vnnnn is a number with 3 - 4 digits. Check in an upgrade installation environment.

      • Destination folder:

        Installation_folder\SQC\sqc_data\control

    2. Execute the following command and enable the settings. 

      Installation_folder\SQC\sqcm\bin\sqcSetPolicy.exe

  3. Register Certificates [Windows Manager]

    Only perform this procedure when performing an upgrade installation in an environment configured using an earlier version of ROR CE.

    Perform this after the upgrade installation is complete.

    1. Stop the ROR manager.
      Execute the following command to stop the manager.

      Installation_folder\SVROR\Manager\bin\rcxmgrctl stop

    2. Change the name of the folder.
      Change the name of the following folder, and back it up.

      Before changing: Installation_folder\IAPS\smee
      After changing: Installation_folder\IAPS\smee_bak

    3. Register the certificates from before the upgrade.
      Execute the following command to register the certificates from before the upgrade with ROR.

      Installation_folder\RCXCTMG\Operation\bin\createTestCert.bat FQDN_of_the_admin_server

    4. If registration is successful, the following folder will be re-created, so the folder backed up in step b can be deleted.

      Installation_folder\IAPS\smee

  4. Restarting after Upgrade Installation is Finished

    After upgrade installation is finished, restart the system in order to complete the upgrade.

  5. 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 "2.3.1.1 Overcommit Definition Files" in the "Release Notes".

  6. Registration of license

    When performing upgrade installation from the following products to Cloud Edition, it is necessary to register the license.

    • RCVE

    • ROR VE

    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 4 License Setup and Confirmation".

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

    1. Check the physical L-Server templates which need to be transferred.

      Templates that have Physical for TYPE and '-' for NICS are the targets of transfer. 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

    2. Export the physical L-Server templates which need to be transferred.

      The following is an example using the template name 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

    3. Edit the file exported in b. Set a value larger than 1 for NumOfNIC (the following example uses 2). If the NICs tag is not displayed, add the NICs tag.
      If a NIC tag and a NICIndex tag are displayed, 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.

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

    5. Check that a value larger 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              -
sample_small        Virtual     1.0GHz,1,1.0GB      20.0GB              1

  8. Usage Charge Calculation Feature Settings

    This section describes the usage charge calculation feature settings.

    If an upgrade installation is performed, pre-upgrade settings are retained. To use the post-upgrade usage charge calculation feature, configure the following, according to the pre-upgrade version.
    Restart the manager for the definition file settings to take effect. Refer to Section "2.1 Starting and Stopping Managers" in the "Operation Guide CE" for information on starting the manager.

    Location of the Definition File

    [Windows Manager]
    Installation_folder\RCXCTMG\Charging\conf

    [Linux Manager]
    /etc/opt/FJSVctchg/conf/

    Definition File Name

    accounting.properties

    Definition File Format

    Describe each line of the definition file in the following format:

    accounting.calculate.sys.disk=yes
accounting.calculate.snapshot=yes
gui.identifier.server=name
gui.identifier.disk=name
    Definition File Items
    Table C.1 List of Items

    Version before upgrade

    Item Name

    Description

    V3.1.0 or V3.1.0A

    accounting.calculate.sys.disk

    From V3.1.1, it is possible to set billing and tally usage charges at the system disk level, separately from L-Server images. When billing system disks separately from L-Server images, add the following row:
    accounting.calculate.sys.disk=yes

    Note that in an environment where system disk units are included in L-Server image products, change the settings carefully for product units, paying special attention to the applicable periods for product units and tenant cut-off dates so that there is no double charging for system disks.
    Refer to Section "15.3.2 Modify Accounting Information" in the "Operation Guide CE" for information on reconfiguring product unit prices.

    V3.1.0 or V3.1.0A

    gui.identifier.server

    From V3.1.1, the server name specified in the L-Platform management, not the internal ID, can be displayed as the identification information for the virtual or physical server in the [Usage Charge Detail] window. To display the server name, add the following row:
    gui.identifier.server=name

    V3.1.0 or V3.1.0A

    gui.identifier.disk

    From V3.1.1, the disk name specified in the L-Platform management, not the internal ID, can be displayed as the identification information for the data disk capacity in the [Usage Charge Detail] window. To display the disk name, add the following row:
    gui.identifier.disk=name

    V3.1.1

    accounting.calculate.snapshot

    From V3.1.2, it is possible to set and tally usage charges at the snapshot level for virtual L-Servers.
    When billing for snapshots, add the following row:
    accounting.calculate.snapshot=yes

    Note that in an environment where snapshot units are included in L-Server image products, change the settings carefully for product units, paying special attention to the applicable periods for product units and tenant cut-off dates so that there is no double charging for snapshots. Refer to "15.3.2 Modify Accounting Information" in the "Operation Guide CE" for information on changing the product unit settings.

  9. Backup

    When using the backup and restoration function of the admin server, save the resources after completion of the upgrade installation by performing an offline backup. If you choose to backup online, use a base backup.
    For details, refer to "10.1 Backup and Restoration of Admin Servers" in the "Operation Guide CE".

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 "2.2 Starting and Stopping Agents" in the "Operation Guide CE".

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

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.

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.

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

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

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

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

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

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

    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 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 Administrators (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]
        /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 CE".

  6. 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 and Customizing Roles" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

  7. 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 4 License Setup and Confirmation".

    Use SSL communications when accessing the ROR console from a browser.
    When replacing the certificate used for SSL communication from the test certificate created by default with another certificate, refer to "Chapter 3 SSL Communication Environment Settings for the ROR Console".

  8. Edit System Configuration Files

    Based on the environment created for the 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 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 ("-").

  9. 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 "8.2 Installing Software and Registering Agents on VM Hosts" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

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

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

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

PreviousNext
Copyright 2010-2016 FUJITSU LIMITED