ACSLS HA is a hardware and software configuration that provides dual-redundancy, automatic recovery and automatic failover recovery to ensure uninterrupted tape library control service if component or subsystem failures occur. This document explains the configuration, setup and testing procedures required to provide High Availability to ACSLS software.
It is best to review the complete installation process before beginning the procedure. The process of installing a clustered application involves multiple steps requiring strict attention to detail. This procedure is normally undertaken by specialists in UNIX system integration.
There are multiple hardware and software components associated with an ACSLS HA system and the full installation procedure may take several days. For existing production library environments, customers are advised to install a simple, standalone ACSLS server to handle library production while the ACSLS HA installation is in progress.
The configuration is a two-node cluster. It includes two complete subsystems, (one active and one standby) with monitoring software capable of detecting serious system failures. It can switch control from the primary to the standby system for any non-recoverable subsystem failure. The configuration provides redundant power supplies, and redundant network and I/O interconnections that can recover subsystem communication failures instantly without the need for a general switch over.
ACSLS HA leverages the monitor and failover features in Solaris Cluster and the multipath features in Solaris operating system to provide resilient library control operation with minimal downtime. Solaris offers IP multipathing to ensure uninterrupted network connectivity and Multipath disk I/O with RAID 1 to ensure uninterrupted access to system data. Solaris Cluster watches the health of system resources including the operating system, internal hardware and external I/O resources and it can manage a system switch over if needed. The ACSLS HA agent monitors the ACSLS application, its database, its file system, and connectivity to StorageTek library resources, invoking the Solaris Cluster failover service, if needed.
In this redundant configuration, the ACSLS Library Control Server has a single logical host identity which is always known within the cluster framework and to the rest of the world. This identity is transferred automatically as needed between the cluster nodes with minimal downtime during the transition.
Before embarking on the project, review the complete process of installing and configuring ACSLS HA as it is documented here. If desired, Advanced Customer Services from Oracle can be arranged to advise, to assist, or to handle the entire installation.
For ACSLS documentation, refer to the Oracle Technical Network (OTN) at:
An ACSLS HA server configuration consists of two Solaris server nodes sharing an external RAID disk array
ACSLS HA supports all ACSLS clients that use the Automated Cartridge System Application Programming Interface (ACSAPI) network interface. A single network IP Address is shared between the two server nodes, allowing ACSAPI clients to address ACSLS using a common virtual host ID.
Logical libraries presented to fibre-channel clients using the SMCE (SCSI Media Changer Emulation) are not supported in this product.
ACSLS HA 8.4 should run on any system that meets the minimum hardware requirements for Solaris Cluster 4.2. For specific server platform requirements, consult the document entitled Oracle Solaris Cluster System Requirements.
To avoid any single point of failure, each ACSLS HA server node must be configured with the following:
Dual (Redundant) Power Supply
Six 10/100/1000 base-T Ethernet ports
Two fibre-channel ports (if using FC attached storage)
Two SAS ports (if using SAS-attached storage)
If the system is intended for use with logical libraries, at least one additional dedicated fibre-channel port is required in configurations supporting SCSI client applications.
One additional fibre-channel port is required for any intended fibre-attached libraries, such as the SL500 or SL150.
For supported disk array subsystems, consult the document entitled Oracle Solaris Cluster Storage Partner Program.
http://www.oracle.com/technetwork/server-storage/solaris-cluster/partnerprogram-cluster-168135.pdf
You should reserve a total of seven IP addresses.
1 - Logical Host (Cluster virtual IP (VIP)
2 - Node-1 IP address
3 - Node-2 IP address
4 - Library interface-1 source IP address (Node-1)
5 - Library interface-2 source IP address (Node-1)
6 - Library interface-1 source IP address (Node-2)
7 - Library interface-2 source IP address (Node-2)
Ideally, Library interface-1 should be on a different subnet from Library interface-2 (see Figure 2-1).
Before installing a new ACSLS HA system or upgrading an ACSLS HA system to a new release, determine and record information about the customer environment in which ACSLS HA is installed.
Completing this pre-installation checklist eliminates risk. This checklist also ensures that your installation proceeds smoothly and is not delayed while you are waiting for details about the customer environment.
Who are the local Oracle people who support this customer?
Do any of them have experience with Solaris system administration?
Do any of them have experience with ACSLS?
Do any of them have experience with ACSLS HA?
Who are the customer's system administration staff who will support activities such as the ACSLS HA servers and the customer's network?
Do any of them have experience with Solaris system administration?
Do any of them have experience with ACSLS?
Do any of them have experience with ACSLS HA?
Who are the network administrators?
Oracle Sun servers - model?
Solaris release and update level?
Memory (10 GB minimum).
Dual boot drives on each server are required to mirror the disks.
What is the model of the shared disk? Is it supported by Solaris Cluster?
SAS or Fibre HBAs used to connect each ACSLS server to the shared disk array.
Six Ethernet ports required on each ACSLS server.
If ACSLS is managing Fibre-attached libraries (SL500 or SL150) or presenting logical libraries using Fibre target mode ports, a Fibre HBA is required on each ACSLS server.
What power cords are needed to connect the Solaris servers and the disk array to the customer's environment? For example, the plugs must match the power outlets at the customer site to avoid a delay in the HA installation.
Before starting an HA installation, make sure the HA servers and shared disk array are configured correctly:
To satisfy the six-port requirement for Ethernet connections, each HA server must be equipped with an extra Network Interface Controller (NIC) card.
Be aware of the interface type for the external shared disk array and ensure that a compatible HBA is configured on each server.
If ACSLS is to communicate with Fibre-attached libraries, such as SL500s or SL150s, Fibre HBAs are required
If ACSLS presents logical libraries using Fibre target mode, Qlogic Fibre HBAs are required.
Review the following network information.
A total of nine IP addresses are needed for the installation:
Local address of ACSLS server node-1
Local address of ACSLS server node-2
Logical host address (virtual IP address shared between two HA nodes)
Library connection-a from node-1
Library connection-b from node-1 (for dual TCP/IP or multi-TCP/IP redundancy)
Library connection-a from node-2
Library connection-b from node-2 (for dual TCP/IP or multi-TCP/IP redundancy)
ILOM on node-1
ILOM on node-2
Will ACSAPI client(s) communicate with ACSLS?
After a failover event, the active node assumes the virtual IP address. The virtual IP address is accessible to ACSLS clients, no mater which node is active.
Do you know how to set the ACSLS HA virtual IP address or hostname on the ACSAPI client(s)? This setting depends on the ISV application running on the client.
The IP addresses that ACSLS uses to communicate with TCP/IP-attached libraries (SL8500s, SL3000s, and 9310s).
To avoid a single point of failure, it is best to route each redundant library connection through its own separate subnet. To prevent problems due to high-volume network traffic, the subnet should be reserved for library communication and not subject to interference from general network chatter.
The IP addresses and password(s) needed to access the service processor (for example, ILOM or ALOM) on each ACSLS HA node.
Is the communication between ACSLS and TCP/IP-attached libraries on a subnet(s) protected from broadcast traffic?
Are there any firewalls between ACSAPI clients and the ACSLS HA system?
Are there any firewalls between the ACSLS HA system and the libraries that it manages?
If any firewalls exist, refer to the ”Firewall Security Option” appendix in the ACSLS 8.4 Administrator's Guide for details about how to configure ACSLS and ACSAPI clients to communicate through the firewalls.
Will there be direct or indirect access from the HA servers to the Internet to allow software downloads from the Oracle edelivery website, including Oracle Solaris Cluster, ACSLS, ACSLS HA, and other required packages or patches?
If access is indirect, ensure that you can transfer files from the Internet to the HA servers.
Assuming that software is to be downloaded directly from the Internet to the local machines, ensure that complete proxy information for browser configuration is available at install time.
Will ACSAPI client(s) (such as backup or Information Lifecycle Management applications) communicate with ACSLS?
If ACSAPI clients will communicate with ACSLS, what are the client applications (such as NetBackup, Oracle SAM).
What versions of these clients are used?
If the client(s) run on Windows and use LibAttach, what version of LibAttach are they running?
Do client applications communicate with ACSLS logical libraries using Fibre Channel target mode ports?
What are the client applications (such as NetBackup and Oracle SAM)?
What versions of these clients are used?
A full ACSLS HA installation involves the following steps:
Install two Solaris platform servers attached to a common external fibre-channel or SAS2 disk array. Install Solaris 11.2 on each server.
Refer to the document, Installing Oracle Solaris 11 Systems, available from the Oracle Technology Network library:
http://www.oracle.com/technetwork/documentation/solaris-11-192991.html
Configure the basic Solaris system.
User access privileges
Multipath network access and disk I/O
Configure the ZFS file systems.
root storage pool
acsls storage pool
Download software packages. See "Downloading Software Packages."
ACSLS 8.4.0
Solaris Cluster 4.2
ACSLS HA 8.4.0
Install ACSLS 8.4.0 and patch update (if any). See "Installing ACSLS 8.4."
Install Solaris Cluster 4.2 and patch update (if any). See "Installing Solaris Cluster 4.2."
Install ACSLS HA 8.4.0. See "ACSLS HA 8.4 Installation and Startup."
Fine tune Cluster operation for ACSLS HA. See "Fine Tuning ACSLS HA."