Veritas Cluster Server 6.

0 for UNIX:
Cluster Management
Lesson 1: Service Group Dependencies

Lesson introduction
Lesson 1: Service Group Dependencies
Lesson 2: Reconfiguring Cluster Membership
Lesson 3: Startup and Failover Policies
Lesson 4: Alternate Network Configurations
Lesson 5: High Availability in the Enterprise

Lesson objectives
Topic

Objectives

Common application
relationships

Describe common example application

relationships.

Service group
dependencies

Define service group dependencies.

Service group
dependency
examples

Describe example uses of service group

dependencies.

Configuring service
group dependencies

Configure service group dependencies.

Alternate methods of
Configure alternative methods for
controlling
controlling service group interactions.
interactions

Common application
relationships
After completing this topic, you
will be able to describe examples
of common application
relationships.

Multitier services
Many services have multiple
tiers.

Web

Tiers are represented by separate

service groups.
Relationships exist between tiers.
Relationships must be enforced
within VCS.

App

DB

Example 1: Online on the same system

Example criteria:

Web

Both must be online to

provide the service.

App

Web and App must run

on the same system, due
to system interprocess
communication.
Web

App

Web requires App to be

online first.
If App faults, Web must
follow it to the failover
system.

Example 2: Online on different systems

App

Example criteria:
Both must be online to
provide the service.

DB

App and DB cannot run

on the same system, due
to system usage
constraints.
App

DB

App requires DB to be
online first.
If App faults, DB
continues to run.

Example 3: Offline on the same system

Test

Example criteria:
One node is used for a
test environment.

Prod

Prod always has priority.

Test

Prod

Test and Prod cannot be

online on the same
system.

Service group
dependencies
After completing this topic, you
will be able to define service
group dependencies.

Service group dependency

definitions
Startup Category
Local
Same system

Online
Child starts first

Offline

Failover
Type
Soft
Firm
Hard

Global

Soft

Any system

Firm

Remote

Soft

Different
system

Firm

Local

Failover types
Soft

Firm

Hard

Keeps the
parent online
when the
child faults

Takes the
parent offline
when the child
faults

Takes child and

parent offline
when either
faults
Applies only to
an online local
dependency
Is allowed only
between a
single parent
and a single
child

Service group
dependency
examples

After completing this topic, you

will be able to describe example
service group dependency
behavior.

Online local example

Startup behavior:
Child comes online first
Parent must come online on
the same system

Soft failover behavior:

The child faults and fails over to an
available system while the parent
keeps running.
The parent is switched to the
failover system now running the
child.

Firm failover behavior:

The child faults and the parent is
taken offline.

Web

The child is restarted on a failover

system and then the parent is
restarted on the same system.

App
Hard difference
The child is taken offline if the
parent faults.

Online remote example

Startup behavior:

Failover example for soft type:

Child must be online

The child faults and fails

over to an available system.

Parent can come online

only on a remote system
App

If the selected target system

for the child is not running
the parent, then the parent
continues to run.
If the selected target has
the parent is online:

DB

The parent is taken offline.

The child is brought online.

Firm difference
The parent is always taken offline
when the child faults.

The parent is then restarted

on a system different from
the childs system.

Offline local example

Startup behavior:

Failover example:

Child can come online

anywhere the parent is offline

The child faults and fails

over to an available system.

Parent can come online only

where child is offline

If the selected target system

for the child is not running
the parent, then the parent
continues to run.

Test
Prod

If the selected target has

the parent is online:
The parent is taken offline.
The child is brought online.
The parent then restarts on a
system different from the
childs system.

Configuring service
group dependencies
After completing this topic, you
will be able to configure service
group dependencies according to
VCS rules.

Service group dependency rules

Service group dependency rules:
web

Child has priority

Multiple parents
Multiple children except for offline local

and online local hard

Maximum of five levels

app1

app2

app3

Cyclical dependencies prohibited

db1

db2

online local firm

online global firm
online global soft

Creating service group dependencies

hagrp link parent child online local firm
hagrp dep [group]
hagrp unlink parent child

main.cf

group g1 (

requires group g2 online local firm

Linking in GUI:
Right-click a service group.

Online and offline of linked service groups

Online/offline propagates to
child/parent groups
hagrp online propagate
Online propagates to offline child
groups.

hagrp offline propagate

Offline propagates to online local hard
and online local firm parent groups

g1

g2

g3

g4

g5

Does not offline online local soft parent

groups

Works with any and sys options

Online local group

dependency

Alternative methods
of controlling
interactions

After completing this topic, you

will be able to implement
resources and triggers to control
service group interactions.

Using triggers to control service group

interactions
preonline
Runs the preonline script before bringing the service
group online
Can bypass trigger with hagrp -online nopre group
...

postonline
Runs the postonline script after bringing a service
group online

postoffline
Runs the postoffline script after taking a service group offline

Managing multi-tier applications

Requirements:
Visualize status of
multi-tier app
across physical
and virtual
environments
Manage ordered
start or stop of
logical application
Start or stop VM
in conjunction
with application

Trading Application
WEB
APA

WEB
APA

WEB
APA

APA

APA

APA

SQL

SQL

SAP

SAP

SAP

IIS

SQL

SQL

APA

APA

APA

IIS

APP
WAS

WAS

APP
WAS

WLS

WLS

WLS

ORA

ORA

ORA

Sybase

Sybase

SAP

ORA

DB
ORA

ORA

Sybase

Sybase

Sybase

Virtual
Physical

6.0

Virtual Business Services

VOM
4.1

Billing
Billing

Web
serverServic
e
Web server
Group

Servi
ce
Grou
p
W
eb

We
b

VM

Application
Application
app app app

Symantec
ApplicationHA

VM

Application
HA
Servi
ce
Grou
p
Ap
p

Veritas Cluster
Server
HA

IP

VCS
Database
Database

Servic
e
Group
DB
IP

FS
VVR

VCS

Veritas Cluster
Server
HA/DR

How Virtual Business Services

Works: High Availability
Fault Propagation Between Clusters

Billing Virtual Business Service

apache_sg

VBS

Soft
oracle_apps_sg

oracle_sg

VBS

Restart
VBS

Configurable
Fault Reaction
Soft
Firm
Restart
Automatic Fault
Propagation
No external brain
No heartbeats
Secure

Lesson summary
Key points
You can use service group dependencies to control interactions
among applications.
You can also use triggers and specialized resources to manage
application relationships.

Reference materials
Veritas Cluster Server Users Guide
Virtual Business Service Availability Users Guide
Job Aids Appendix

End of Presentation