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.

Chapter 12 Troubleshooting<br />

This chapter provides instructions <strong>for</strong> troubleshooting problems with <strong>ExpressCluster</strong>.<br />

This chapter covers:<br />

• Troubleshooting···································································································································· 772<br />

• When the <strong>ExpressCluster</strong> system does not start or end·········································································· 772<br />

• When activating or deactivating network partition resolution resource fails·········································· 773<br />

• When a network partition resolution resource error is detected ····························································· 773<br />

• Network partition resolution resource becomes unavailable·································································· 773<br />

• When activating or deactivating group resources fails··········································································· 774<br />

• When a monitor resource error occurs··································································································· 774<br />

• When a heartbeat time-out occurs ········································································································· 774<br />

• Recovering from failure of one server··································································································· 774<br />

• Recovering from failure of both servers ································································································ 774<br />

• Recovering a suspended server (with unresolved network partition) ····················································· 775<br />

• When network partitioning occurs ········································································································ 776<br />

• Unavailable commands when interconnections are disconnected ·························································· 779<br />

• Connecting mirror disks/hybrid disks manually ···················································································· 780<br />

• Normally connecting mirror disk when mirroring is available······························································· 780<br />

• Forcibly connecting mirror disk when mirroring is not available ·························································· 780<br />

• Recovering from mirror breaks ············································································································· 781<br />

• Automatically recovering from mirroring ····························································································· 781<br />

• Checking the mirror break status with a command················································································ 783<br />

• Checking the mirror recovery progress with a command······································································· 784<br />

• Recovering mirror with a command······································································································ 784<br />

• Running the <strong>for</strong>cible mirror recovery with a command ········································································· 786<br />

• Running the <strong>for</strong>cible mirror recovery with a command only on one server············································ 787<br />

• Checking the mirror break status from the WebManager ······································································ 788<br />

• Checking the mirror recovery progress from the WebManager ····························································· 789<br />

• Recovering mirror using the WebManager···························································································· 791<br />

• Running the <strong>for</strong>cible mirror recovery using the WebManager······························································· 791<br />

• Running the <strong>for</strong>cible mirror recovery from the WebManager only on one server ·································· 793<br />

• Media sense function becomes invalid ·································································································· 793<br />

771

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

Saved successfully!

Ooh no, something went wrong!