Summary
What is high availability and cluster? VCS Communication Mechanism VCS Architecture and Agent Monitoring Fail Over Configurations Installation of Veritas Cluster Server in Unix platforms

Add systems. web interface. restart and failover Simplified administration of IT assets (manageability) Java. storage to running clusters .High Availability & VCS Features Combination of 2 or more servers with appropriate middleware and interconnects to achieve some or all of the following: High levels of system reliability (availability) Monitor. Manage multiple clusters Increased processing power (scalability) Distributed services.

Sample Cluster .

High Availability Design HA-aware applications Restart capability Crash-tolerance HA Management software Site replication Fault detection. switches storage . hubs. and failover Storage management Backup and recovery Redundant Hardware Power supplies Network interface cards. notification.

Most applications are configured this way Parallel – Online on multiple services at a time. web servers.g. also referred as node Has it’s own copy of VCS software Share a common view of cluster configuration which is dynamically communicated whenever changes are made within the cluster Connected to public network to provide application services to users Service groups Related collection of resources All resources within the service group must be available and this can’t be spitted across systems Resources have interdependencies which must be considered during configuration and management Service groups also have interdependencies Service group types Failover – online on one server at a time. Application must be specifically designed to run in parallel.. FTP.VCS Terms & Concepts Cluster A VCS cluster consists of multiple systems connected in various combinations to shared storage devices VCS engines (had) runs on each system in the cluster that controls applications running in the cluster Systems Member of a cluster. Oracle parallel servers . E.

IPs. NIC Resource Types have inherent interdependencies – IP resource type depends on the NIC resource type New resource types can be created as required Agents Processes that control resources One agent per resource type Agent controls all resources of that type New agents can be added apart from predefined agents Dependencies The order in which VCS brings the resources and service groups online or offline Parent resource depends on child resource for example Mount depends on Disk Dependencies are homogenous.VCS Terms & Concepts contd. IP. offline. Resources VCS objects that correspond to hardware of software components – disks. databases Predefined resource types: Mount. Share. IP.. monitor Classified by type Identified by unique names and attributes Can depend on other resources within the same service group –( correct order) Resource Types General description of the attributes of a resource such as disks. interface cards. etc Monitored and controlled by VCS – online. for example Service group can’t depend on a resource . applications.

VCS Communication Mechanisms Private Network Minimum of two dedicated communication channels between each system in the cluster Heartbeat communication – Determines cluster membership Configuration distribution – Configuration & status information for every resource and service groups are dynamically distributed dynamically to all systems LLT (Low Latency Transport) Proprietary networking protocol used by VCS for heartbeat communication and Traffic distribution Very fast. kernel-to-kernel communication. not routable Uses DLPI over Ethernet GAB (Group Membership Services/Atomic Broadcast) Manages cluster membership and maintain cluster state Runs over LLT Uses broadcasts to distribute cluster configuration information VCS Engine (had) Maintains configuration and state information for all cluster resources Uses GAB to communicate among systems Monitored by hashadow process VCS Architecture overview .

VCS components VCS: A Replicated State Machine .

Monitoring and Communication VCS HAD process agent web process SGweb file system agent web fs web ip nic agent ip agent web dg disk group agent nic .

VCS Architecture Overview Each cluster system has VCS agents that monitor the status of resources Agents communicate the status of resources to the VCS engine The VCS engine communicates the status of all local resources to other systems using GAB GAB uses LLT to communicate between systems over private network These mechanisms work together to ensure all members of the cluster maintain identical copy in local memory .

1.1 192.1.1.1.Fail Over Configurations Asymmetric Before After 192.1 Asymmetric Failover .

1.1.1.1.1.2 192.1.1.2 192.1.1 192.1 Symmetric Failover .Fail Over Configurations Symmetric Before After 192.

Fail Over Configurations N to 1 N to 1 failover .

Application Service Management SG Web SG Web SG Oracle NBU SG SG Oracle Multi Node / Multi Group Clusters Unlimited numbers of resource (service) groups Migrate RG without affecting other RG’s Cascading failover Policy based failover . stop and migration of resource groups .GUI .load distribution Attribute based RGs Easy start.

veritas.VCS Installation on Solaris Prerequisites: Sun Solaris with latest patches.com) A minimum of two physically independent private networks Crossover cable or hub based on number of nodes Atleast 3 ethernet cards Shared storage with separate controller Environment variables PATH=$PATH:/sbin:/usr/sbin:/opt/VRTSvcs/bin MANPATH=$MANPATH:/opt/VRTS/man export $PATH. VxVM. VCS and VxFS Veritas license keys for all Veritas products (http://vlicense. $MANPATH .

RISC RHEL 4 Update 3 and SLES9 SP3 Solaris SPARC 2.0 Installation – Disk space required: – Operating System Support: Cluster Manager (Java Console) AIX 5.10 Windows 2000. 2.9. Windows XP & Windows 2003 .23 IA and PA .8.2 and 5. and 2.VCS 5.3 HPUX 11.

VRTSvcsmg. VRTSvlic. VRTSvcs. VRTSweb.cf /etc/VRTSvcs/conf/config/types.The installvcs utility VCS packages: VRTSgab. VRTSvcsw It creates VCS communication files: /etc/llttab /etc/gabtab /etc/llthosts The following configuration files are added: /etc/VRTSvcs/conf/config/main.pm file . VRTSperl. VRTSvcsag. VRTSvcsmn. VRTSllt. VRTSvcsdc.cf Installvcs options -installonly -> Only licensing & installation of VCS software -configonly -> creates configuration files without performing installation -configfile -> unattended installation using VCSvars.

Installation parameters Cluster Name Cluster Number : 0 to 255. Avoid “0” as it’s default System Names (host name) Network interfaces identified for VCS private network Web console configuration – Virtual IP. ClusterService servicegroup is created SMTP/SNMP notification configuration . Subnet mask and Network interface.

cf “had” daemon maintains configuration in memory and state information of all cluster resources Starting VCS “hastart” command starts the “had” and “hashadow” processes “had” checks for active configuration in private network otherwise it loads the configuration from disk.cf on each system in the cluster The cluster configuration in memory is created from main. . Node-1 starts had & hashadow processes on second node and process is repeated until all members have identical copies.Managing Cluster Services Cluster Configuration File: /etc/VRTSvcs/conf/config/main.

it prompts to open the configuration when attempting to modify the configuration Starting VCS with a stale configuration If .cf .stale file found during startup.stale file is removed after saving valid configuration to main.stale file is created in config directory “haconf –dump –makero” – Changes written to disk and .stale file removed otherwise it keeps the changes only in memory In GUI.Managing Cluster Services Modifying Cluster Configuration “haconf –makerw” -> Cluster configuration opened and . it requests the configuration from another server via private network .

Managing Cluster Services Modifying Cluster Configuration “haconf –makerw” -> Cluster configuration opened and .stale file is removed after saving valid configuration to main. it requests the configuration from another server via private network . it prompts to open the configuration when attempting to modify the configuration Starting VCS with a stale configuration If .cf .stale file found during startup.stale file is created in config directory “haconf –dump –makero” – Changes written to disk and .stale file removed otherwise it keeps the changes only in memory In GUI.

com/business/support/index?page=content &id=DOC5492 https://sort.symantec.symantec.0 http://www.com/public/documents/sf/5.pdf Thanks & Regards Kiran Jangam Fujitsu India Pvt Ltd .0/solaris/pdf/vcs _users.com/connect/forums/top-technotes-veritascluster-server-updated-march-2012 http://www.symantec.References : Symantec Tech notes & VCS Admin Guide 5.

Sign up to vote on this title
UsefulNot useful