Overview of Oracle Solaris Cluster Administration Concepts

Language:

You must be an experienced Oracle Solaris Cluster administrator to administer the Geographic Edition framework.

This section describes the following Oracle Solaris Cluster administration topics that you need to understand before you administer the Geographic Edition framework:

Configuring Resources and Resource Groups

You use either Oracle Solaris Cluster commands or the Oracle Solaris Cluster Manager browser interface to create failover and scalable resource groups.

For more information about administering resources and resource groups in Oracle Solaris Cluster software, see the Oracle Solaris Cluster 4.3 Data Services Planning and Administration Guide.

Legal Names and Values of Geographic Edition Entities

This section lists the requirements for legal characters for the names and values of Geographic Edition entities.

This appendix contains the following sections:

Legal Names for Geographic Edition Entities

Geographic Edition entity names consist of the following:

Host names
Cluster names, which must follow the naming requirements for host names
Partnership names
Protection group names
Custom heartbeat names

All names must comply with the following rules:

Must start with a letter
Must not exceed 255 characters
Can contain the following:
- Upper and lowercase letters
- Digits
- Dashes (-), except as the last character of a host name or cluster name
- Underscores (_), except in a host name or cluster name

For more information about host name requirements, see RFC 1123 at http://www.rfcs.org/.

Legal Values for Geographic Edition Entities

The Geographic Edition entity values fall into two categories: property values and description values. Both types of values share the following rules:

Values must be in ASCII
The maximum length of a value is 4 megabytes minus 1, that is, 4,194,303 bytes
Values cannot contain a newline or a semicolon

Administering Rights Profiles

This section describes how to administer role-based access control (RBAC) rights in the Geographic Edition framework. For information about rights for the Geographic Edition framework, see Planning Security in Oracle Solaris Cluster 4.3 Geographic Edition Installation and Configuration Guide.

Modifying a User's Rights

Note - The rights profiles for Oracle Solaris Cluster software, including the Geographic Edition framework,are intended to simplify the assignment of management roles and protect against accidental errors. However, a malicious user would be able to abuse rights-based cluster administration privileges to gain wider system privileges. Therefore, user rights should be assigned with care.

When you grant authorization to users other than the root role, you must do so on all nodes of both partner clusters. Otherwise, some operations that have a global scope might fail due to insufficient user rights on one or more nodes in the partnership.

To modify the rights for a user, you must be logged in as the root role or assume a role that is assigned the System Administrator rights profile.

For example, you can assign the Geo Management rights profile to the user admin as follows:

# usermod -P "Geo Management" admin
# profiles admin
Geo Management
Basic Solaris User
#

For more information about how to modify the rights properties for a user, refer to Chapter 2, Oracle Solaris Cluster and User Rights in Oracle Solaris Cluster 4.3 System Administration Guide.

Configuring Logical Hostnames

The logical hostname is a special high-availability (HA) resource. The geoadm start command configures the logical hostname that corresponds to the cluster name. You must set up the IP address and host maps for the logical hostname before you run this command.

For more information about using the geoadm start command, see Enabling and Disabling the Geographic Edition Framework.

Note - If you are using Availability Suite for data replication, a logical hostname is created for each device group to be replicated. For more information, see Chapter 1, Replicating Data With the Availability Suite Feature of Oracle Solaris in Oracle Solaris Cluster Geographic Edition Data Replication Guide for Oracle Solaris Availability Suite.

The following table lists the Oracle Solaris Cluster and Geographic Edition components that require IP addresses. Add these IP addresses to the following locations:

All naming services that are being used
The local /etc/inet/hosts file on each cluster node, after you install the Oracle Solaris OS software

Table 1 IP Addresses Required by the Geographic Edition Framework

Component	Number of IP Addresses Needed
Oracle Solaris Cluster administrative console	One per subnet
IP Network Multipathing groups	Single-adapter groups – one primary IP address. Multiple-adapter groups – one primary IP address plus one test IP address for each adapter in the group.
Cluster nodes	One per node, per subnet
Domain console network interface	One per domain
Console-access device	One
Logical addresses	One per logical host resource, per subnet
Geographic Edition infrastructure hostname	One logical IP address per cluster infrastructure. For example, if you have two clusters in your Geographic Edition infrastructure, you need two IP addresses.
Replication with Availability Suite from Oracle	One dedicated logical IP address on the local cluster for each device group to be replicated. For example, if you have two clusters in your Geographic Edition infrastructure, you need two IP addresses.

