VCS - Implementing Cluster File System (CFS)

Tuesday, March 10, 2009 at 1:30 PM |

Veritas Cluster File System (CFS)

CFS allows the same file system to e simulta!eously mou!ted o! multi"le !odes i! the cluster# The CFS is desi$!ed with master%sla&e architecture# Thou$h a!y !ode ca! i!itiate a! o"eratio! to create, delete, or resi'e data, the master !ode carries out the actual o"eratio!# CFS caches the metadata i! memory, ty"ically i! the memory uffer cache or the &!ode cache# ( distri uted loc)i!$ mecha!ism, called *+M, is used for metadata a!d cache cohere!cy amo!$ the multi"le !odes#

The examples here are :

1# ,ased o! -CS .#/ ut should also wor) o! 0#/ 2# ( !ew 0 !ode cluster with !o resources defi!ed# 3# 1is)$rou"s a!d &olumes will e created a!d shared across all !odes#

Before you configure CFS

1# Ma)e sure you ha&e a! esta lished Cluster a!d ru!!i!$ "ro"erly# 2# Ma)e sure these "ac)a$es are i!stalled o! all !odes: -2TSca&f -eritas cfs a!d c&m a$e!ts y Syma!tec -2TS$lm -eritas +3C4 M*2 y Syma!tec 3# Ma)e sure you ha&e a lice!se i!stalled for -eritas CFS o! all !odes# 0# Ma)e sure &/fe!ci!$ dri&er is acti&e o! all !odes 5e&e! if it is i! disa led mode6#

Check the status of the cluster

7ere are some ways to chec) the status of your cluster# 3! these e/am"les, C-M%CFS are !ot co!fi$ured yet#

# cfscluster status
NODE serverA server serverC serverD CLUSTER MANAGER STATE running running running running CVM STATE not-running not-running not-running not-running

Error! V-"#-$%! Cluster not configure& for &ata s'aring a((lication

# v)&ctl -c *o&e
*o&e! ena+le&! cluster inactive

