27.02.2013 Views

ExpressCluster X 2.0 for Windows Reference Guide - Nec

ExpressCluster X 2.0 for Windows Reference Guide - Nec

ExpressCluster X 2.0 for Windows Reference Guide - Nec

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Activation<br />

failure<br />

Section II Resource details<br />

Server1 Server2<br />

Monitor resource<br />

Disk TUR monitor<br />

resource 1<br />

Monitor<br />

error<br />

Monitor<br />

error<br />

Shared disk<br />

Server1 Server2<br />

Monitor resource<br />

Disk TUR monitor<br />

resource 1<br />

Failover<br />

Group A<br />

Disk<br />

Application 1<br />

Floating 1IP<br />

resource 1<br />

Shared<br />

disk<br />

Monitor resource<br />

Disk TUR monitor<br />

resource 1<br />

Failover Group A<br />

Disk resource 1<br />

Application resource<br />

Floating 1 IP<br />

resource 1<br />

Monitor<br />

error<br />

Monitor resource<br />

Disk TUR<br />

monitor resource<br />

1<br />

Monitor<br />

error<br />

Monitor resources<br />

Failover of the failover group A<br />

due to detection of the error by<br />

the disk TUR monitor resource<br />

1 starts in server2.<br />

“Failover threshold” of the<br />

monitor resource is a failover<br />

count on a server basis.<br />

Activation<br />

failure<br />

Server1:<br />

Disk TUR Monitor Resource 1:<br />

Failover count 1<br />

Disk Resource 1:<br />

Failover count 1<br />

Server2:<br />

Disk TUR Monitor Resource 1:<br />

Failover count 1<br />

Disk Resource 1<br />

Failover count 1<br />

Activating the disk resource<br />

1 due to failover fails in<br />

server1.<br />

(failure of fsck, mount, etc.)<br />

Server1:<br />

Disk TUR Monitor Resource 1:<br />

Failover count 1<br />

Disk Resource 1:<br />

Failover count 1<br />

Server2:<br />

Disk TUR Monitor Resource 1:<br />

Failover count 1<br />

Disk Resource 1:<br />

Failover count 1<br />

The final action is executed in server1 as is the case in server2 because the number of failovers<br />

due to failure of activating the disk resource 1 has exceeded the threshold.<br />

However, note that activation ends abnormally without activating the rest of the group resources<br />

in the Failover Group A because “No operation (Next resources are not activated)” is selected as<br />

the final action.<br />

An error can be detected in deactivation of the disk resource depending on the location of the<br />

disk device failure.<br />

579

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!