For more information about configuring the IP address and host maps during the installation of Oracle Solaris Cluster software, refer to Chapter 2, Installing Software on Global-Cluster Nodes in Oracle Solaris Cluster 4.3 Software Installation Guide.

Managing Device Groups

A device group is a hardware resource that is managed by the Oracle Solaris Cluster software. A device group is a type of global device that is used by the Oracle Solaris Cluster software to register device resources, such as disks. A device group can include the device resources of disks and Solaris Volume Manager disk sets.

For information about configuring device groups in Oracle Solaris Cluster software, refer to Chapter 5, Administering Global Devices, Disk-Path Monitoring, and Cluster File Systems in Oracle Solaris Cluster 4.3 System Administration Guide.

The Geographic Edition framework configures Oracle Solaris Cluster device groups to include replication.

For more information about configuring data replication in the Geographic Edition framework, see the Geographic Edition documentation for the data replication product you use.

Geographic Edition Configuration and Administration Tasks

The following table lists administration tasks for your Geographic Edition configuration.

Note - For procedures to create partnerships, heartbeats, protection groups, sites, and multigroups, see Oracle Solaris Cluster 4.3 Geographic Edition Installation and Configuration Guide and the Geographic Edition manual for your data replication product.

Table 2 Geographic Edition Administration Tasks

Task	Description and Documentation
Switch over services to the partner cluster. You can switch over individual protection groups or multigroups.	See the procedures to switch over a protection group from primary to secondary in the Geographic Edition manual for your data replication product. You can also use the Oracle Solaris Cluster Manager browser interface. To switch over multiple protections groups that are configured in a multigroup, see How to Switch Over a Multigroup. You can also use the Oracle Solaris Cluster Manager browser interface.
Take over services from primary to secondary during a disaster. You can take over services for an individual cluster or for a multigroup.	See the procedures to force immediate takeover of services by a secondary cluster in the Geographic Edition manual for your data replication product. You can also use the Oracle Solaris Cluster Manager browser interface. To take over multiple protection groups that are configured in a multigroup, see How to Take Over a Multigroup. You can also use the Oracle Solaris Cluster Manager browser interface.
Recover from a takeover.	Perform data recovery and error repair outside of the Geographic Edition infrastructure. See the Geographic Edition documentation for the data replication product you are using. Resynchronize the partner clusters. See Resynchronizing a Protection Group. You can also use the Oracle Solaris Cluster Manager browser interface.
Start an individual protection group or a multigroup.	To start an individual protection group, see How to Activate a Protection Group or use the Oracle Solaris Cluster Manager browser interface. To start a multigroup, see How to Start All Protection Groups in a Multigroup or use the Oracle Solaris Cluster Manager browser interface.
Stop an individual protection group or a multigroup.	To stop an individual protection group, see How to Deactivate a Protection Group. You can also use the Oracle Solaris Cluster Manager browser interface. To stop a multigroup, see How to Stop All Protection Groups in a Multigroup. You can also use the Oracle Solaris Cluster Manager browser interface.
Delete a multigroup	See Deleting a Multigroup. You can also use the Oracle Solaris Cluster Manager browser interface.
Delete a site.	See Deleting a Site. You can also use the Oracle Solaris Cluster Manager browser interface.
Delete a protection group or a data replication component.	See Deleting Protection Groups and Data Replication Components. You can also use the Oracle Solaris Cluster Manager browser interface.
Delete a partnership.	See Leaving or Deleting a Partnership. You can also use the Oracle Solaris Cluster Manager browser interface.
Disable the Geographic Edition framework.	See How to Disable the Geographic Edition Framework.
Uninstall the Geographic Edition software.	See Oracle Solaris Cluster 4.3 Geographic Edition Installation and Configuration Guide.