# ,etc,v),+in,v)clusta&* ni&*a(
Out of cluster! No *a((ing infor*ation availa+le

# ,etc,v),+in,v)clusta&* -v no&estate
state! out of cluster

# 'astatus -su*
-- S-STEM STATE -- S.ste* A A A A serverA server serverC serverD State RUNN1NG RUNN1NG RUNN1NG RUNN1NG 2 2 2 2 /ro0en

Configure the cluster for CFS

1uri!$ co!fi$uratio!, &eritas will "ic) u" all i!formatio! that is set o! your cluster co!fi$uratio!# (!d will acti&ate C-M o! all the !odes#

# cfscluster config
T'e cluster configuration infor*ation as rea& fro* cluster configuration file is as follo3s4 Cluster ! M.Cluster No&es ! serverA server serverC serverD -ou 3ill no3 +e (ro*(te& to enter t'e infor*ation (ertaining to t'e cluster an& t'e in&ivi&ual no&es4 S(ecif. 3'et'er .ou 3oul& li5e to use GA *essaging or TC6,UD6 *essaging4 1f .ou c'oose ga+ *essaging t'en .ou 3ill not 'ave to configure 16 a&&resses4 Ot'er3ise .ou 3ill 'ave to (rovi&e 16 a&&resses for all t'e no&es in t'e cluster4 ------- /ollo3ing is t'e su**ar. of t'e infor*ation! -----Cluster ! M.Cluster No&es ! serverA server serverC serverD Trans(ort ! ga+ ----------------------------------------------------------7aiting for t'e ne3 configuration to +e a&&e&4 88888888888888888888888888888888888888888888888888888888 Cluster /ile S.ste* Configuration is in (rogress444 cfscluster! C/S Cluster Configure& Successfull.

Check the status of the cluster

8ow let9s chec) the status of the cluster# (!d !otice that there is !ow a !ew ser&ice $rou" c&m# C-M is re:uired to e o!li!e efore we ca! ri!$ u" a!y clustered filesystem o! the !odes#

# cfscluster status
No&e ! serverA Cluster Manager ! running CVM state ! running No *ount (oint registere& 3it' cluster configuration No&e ! server Cluster Manager ! running CVM state ! running No *ount (oint registere& 3it' cluster configuration No&e ! serverC Cluster Manager ! running CVM state ! running No *ount (oint registere& 3it' cluster configuration No&e ! serverD Cluster Manager ! running CVM state ! running No *ount (oint registere& 3it' cluster configuration

# v)&ctl -c *o&e
*o&e! ena+le&! cluster active - MASTER *aster! serverA

# ,etc,v),+in,v)clusta&* ni&*a(
Na*e serverA server serverC serverD state! cluster *e*+er no&e1&82 *aster1&8% neig'+or1&8% *e*+ers82)f ;oiners82)2 leavers82)2 reconfig<se=nu*82)f2a>%2 v)fen8off CVM Ni& 2 % : " 2 % : " CM Ni& State 9oine&! 9oine&! 9oine&! 9oine&! Master Slave Slave Slave

# ,etc,v),+in,v)clusta&* -v no&estate

# 'astatus -su*
-- S-STEM STATE -- S.ste* A A A A serverA server serverC serverD State RUNN1NG RUNN1NG RUNN1NG RUNN1NG S.ste* serverA server serverC serverD 2 2 2 2 6ro+e& N N N N AutoDisa+le& State ONL1NE ONL1NE ONL1NE ONL1NE /ro0en

-- GROU6 STATE -- Grou( cv* cv* cv* cv*

Creating a Share !isk "roup an Volumes#Filesystems

This "rocedure creates a shared dis) $rou" for use i! a cluster e!&iro!me!t# 1is)s must e "laced i! dis) $rou"s efore they ca! e used y the -olume Ma!a$er# ;he! you "lace a dis) u!der -olume Ma!a$er co!trol, the dis) is i!itiali'ed# <!itiali'atio! destroys a!y e/isti!$ data o! the dis)# ,efore you e$i!, ma)e sure the dis)s that you add to the shared=dis) $rou" must e directly attached to all the cluster !odes# First, ma)e sure you are o! the master !ode:

serverA # v)&ctl -c *o&e

*o&e! ena+le&! cluster active - MASTER *aster! serverA

<!itiali'e the dis)s you wa!t to use# Ma)e sure they are attached to all the cluster !odes# >ou may o"tio!ally s"ecify the dis) format#

serverA # v)&is5setu( -if EMC2<% for*at8c&s&is5 serverA # v)&is5setu( -if EMC2<: for*at8c&s&is5

Create a shared dis) $rou" with the dis)s you ?ust i!itiali'ed#

serverA # v)&g -s init *.s'are&g *.s'are&g2%8EMC2<% *.s'are&g2:8EMC2<: serverA # v)&g list

*.s'are&g ena+le&?s'are&?c&s %:"%@#$%%:4%A"4serverA

8ow let9s add that !ew dis) $rou" i! our cluster co!fi$uratio!# *i&i!$ all !odes i! the cluster a! o"tio! for Shared ;rite 5sw6#

serverA # cfs&ga&* a&& *.s'are&g all8s3

Dis5 Grou( is +eing a&&e& to cluster configuration444

-erify that the cluster co!fi$uratio! has ee! u"dated#

serverA # gre( *.s'are&g ,etc,VRTSvcs,conf,config,*ain4cf

ActivationMo&e ActivationMo&e ActivationMo&e ActivationMo&e BserverA Bserver BserverC BserverD 8 8 8 8 C C C C *.s'are&g *.s'are&g *.s'are&g *.s'are&g 8 8 8 8 s3 s3 s3 s3 D D D D

serverA # cfs&ga&* &is(la.

No&e Na*e ! serverA D1SE GROU6 *.s'are&g No&e Na*e ! server D1SE GROU6 *.s'are&g No&e Na*e ! serverC D1SE GROU6 *.s'are&g No&e Na*e ! serverD D1SE GROU6 *.s'are&g ACT1VAT1ON MODE s3 ACT1VAT1ON MODE s3 ACT1VAT1ON MODE s3 ACT1VAT1ON MODE s3

;e ca! !ow create &olumes a!d filesystems withi! the shared dis)$rou"#

serverA # v)assist -g *.s'are&g *a5e *.s'arevol% %22g serverA # v)assist -g *.s'are&g *a5e *.s'arevol: %22g serverA # *5fs -/ v)fs ,&ev,v),r&s5,*.s'are&g,*.s'arevol% serverA # *5fs -/ v)fs ,&ev,v),r&s5,*.s'are&g,*.s'arevol:

The! add these &olumes%filesystems to the cluster co!fi$uratio! so they ca! e mou!ted o! a!y or all !odes# Mou!t"oi!ts will e automatically created#

serverA # cfs*nta&* a&& *.s'are&g *.s'arevol% ,*ount(oint%

Mount 6oint is +eing a&&e&444 ,*ount(oint% a&&e& to t'e cluster-configuration

serverA # cfs*nta&* a&& *.s'are&g *.s'arevol: ,*ount(oint:

Mount 6oint is +eing a&&e&444 ,*ount(oint: a&&e& to t'e cluster-configuration

1is"lay the CFS mou!t co!fi$uratio!s i! the cluster#

serverA # cfs*nta&* &is(la. -v

Cluster Configuration for No&e! a(=*a#%@ MOUNT 6O1NT T-6E SFARED VOLUME ,*ount(oint% Regular *.s'arevol% ,*ount(oint: Regular *.s'arevol: D1SE GROU6 *.s'are&g *.s'are&g STATUS NOT MOUNTED NOT MOUNTED MOUNT O6T1ONS cr3 cr3

That9s it# Chec) you cluster co!fi$uratio! a!d try to 38+<8@ the filesystems o! your !odes#

serverA # 'astatus -su*

-- S-STEM STATE -- S.ste* A A A A serverA server serverC serverD State RUNN1NG RUNN1NG RUNN1NG RUNN1NG S.ste* serverA server serverC serverD serverA server serverC serverD 2 2 2 2 6ro+e& N N N N AutoDisa+le& State ONL1NE ONL1NE ONL1NE ONL1NE N N N N N N N N O//L1NE O//L1NE O//L1NE O//L1NE O//L1NE O//L1NE O//L1NE O//L1NE /ro0en

-- GROU6 STATE -- Grou(

cv* serverA cv* server cv* serverC cv* serverD vrts<vea<cfs<int<cfs*ount% vrts<vea<cfs<int<cfs*ount% vrts<vea<cfs<int<cfs*ount% vrts<vea<cfs<int<cfs*ount% vrts<vea<cfs<int<cfs*ount: vrts<vea<cfs<int<cfs*ount: vrts<vea<cfs<int<cfs*ount: vrts<vea<cfs<int<cfs*ount:

@ach &olume will ha&e its ow! Ser&ice $rou" a!d loo)s really u$ly, so you may wa!t to modify your mai!#cf file a!d $rou" them# ,e creati&eA