InfoScale™ Operations Manager 9.0 Installation and Configuration Guide
- Section I. Installing and configuring Arctera InfoScale Operations Manager
- Planning your Arctera InfoScale Operations Manager installation
- Downloading Arctera InfoScale Operations Manager 9.0
- Typical Arctera InfoScale Operations Manager deployment configuration
- System requirements
- Installing, upgrading, and uninstalling Arctera InfoScale Operations Manager
- About installing Management Server
- About installing managed host
- About upgrading the Management Server
- About backing up and restoring Arctera InfoScale Operations Manager data
- About upgrading managed hosts to Arctera InfoScale Operations Manager 9.0
- Configuring Arctera InfoScale Operations Manager in a high availability and disaster recovery environment
- Configuring the high availability feature in Arctera InfoScale Operations Manager
- Configuring a new Arctera InfoScale Operations Manager installation in high availability environment
- Configuring an existing Arctera InfoScale Operations Manager installation in high availability environment
- Configuring a new Arctera InfoScale Operations Manager installation in high availability environment
- Configuring Management Server in one-to-one DR environment
- Configuring Arctera InfoScale Operations Manager in high availability and disaster recovery environment
- About upgrading the high availability configurations
- About upgrading the high availability and disaster recovery configurations
- Configuring the high availability feature in Arctera InfoScale Operations Manager
- Installing and uninstalling Arctera InfoScale Operations Manager add-ons
- Uploading a Arctera InfoScale Operations Manager add-on to the repository
- Installing a Arctera InfoScale Operations Manager add-on
- Uninstalling a Arctera InfoScale Operations Manager add-on
- Removing a Arctera InfoScale Operations Manager add-on from the repository
- Canceling deployment request for a Arctera InfoScale Operations Manager add-on
- Installing a Arctera InfoScale Operations Manager add-on on a specific managed host
- Uninstalling a Arctera InfoScale Operations Manager add-on from a specific managed host
- Planning your Arctera InfoScale Operations Manager installation
- Section II. Setting up the Management Server environment
- Basic Arctera InfoScale Operations Manager tasks
- Adding and managing hosts
- Overview of host discovery
- Overview of agentless discovery
- About installing OpenSSH on a UNIX host
- Adding the managed hosts to Management Server using an agent configuration
- Adding the managed hosts to Management Server using an agentless configuration
- Adding Agentless hosts to the Management Server using Profile
- Editing the agentless host configuration
- Setting up user access
- Adding Lightweight Directory Access Protocol or Active Directory-based authentication on Management Server
- Configuring LDAP using CLI
- Setting up fault monitoring
- Creating rules in the Management Server perspective
- Editing rules in the Management Server perspective
- Deleting rules in the Management Server perspective
- Enabling rules in the Management Server perspective
- Disabling rules in the Management Server perspective
- Suppressing faults in the Management Server perspective
- Suppressing a fault definition in the Management Server perspective
- Setting up virtualization environment discovery
- Setting up near real-time discovery of VMware events
- Requirements for discovering the Solaris zones
- Adding a virtualization server
- Editing a virtualization discovery configuration
- Refreshing a virtualization discovery configuration
- Deploying hot fixes, packages, and patches
- Installing a Arctera InfoScale Operations Manager hot fix, package, or patch
- Configuring Management Server settings
- Configuring SNMP trap settings for alert notifications
- Setting up extended attributes
- Viewing information on the Management Server environment
- Appendix A. Troubleshooting
- Management Server (MS)
- Managed host (MH)
- Management Server (MS)
Creating the base service groups for DR configuration
You need to create the base service groups in Cluster Server and link those base service groups and resource types for DR configuration.
You need to create at least the following service groups with their respective resources on Node1 and Node2:
Service group | Resource |
---|---|
SFM_SStore |
|
SFM_Services |
|
Note:
For DR configuration, you need to use the service group names and resource names as suggested. Failure to do so may result in configuration failure.
It is recommended to set up the VVR rlinks under Cluster Server control. No naming convention is required for the VVR rlink resources. For more information, refer to the Cluster Server Bundled Agents Reference Guide and Cluster Server Agents for Volume Replicator Configuration Guide depending on the version of the Cluster Server.
For the resources that you need to create on the SFM_SStore service group, refer to the following table:
Resource name
Resource type
Attributes
SFM_SStore_DG
Disk group for Linux
VMDg for Windows
Diskgroup: Disk group that is specified for the failover.
Note:
You must create a clustered disk group.
SFM_SStore_IP
IP
Address: Virtual IP address.
MACAddress: Physical address of NIC, to which virtual IP address is assigned. This address is always local and different for each system.
SubNetMask: Subnet mask that is associated with the IP address
SFM_SStore_NIC
NIC
Device: Name of the NIC where virtual IP is plumbed.
SFM_SStore_RVG
RVG for Linux
VvrRvg for Windows
RVG: Replicated volume group (RVG) that is configured for replication of volumes
Diskgroup: Disk group that is used for creating RVG.
For resources that you need to create for the SFM_Services service group, refer to the following link for creating the resources that you need for HA:
For HA-DR configuration, apart from the resources you create for HA, you need to create the following additional resource for the SFM_Services service group:
Resource name
Resource type
Attributes
SFM_Services_RVGPRI
RVGPrimary
Contains the RVG resource name that is to be used for replication.
For more information on configuring resources, refer to the Cluster Server Bundled Agents Reference Guide.
After creating the required service groups and resources, you need to link the base service groups. For selecting the options while linking the service groups, refer to the following table:
Selection | Option |
---|---|
SFM_Services | Parent Group |
SFM_SStore | Child Group |
Relationship | Online Local |
Dependency Type | Hard |
You need to link the resources. For selecting parent and child dependencies, refer to the following table:
Parent Dependency | Child Dependency |
---|---|
SFM_SStore_RVG | SFM_SStore_DG |
SFM_Services_IP | SFM_Services_NIC |
SFM_Services_Mount | SFM_Services_RVGPrimary |
SFM_Services_RVGPrimary | SFM_Services_IP |
After creating the SFM_Services and SFM_SStore service groups on Site A and linking them, repeat the same procedure for site B. On Site B, ensure that the SFM_Services_NIC, SFM_SStore_RVG, and SFM_SStore_DG are online and rest of the resources are offline. Also, you must configure SFM_Services service group as Global on site A and add Site B in the cluster.