This section explains the software requirements for installation of Resource Orchestrator.
The basic software listed below is required when using Resource Orchestrator.
Required Basic Software
Basic Software (OS) | Remarks |
|---|---|
Microsoft(R) Windows Server(R) 2003 R2, Standard Edition | SP2 or later supported. |
Microsoft(R) Windows Server(R) 2008 Standard (x86, x64) | The Server Core installation option is not supported. In clustered manager configurations, as Microsoft Failover Cluster (MSFC) is used, Enterprise or Datacenter is required. |
Microsoft(R) Windows Server(R) 2012 Standard | The Server Core installation option is not supported. |
* Note: This service also can be run on a VM guest OS as virtualization software.
Basic Software (OS) | Remarks |
|---|---|
Red Hat(R) Enterprise Linux(R) 5.0 (for x86) | Prepare any required driver kits, update kits, or software. For information about required software, refer to the manual of the server or the Linux installation guide. About required packages, refer to "6.1.1.3 Required Packages". The Linux Kernel version for each hardware model corresponds to the version supported by Fujitsu. |
*1: This service also can be run on a VM guest OS as virtualization software.
*2: Use the internal authentication function.
Basic Software (OS) | Remarks |
|---|---|
Microsoft(R) Windows Server(R) 2003, Standard Edition | SP2 supported. |
Microsoft(R) Windows Server(R) 2003 R2, Standard Edition | SP2 or later supported. |
Microsoft(R) Windows Server(R) 2008 Standard (x86, x64) | The Server Core installation option is not supported. |
Microsoft(R) Windows Server(R) 2012 Standard | The Server Core installation option is not supported. |
Basic Software (OS) | Remarks |
|---|---|
Microsoft(R) Windows Server(R) 2008 Standard (x64) | The Server Core installation option is not supported. |
Basic Software (OS) | Remarks |
|---|---|
Red Hat(R) Enterprise Linux(R) AS (v.4 for x86) | Prepare any required driver kits, update kits, or software. About required packages, refer to "6.1.1.3 Required Packages". The Linux Kernel version for each hardware model corresponds to the version supported by Fujitsu. |
* Note: When using the PRIMEQUEST series, RHEL7 is not supported.
Basic Software (OS) | Remarks |
|---|---|
Solaris(TM) 10 Operating System |
When using SAN boot, refer to the manual for Fibre Channel card driver, "SPARC Enterprise - ETERNUS SAN Boot Environment Build Guide". |
* Note: Management using the following functions of Solaris 11.2 is not possible.
Centralized management of clouds using OpenStack
Independent and isolated environments using kernel zones
Software-defined networking - elastic virtual switches
Immutable global zones
Basic Software (OS) | Remarks |
|---|---|
Solaris(TM) 11 Operating System | When using SAN boot, refer to the manual for Fibre Channel card driver, "SPARC Enterprise - ETERNUS SAN Boot Environment Build Guide". When a guest domain on OVM for SPARC is registered as a VM Host, it is necessary to install an agent in that guest domain. |
Basic Software (OS) | Remarks |
|---|---|
VMware vSphere 4.0 | Install Resource Orchestrator on the VMware ESX host. Use the VMware Service Console for installation. (*) |
* Note: VMware ESXi of VMware vSphere 4.0 or earlier cannot be used for managed servers.
VMware ESXi of VMware vSphere 4.1 or later can be used for managed servers.
There is no need to install Resource Orchestrator on VMware ESXi, but agents must be registered.
Basic Software (OS) | Remarks |
|---|---|
Citrix(R) XenServer(R) 5.5 | - |
Basic Software (OS) | Remarks |
|---|---|
Red Hat(R) Enterprise Linux(R) 5.4 (for x86) | - |
Basic Software (OS) | Remarks |
|---|---|
Red Hat(R) Enterprise Linux(R) 6.2 (for Intel64) | Intel64 and AMD64 are supported. (*) |
* Note: For details, refer to the following section in the "Red Hat Enterprise Linux 6 Virtualization Host Configuration and Guest Installation Guide".
Chapter 2. System requirements
URL: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Host_Configuration_and_Guest_Installation_Guide/index.html |
The manuals for Red Hat Enterprise Linux can be referred to from the following URL.
URL: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/index.html |
Basic Software (OS) | Remarks |
|---|---|
Microsoft(R) Windows Server(R) 2003 R2, Standard Edition | SP2 or later supported. |
Microsoft(R) Windows Server(R) 2008 Standard (x86, x64) | The Server Core installation option is not supported. |
Microsoft(R) Windows Server(R) 2012 Standard | The Server Core installation option is not supported. |
Microsoft(R) Windows Vista(R) Business | - |
Microsoft(R) Windows(R) 7 Professional | - |
Windows(R) 8 Pro | - |
* Note: This service also can be run on a VM guest OS as virtualization software.
Basic Software (OS) | Remarks |
|---|---|
Red Hat(R) Enterprise Linux(R) 5.3 (for x86) | Prepare any required driver kits, update kits, or software. For information about required software, refer to the manual of the server or the Linux installation guide. About required packages, refer to "6.1.1.3 Required Packages". The Linux Kernel version for each hardware model corresponds to the version supported by Fujitsu. |
* Note: This service also can be run on a VM guest OS as virtualization software.
Note
[VMware]
The free version of VMware ESXi cannot be used for managed servers.
When using VMware ESXi for managed servers, purchase the appropriate license.
Installation will fail when a Resource Orchestrator agent is installed on an unsupported OS.
[Hyper-V]
When using Hyper-V on managed servers, the only supported OS of the admin server is Windows.
[Xen]
When using RHEL5-Xen on managed servers, the only supported OS of the admin server is Linux.
Required Basic Software: Admin Clients
It is not necessary to install Resource Orchestrator on admin clients, but the following basic software is required.
Basic Software (OS) | Remarks |
|---|---|
Microsoft(R) Windows Vista(R) Business | SP1 or later supported. |
Microsoft(R) Windows(R) 7 Professional | - |
Windows(R) 8 Pro | - |
Windows(R) 10 Pro | - |
Microsoft(R) Windows Server(R) 2003 R2, Standard Edition | SP2 or later supported. |
Microsoft(R) Windows Server(R) 2008 Standard (x86, x64) | The Server Core installation option is not supported. |
Microsoft(R) Windows Server(R) 2012 Standard | - |
When using Resource Orchestrator, the following patches are required.
Basic Software (OS) | Patch ID/Bundle Update |
|---|---|
Microsoft(R) Windows Server(R) 2003 R2, Standard x64 Edition | Hotfix KB942589 (*) |
Microsoft(R) Windows Server(R) 2003 R2, Enterprise x64 Edition | Hotfix KB942589 (*) |
* Note: Necessary when managing a managed server within a separate subnet to the admin server.
Basic Software (OS) | Patch ID/Bundle Update (*) |
|---|---|
Red Hat(R) Enterprise Linux(R) 5 (for x86) | Bundle Update U09031 (5.3 compatible) |
Red Hat(R) Enterprise Linux(R) 5 (for Intel64) | Bundle Update U09031 (5.3 compatible) |
* Note: Necessary when upgrading.
Basic Software (OS) | Patch ID/Bundle Update |
|---|---|
Microsoft(R) Windows Server(R) 2008 | Hotfix KB2487376 (*) |
Microsoft(R) Windows Server(R) 2008 R2 | Hotfix KB2344941 (*) |
Microsoft(R) Windows Server(R) 2008 R2 SP1 | Hotfix KB2550978 (*) |
Necessary when using server switchover to a spare server on a managed server that is one of the following models:
PRIMERGY BX920 S3 or later
PRIMERGY BX924 S3 or later
PRIMERGY BX2560 M1 or later
PRIMERGY BX2580 M1 or later
PRIMERGY RX200 S7 or later
PRIMERGY RX300 S7 or later
PRIMERGY RX2520 M1 or later
PRIMERGY RX2530 M1 or later
PRIMERGY RX2540 M1 or later
PRIMERGY RX4770 M1 or later
Basic Software (OS) | Patch ID/Bundle Update |
|---|---|
None | - |
Basic Software (OS) | Patch ID/Bundle Update (*) |
|---|---|
Red Hat(R) Enterprise Linux(R) 5 (for x86) | Bundle Update U07121 (5.1 compatible) |
Red Hat(R) Enterprise Linux(R) 5 (for Intel64) | Bundle Update U07121 (5.1 compatible) |
Red Hat(R) Enterprise Linux(R) AS (v.4 for x86) | Bundle Update U06091 (Update 4 compatible) |
Red Hat(R) Enterprise Linux(R) ES (v.4 for x86) | Kernel Update kit (Update4/4.5/4.6/4.7/4.8 compatible) |
Red Hat(R) Enterprise Linux(R) AS (v.4 for EM64T) | Bundle Update U06091 (Update 4 compatible) |
Red Hat(R) Enterprise Linux(R) ES (v.4 for EM64T) | Kernel Update kit (Update4/4.5/4.6/4.7/4.8 compatible) |
SUSE Linux Enterprise Server 10 SP3 (for AMD64, Intel64) | Kernel-2.6.16.60-0.50.1 or later |
SUSE Linux Enterprise Server 11 (for x86) | Kernel-2.6.27.19-5 or later |
SUSE Linux Enterprise Server 11 (for AMD64, Intel64) | Kernel-2.6.27.19-5 or later |
SUSE Linux Enterprise Server 11 SP1 (for x86) | Kernel-2.6.32 or later |
SUSE Linux Enterprise Server 11 SP1 (for AMD64, Intel64) | Kernel-2.6.32 or later |
* Note: Necessary when upgrading.
Basic Software (OS) | Patch ID/Bundle Update |
|---|---|
Solaris(TM) 11 Operating System | SRU12111(SRU1.4) or later (*) |
* Note: Required when using OVM for SPARC for a managed server.
Basic Software (OS) | Patch ID/Bundle Update |
|---|---|
None | - |
Basic Software (OS) | Patch ID/Bundle Update |
|---|---|
None | - |
Basic Software (OS) | Patch ID/Bundle Update |
|---|---|
None | - |
Basic Software (OS) | Patch ID/Bundle Update (*) |
|---|---|
Red Hat(R) Enterprise Linux(R) 5 (for x86) | Bundle Update U09031 (5.3 compatible) |
Red Hat(R) Enterprise Linux(R) 5 (for Intel64) | Bundle Update U09031 (5.3 compatible) |
* Note: Necessary when upgrading.
The packages listed below are required when using Resource Orchestrator.
Install the required packages beforehand, if necessary.
The architecture of the required packages to be installed is shown enclosed by parenthesis "()".
For the packages followed by "(32bit)", install either the i386 or i686 package.
For the items with no architecture to be installed is specified, install the package of the same architecture as the OS.
Conditions | Required Packages |
|---|---|
Always required | alsa-lib(32bit) |
Necessary when managing a managed server within a separate subnet to the admin server | openldap |
* Note: For openssl(32bit) and openssl098e(32bit), install the latest package.
Conditions | Required Packages |
|---|---|
Always required | apr(32bit) |
Necessary when managing a managed server within a separate subnet to the admin server | glibc |
* Note: For openssl(32bit), install the latest package.
Conditions | Required Packages |
|---|---|
Always required | alsa-lib(32bit) |
Conditions | Required Packages |
|---|---|
Always required | alsa-lib(32bit) |
[KVM]
| fuse.x86_64
|
[KVM]
| libguestfs-tools.x86_64 For RHEL6.2, the following packages are necessary. guestfish.x86_64 |
* Note: Obtain libguestfs-winsupport from the "RHEL V2VWIN (v. 6 for 64-bit x86_64)" channel for Red Hat Network.
For details, refer to the following section in the "Virtualization Administration Guide".
Chapter 16. Guest virtual machine disk access with offline tools
URL: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Administration_Guide/index.html |
The manuals for Red Hat Enterprise Linux can be referred to from the following URL.
URL: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/index.html |
Conditions | Required Packages |
|---|---|
Always required | alsa-lib(32bit) |
Conditions | Required Packages |
|---|---|
Always required | alsa-lib(32bit) |
* Note: Install an OS, specifying a package.
Conditions | Required Packages |
|---|---|
Always required | alsa-lib(32bit) |
* Note: Install an OS, specifying a package.
The software listed below is required when using Resource Orchestrator.
Required Software (Windows Manager)
The required software for Windows manager is as follows:
Unless specified otherwise, install on the same server as the manager.
When the ROR console is started on Windows manager, the required software of the admin client is also necessary.
Required Software | Version | Remarks |
|---|---|---|
ServerView Operations Manager (*1) | V4.20.25 - V7.02 | Necessary when using VIOM coordination or invoking the Web UI of server management software from the ROR console. |
V5.30 - V7.02 | Necessary when using VMware ESXi as a managed server, or Single Sign-ON. | |
Microsoft(R) LAN Manager module | - | Used when performing backup and restore, or cloning for physical servers. |
BACS | - | Necessary when performing redundancy of the admin LAN for admin servers. When using PRIMECLUSTER GLS, also apply the latest patches for GLS. |
ServerView Virtual-IO Manager | 2.6 or later | Necessary when using VIOM's Virtual I/O. |
Microsoft(R) Windows Server(R) 2008 Enterprise (x86, x64) Failover Cluster (MSFC) | - | Required when admin servers are in a cluster configuration. |
VMware vCenter Server | 4.0 | Required when using migration of VM guests on VMware. |
Microsoft(R) System Center Virtual Machine Manager 2008 R2 | - | Required when using migration, or setting or releasing VM maintenance mode of VM guests on Hyper-V. |
Windows PowerShell | 2.0 or later | Required when using migration, or setting or releasing VM maintenance mode of VM guests on Hyper-V. |
SNMP Service | - | Necessary for ServerView Operations Manager. |
SNMP Trap Service (Standard OS service) | - | Necessary for ServerView Operations Manager. |
DHCP Server (Standard OS service) | - | Necessary when managing a managed server within a separate subnet to the admin server. |
ETERNUS SF Storage Cruiser Manager | 14.2 or later (*3) | Necessary when using the storage affinity switchover method for server switchover.
|
BMC BladeLogic Server Automation | 8.0 or later | Necessary when using coordination of registration and deletion of managed servers, cloning, and software deployment in PRIMERGY and PRIMEQUEST. |
BMC BladeLogic Server Automation Console | 8.0 or later | Necessary when using coordination of registration and deletion of managed servers, cloning, and software deployment in PRIMERGY and PRIMEQUEST. |
Microsoft Visual C++ 2008 Redistributable Package (x86) | - | Necessary to use V3.2.0 (T011582WP-01) or later. |
*1: When installing managers in cluster environments, installation on both the primary and secondary nodes is necessary.
*2: Obtain it from the following Microsoft FTP site.
Microsoft FTP site
URL: ftp://ftp.microsoft.com/bussys/clients/msclient/dsk3-1.exe |
*3: When the OS of the agent is Solaris 11 11/11 or later, use 15.1 or later.
Required Software (Linux Manager)
Required Software for Linux Manager is as follows.
Unless specified otherwise, install on the same server as the manager.
Required Software | Version | Remarks |
|---|---|---|
ServerView Operations Manager | V4.81.05 - V7.00 | Necessary when viewing the server management software Web UI from the ROR console. |
V5.30 - V7.00 | Necessary when using VMware ESXi as a managed server, or Single Sign-On. | |
Microsoft(R) LAN Manager module | - | Necessary when using backup and restore, or cloning. For how to install it, refer to "Microsoft LAN Manager Module" in "2.1.2.2 Software Preparation and Checks" in the "Setup Guide VE". |
ServerView Virtual-IO Manager | 2.6 or later | Necessary when using VIOM's Virtual I/O. |
VMware vCenter Server | 4.0 | Required when using migration of VM guests on VMware. |
PRIMECLUSTER Enterprise Edition | 4.2A00 or later | When an admin server is in a cluster configuration, one of the following software is necessary. |
PRIMECLUSTER HA Server | 4.2A00 or later | |
PRIMECLUSTER GLS | - | Necessary when performing redundancy of the admin LAN for admin servers. |
ETERNUS SF Storage Cruiser Manager | 14.2 or later (*3) | Necessary when using the storage affinity switchover method for server switchover.
|
DHCP Server (Standard OS service) | - | Necessary when managing a managed server within a separate subnet to the admin server. |
BMC BladeLogic Server Automation | 8.0 or later | Necessary when using coordination of registration and deletion of managed servers, cloning, and software deployment in PRIMERGY and PRIMEQUEST. |
BMC BladeLogic Server Automation Console | 8.0 or later | Necessary when using coordination of registration and deletion of managed servers, cloning, and software deployment in PRIMERGY and PRIMEQUEST. |
*1: Obtain it from the following Microsoft FTP site.
Microsoft FTP site
URL: ftp://ftp.microsoft.com/bussys/clients/msclient/dsk3-1.exe |
*2: Check the following VMware manuals:
URL: https://www.vmware.com/jp/support/support-resources/pubs/ |
*3: When the OS of the agent is Solaris 11 11/11 or later, use 15.1 or later.
Required Software (Agent)
Required Software | Version | Remarks |
|---|---|---|
ServerView Agents for Windows (*1) | V4.50.05 or later | Required for collecting and managing server information of PRIMERGY and PRIMEQUEST. |
"setupcl.exe" module | - | Necessary when using backup and restore, or cloning. When using Windows Server 2008 or later, the modules are already configured in the OS so there is no need to obtain new modules. |
BACS | - | Necessary when performing redundancy of the admin LAN and public LAN for managed servers. When using PRIMECLUSTER GLS, also apply the latest patches for GLS. |
*1: When installing managers in cluster environments, installation on both the primary and secondary nodes is necessary.
*2: The necessary files vary depending on the CPU architecture (x86, x64) of the target system, and the OS version. Please refer to the Microsoft web site for the module to obtain.
Microsoft download web site
URL(x86): URL(x64): |
After obtaining the latest version of module, place it in a work folder (such as C:\temp) of the system for installation and execute it.
For how to execute it, refer to "2.1.1.2 Software Preparation and Checks" in the "Setup Guide VE".
The module is not necessary after installation of agents.
Required Software | Version | Remarks |
|---|---|---|
ServerView Agents for Linux | V4.90.14 or later | Required for collecting and managing server information of PRIMERGY and PRIMEQUEST. |
Required Software | Version | Remarks |
|---|---|---|
PRIMECLUSTER GLS | 4.2A00 or later | Necessary when performing redundancy of the admin LAN and public LAN for managed servers. |
Required Software | Version | Remarks |
|---|---|---|
PRIMECLUSTER GLS | 4.2 or later | Necessary when performing redundancy of the admin LAN and public LAN for managed servers. |
Oracle VM Server for SPARC Software | 3.0 or later | Required when using the control domain of OVM for SPARC for an agent. |
Required Software | Version | Remarks |
|---|---|---|
ServerView Agents for VMware | V4.30-20 or later | Required for collecting and managing server information of PRIMERGY and PRIMEQUEST. |
ServerView ESXi CIM Provider | 1.00 or later | Necessary when using VMware ESXi as a managed server. |
Required Software | Version | Remarks |
|---|---|---|
ServerView Agents for Linux | V4.81-14 or later | Required for collecting and managing server information of PRIMERGY and PRIMEQUEST. |
Required Software (HBA address rename Setup Service)
Required Software | Version | Remarks |
|---|---|---|
Internet Explorer | 8 | Necessary for displaying the online help. |
Required Software | Version | Remarks |
|---|---|---|
Firefox | 3 | Necessary for displaying the online help. |
Required Software: Admin Clients
The following software is necessary for admin clients.
Required Software | Version | Remarks |
|---|---|---|
Internet Explorer | 8 (*1) | Internet Explorer or Firefox is required to display the ROR console. When using Windows 10, Microsoft(R) Edge cannot be used. |
Firefox | ESR24 | |
Java(TM) 2 Runtime Environment Standard Edition | (*5) | Necessary for displaying the management window of ServerView Operations Manager or the VM management console, on admin clients. |
VMware Virtual Infrastructure Client | 2.0 | [VMware] |
VMware vSphere Client | 4.0 | |
Hyper-V Manager | - | [Hyper-V] |
Microsoft(R) System Center Virtual Machine Manager 2008 R2 VMM Admin Console | - | [Hyper-V] |
XenCenter | - | [Citrix Xen] |
*1: Cannot be used by the NetworkViewer. Use another browser.
*2: When connecting with the ROR Console, use Compatibility View Settings.
*3: Only Internet Explorer (Desktop version) is supported.
*4: Set the resolution of the browser window as 100%.
*5: To display the management window of ServerView Operations Manager, please refer to the ServerView Operations Manager manual.
To display the VM management console or the console window, version 1.5 or later is necessary.
See
Installation of Related ServerView Products
For advisory notes regarding the installation of the manager of "ServerView Operations Manager", refer to "Required settings for ServerView Operations Manager 4.X for Windows" in "2.1.1.2 Software Preparation and Checks" in the "Setup Guide VE".
Resource Orchestrator cannot be used in combination with Resource Coordinator, Resource Orchestrator, or the following products.
ServerView Resource Coordinator VE is the old name of this product. Earlier versions cannot be used in combination with Resource Orchestrator, but upgrading is possible. For upgrading, refer to "Appendix D Upgrading from Earlier Versions" in the "Setup Guide VE".
Software | Product Name |
|---|---|
[Windows Manager] | ServerView Installation Manager (*1) |
ServerView Deployment Manager | |
[Linux Manager] | Server System Manager |
Agent [Windows] [Hyper-V] | Server System Manager |
ServerView Deployment Manager (*2) | |
Agent [Linux] | Server System Manager |
ServerView Deployment Manager (*2) | |
Agent [Solaris] [Solaris Zones] [OVM for SPARC] | Server System Manager (Manager only) |
Agent [VMware] | ServerView Deployment Manager (*2) |
Agent [Xen] [Citrix Xen] [KVM] | ServerView Deployment Manager (*2) |
HBA address rename setup service [Windows] | ServerView Deployment Manager |
HBA address rename Setup Service [Linux] | Server System Manager |
*1: As managers of Resource Orchestrator include PXE server, use in combination with the PXE server required for remote installation of ServerView Installation Manager is not possible.
*2: ServerView Deployment Manager can be installed after Resource Orchestrator has been installed. For details on installation, refer to "2.2 Agent Installation" in the "Setup Guide VE".
Note
When using an Active Directory domain controller as an admin server, it can be installed by promoting it to a domain controller after manager installation.
Resource Orchestrator managers contain some functions of DHCP servers and PXE servers. Do not use products or services that use the functions of other DHCP servers or PXE servers on the admin server.
However, such products or services can be placed in the same network as Resource Orchestrator managers. In this case, configure the managed server for Resource Orchestrator to be excluded from being managed by any other DHCP server.
Examples of Products Including DHCP Servers and PXE Servers
The Windows Server 2003 "Remote Installation Service", and the Windows Server 2012/Windows Server 2008/Windows Server 2003 "Windows Deployment Service"
ADS (Automated Deployment Services) of Windows Server 2003
Boot Information Negotiation Layer (BINLSVC)
ServerView Deployment Manager (*)
ServerStart (when using the remote installation function)
ServerView Installation Manager
Solaris JumpStart
* Note: As PXE server is included, the use of some functions is restricted when it is used on the same admin LAN as FUJITSU Software ServerView Resource Orchestrator. For details, refer to "A.3 Co-Existence with ServerView Deployment Manager" in the "Setup Guide VE".
Resource Orchestrator managers contain some functions of TFTP servers.
On manager, do not use the OS standard TFTP services.
[Physical Servers]
Contact Fujitsu technical staff for information about ServerView Deployment Manager.
The size of the required static disk space does not increase even after Resource Orchestrator is operated.
When using Resource Orchestrator, the disk space described in "6.1.1.7 Dynamic Disk Space" is required for each folder, in addition to the static disk space.
The amount of disk space may vary slightly depending on the environment in question.
Software | Folder | Disk Space (Unit: MB) |
|---|---|---|
[Windows Manager] | Installation_folder (*) | 2000 |
[Linux Manager] | /opt | 1000 |
/etc/opt | 30 | |
/var/opt | 900 | |
Agent [Windows] [Hyper-V] | Installation_folder (*) | 140 |
Agent [Linux] [VMware] [Xen] [Citrix Xen] [KVM] | /opt | 110 |
/etc/opt | 5 | |
/var/opt | 5 | |
Agent [Solaris] [Solaris Zones] [OVM for SPARC] | /opt | 100 |
/etc/opt | 5 | |
/var/opt | 5 | |
HBA address rename setup service [Windows] | Installation_folder (*) | 120 |
HBA address rename Setup Service [Linux] | /opt | 110 |
/etc/opt | 1 | |
/var/opt | 10 |
* Note: The installation folder name specified when this software is installed.
The default folder name when Windows is installed on C:\ is as follows:
When using a 64-bit (x64) OS
Default value: C:\Program Files (x86)\Resource Orchestrator
When using a 32-bit (x86) OS
Default value: C:\Program Files\Resource Orchestrator
The size of the required dynamic disk space changes dynamically when Resource Orchestrator is operated.
When using Resource Orchestrator, the following disk space is required for each folder, in addition to static disk space.
Software | Folder | Disk Space (Unit: MB) |
|---|---|---|
[Windows Manager] | Installation_folder (*1) | 2580 + Number_of_managed_servers * 4 + 16 * 10 (*3) |
Environmental_data_storage_area (*4) | ||
Image_file_storage_folder (*2) | Image_file_storage_area | |
[Linux Manager] | /etc | 2 |
/var/opt | 2580 + Number_of_managed_servers * 4 | |
Environmental_data_storage_area (*4) | ||
Image_file_storage_directory (*2) | Image_file_storage_area | |
Agent [Windows] [Hyper-V] | Installation_folder (*1) | 60 |
Agent [Linux] [Solaris] [Solaris Zones] [VMware] [Xen] [Citrix Xen] [KVM] [OVM for SPARC] | /etc | 1 |
/var/opt | 1 | |
HBA address rename setup service [Windows] | Installation_folder (*1) | 60 |
HBA address rename Setup Service [Linux] | /etc | 1 |
/var/opt | 60 |
*1: The installation folder name specified when this software is installed.
The default folder name when Windows is installed on C:\ is as follows:
When using a 64-bit (x64) OS
Default value: C:\Program Files (x86)\Resource Orchestrator
When using a 32-bit (x86) OS
Default value: C:\Program Files\Resource Orchestrator
*2: The name of the storage folder (directory) specified for image files when this software is installed.
[Windows Manager]
The default folder name when Windows is installed on C:\ is as follows:
When using a 64-bit (x64) OS
Default value: C:\Program Files (x86)\Resource Orchestrator\SVROR\ScwPro\depot
When using a 32-bit (x86) OS
Default value: C:\Program Files\Resource Orchestrator\SVROR\ScwPro\depot
[Linux Manager]
The default is as follows:
/var/opt/FJSVscw-deploysv/depot
*3: When an image operation is canceled or an error occurs, troubleshooting data regarding the image operation is backed up. During one backup, up to 16 MB or data for the last 10 times is backed up.
*4: Necessary when using power monitoring. For details, refer to "Environmental Data Storage Area".
Environmental Data Storage Area
The environmental data storage area is the area necessary when using power monitoring.
The environmental data storage area is located in the installation folder of the admin server, and is used to store environmental data collected from power monitoring targets and aggregate data.
The amount of space that is necessary for the environmental data storage area can be determined from the number of power monitoring targets being registered, the polling interval, and the period the environmental data is to be stored for.
For details on the settings, refer to "11.1.1 Settings for the Power Monitoring Environment" in the "Design Guide VE".
Estimate the necessary space using the following formula.
Necessary disk space (MB) = (detail_storage_period_(months) * 6 / polling_interval_(minutes) + 10) * 3 * number_of_power_monitoring_targets |
Image File Storage Area
The image file storage area is necessary when performing backup and cloning.
The image file storage area is secured on an admin server as an area to store the image files (system images and cloning images) collected through the backup and cloning of managed servers.
Note
Create the image file storage area on the local disk of the admin server, or SAN storage. It is not possible to specify folders on network drives, shared folders (NFS, SMB, etc.) on other machines on a network, or UNC format folders.
The space necessary for the image file storage area is the total amount of disk space necessary for the "system image storage area", the "cloning image storage area", and the "temporary work area".
Estimate the necessary space based on the disk space required for each storage area using the following formula.
Estimate the necessary space for the image file storage area using the following procedure.
Calculate the size of image files.
Calculate the image file sizes as base data for estimating the required disk space for A, B, and C indicated above.
The calculation method is given below.
File size of image files = disk_space_per_managed_server * compression_ratio |
When system construction using the same software configuration has been performed before, use the consumed disk space of that system (the sum of the disk space for each partition when dividing one disk into multiple partitions).
Check the consumed disk space using the relevant OS function.
When system construction using the same software configuration has not been performed before, calculate the disk space from the required disk space indicated in the installation guide for each piece of software.
For the OS, refer to "Examples of Calculation".
The compression ratio involved when storing the consumed disk space of managed servers as an image file on the admin server.
Compression ratio is dependent on file content, and usually a compression ratio of around 50% can be expected. When there are many files that have already been compressed (installation media of software, image data, or other media), the overall compression ratio is lower.
For the OS, refer to "Examples of Calculation".
An example of the calculation of disk space and the compression ratio directly after OS installation is given below.
Example
Examples of Calculation
For Windows Server 2003
Used disk space: 1.9 GB -> After compression: 0.9 GB Compression ratio: 0.9/1.9 = 47%
Calculate the space required for the system image storage area.
The system image storage area is the area necessary when performing backup. Secure space for each managed server for which backup system images are made.
This is not necessary when not performing backup.
Calculate the size of the system image storage area based on the image file size of step 1. Estimate the area for each managed server for which system images are backed up using the following formula, and use the total as the estimated size.
Disk space required for the system image storage area = file_size_of_image_files * number_of_versions |
The number of versions of system images. By default, up to three versions of system images can be managed.
Point
By reducing the number of versions of system images saved it is possible to reduce the amount of space required for the system image storage area.
For details of how to change the number of system images saved, refer to "5.8 rcxadm imagemgr" in the "Reference Guide (Command) VE".
The following is an example when three managed servers, A, B, and C are performing backup of system images, and the used disk space and compression ratios are expected to be the following values.
Example
Example of Estimation
Server A - Image_file_size: 3.0 GB (Used disk space: 6.0 GB, Compression ratio 50%)
Server B - Image_file_size: 1.6 GB (Used disk space: 4.0 GB, Compression ratio 40%)
Server C - Image_file_size: 1.6 GB (Used disk space: 4.0 GB, Compression ratio 40%)
(3.0 * 3) + (1.6 * 3) + (1.6 * 3) = 18.6 (GB)
Calculate the space required for the cloning image storage area.
The cloning image storage area is the area necessary when performing cloning. Secure space for each managed server for which cloning images are collected.
This is not necessary when not performing cloning.
Calculate the size of the cloning image storage area based on the image file size of step 1. Estimate the area for each managed server from which cloning images are collected using the following formula, then set the total as the estimated size.
Disk space required for the cloning image storage area = file_size_of_image_files * number_of_versions |
The number of versions of cloning images. By default, up to three versions of cloning images can be managed.
Point
By reducing the number of versions of cloning images saved it is possible to reduce the amount of space required for the cloning image storage area.
For details of how to change the number of versions of cloning images saved, refer to "5.8 rcxadm imagemgr" in the "Reference Guide (Command) VE".
The following is an example when managed servers A and B are used to collect cloning images, and the used disk space and compression ratios are expected to be the following values.
Example
Example of Estimation
Server A - Image_file_size: 3.0 GB (Used disk space: 6.0 GB, Compression ratio 50%)
Server B - Image_file_size: 1.6 GB (Used disk space: 4.0 GB, Compression ratio 40%)
(3.0 * 3) + (1.6 * 3) = 13.8 (GB)
Calculate the space required for the temporary work area.
When collecting system images or cloning images, the temporary work area is necessary to keep the former version of images until collection of new system images or cloning images is completed.
This is not necessary when not performing backup or cloning.
Calculate the size of the temporary work area based on the image file size of step 1.
Estimate the largest size of the image files of all managed servers, and determine the necessary area using the following formula.
Disk space required for the temporary work area = largest_image_file_size * image_file_collection_multiplicity |
Estimate image file collection multiplicity using operational designs in which image file collection (system image backup and cloning image collection) is simultaneously performed at the limit of multiplicity for multiple managed servers under management of an admin server. However, as Resource Orchestrator is designed not to exceed four multiplicities in order to reduce the load on the admin servers, the maximum multiplicity is 4.
The following is an example when three managed servers, A, B, and C are used to collect system images or cloning images, and the file size of each image file is as below. In this example, the image file collection multiplicity is 3.
Example
Example of Estimation
Server A - Image_file_size: 3.0 GB (Used disk space: 6.0 GB, Compression ratio 50%)
Server B - Image_file_size: 1.6 GB (Used disk space: 4.0 GB, Compression ratio 40%)
Server C - Image_file_size: 1.6 GB (Used disk space: 4.0 GB, Compression ratio 40%)
3.0 * 3 = 9.0 (GB)
Calculate the space necessary for the image file storage area based on the disk space calculated in steps 2 to 4.
Calculate the total amount of required space for A, B, and C calculated in steps 2 to 4. (A: Disk area required for system image storage area, B: Disk area required for cloning image storage area, C: Disk area required for temporary work area).
The memory size listed below is the minimum amount required when using Resource Orchestrator.
Consider the amount of memory necessary for required software as well as the amount of memory necessary for Resource Orchestrator.
Software | Memory Size (Unit: MB) |
|---|---|
[Windows Manager] | 1700 (3400 when managing VM guests) (*) |
[Linux Manager] | 5200 (7000 when managing VM guests) (*) |
Agent [Windows] [Hyper-V] | 200 |
Agent [Linux] | 500 |
Agent [Solaris] [Solaris Zones] [OVM for SPARC] | 100 |
Agent [VMware] | 500 |
Agent [Xen] [Citrix Xen] [KVM] | 500 |
HBA address rename setup service [Windows] | 300 |
HBA address rename Setup Service [Linux] | 600 |
*Note: When enabling the function in "7.5.1 Enabling the Network Device Management Function" in the "User's Guide VE", an additional 600 MB are required.
