This section explains high availability of managers.
For details on prerequisites, refer to "7.3 Admin Server High Availability Design" in the "Design Guide CE".
Manager High Availability in Windows Guest Environments in Hyper-V environments
Install an operating system and configure a domain controller on the domain controller server.
Perform installation and configuration of the admin server.
The following operations are necessary:
Primary Node
Connection with shared storage
Configure BIOS
Install Hyper-V roles
Install and configure EMC Solutions Enabler (when used)
Add a failover clustering function
Create a Hyper-V virtual network
Create clusters
Prepare virtual machines
Register virtual machines in clusters
Install and configure storage management software
Install and configure VM management software
Install and configure ServerView Operations Manager and ServerView Virtual-IO Manager
Install the Resource Orchestrator manager
Setup Resource Orchestrator
Secondary Node
Connection with shared storage
Configure BIOS
Install Hyper-V roles
Install and configure EMC Solutions Enabler (when used)
Add a failover clustering function
Create a Hyper-V virtual network
For details on the following items, refer to the Hyper-V manual.
Install Hyper-V Roles
Add a Failover Clustering Function
Create a Hyper-V Virtual Network
Create Clusters
Prepare Virtual Machines
Register Virtual Machines in Clusters
Operation
When an error occurs on a VM guest, the operation will continue if the VM guest is switched over.
Note
When performing configuration, modification, or deletion of managed server environments, such as L-Server creation, if an error occurs on VM guest, the operation may fail.
In this case, part of the environment of the managed server may be created. Perform the operation again after deleting created environments.
When performing L-Server creation or ETERNUS configuration information modification using ETERNUS, if an error occurs on a VM guest, ETERNUS may not be able to return from the status of processing to normal status. In this case, to restore, forcibly log on from ETERNUSmgr, then log off. In the case of ETERNUS DX60/DX80/DX90, contact Fujitsu technical staff. For details on how to restore ETERNUS, refer to the ETERNUS manual.
Manager Cluster Operation in Windows and Linux Environments
The settings and deletion operations described below are required for cluster operation.
For details on the settings for cluster operation and the procedure for deletion, refer to "Appendix C Manager Cluster Operation Settings and Deletion" in the "Setup Guide VE".
Settings
Primary Node
Create cluster resources
Copy dynamic disk files
Perform link settings for folders on the shared disk
Set folder and file access rights
Set access rights for the Resource Orchestrator database
Change the IP address set for the manager's admin LAN
Register service resources
Start the cluster service
Secondary Node
Perform link settings for folders on the shared disk
Set access rights for the Resource Orchestrator database
Change the IP address set for the manager's admin LAN
Start the cluster service
Deletion
Primary Node
Stop the cluster service
Delete service resources
Uninstall the manager
Secondary Node
Uninstall the manager
Delete shared disk files
Delete cluster resources
Note
If switchover of an admin server occurs while L-Servers are operating, the operation being performed may fail.
If you were creating or registering resources, delete unnecessary resources and then perform the operation again.
When performing L-Server creation or ETERNUS configuration information modification using ETERNUS, if an error occurs on an admin server, ETERNUS may not be able to return from the status of processing to normal status. In this case, to restore, forcibly log on from ETERNUSmgr, then log off. In the case of ETERNUS DX60/DX80/DX90, contact Fujitsu technical staff. For details on how to restore ETERNUS, refer to the ETERNUS manual.
