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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 11 The system maintenance in<strong>for</strong>mation<br />

How to replace a server with a new one<br />

750<br />

When you replace a server in a cluster environment, follow the instructions below:<br />

1. Set up a new server in the same way as the failed server.<br />

• When using a shared disk, do not connect the new server to the shared disk yet.<br />

• Set the same computer name and IP address as the failed server.<br />

• Register the <strong>ExpressCluster</strong> license and apply updates as they have been registered and<br />

applied be<strong>for</strong>e.<br />

• If there were cluster partition and/or data partition of a mirror disk or hybrid disk on the<br />

local disk of the failing server, allocate these partitions and assign drive letters <strong>for</strong> them<br />

as they were configured in the failing server. When you use the disk of the failing<br />

server, configure drive letters <strong>for</strong> the partitions, though allocating partitions is not<br />

necessary.<br />

• When using a shared disk, set the SCSI controller or the HBA that is connected to the<br />

shared disk to be filtered in Filter Settings of Shared Disk upon installing the<br />

<strong>ExpressCluster</strong> Server.<br />

• After the setup, shut it down and power it off.<br />

Important:<br />

In Filter Settings of Shared Disk, set the SCSI controller or the HBA that is connected to<br />

the shared disk to be filtered. If the new server is connected to the shared disk when it has<br />

not been set to be filtered, data on the shared disk may be corrupted.<br />

2. If the failed server is still running, shut it down and remove it from the shared disk and the<br />

LAN, and make sure other servers in the cluster are working properly. (Ignore errors caused<br />

by the failed server being stopped.)<br />

3. Start the new server while it is connected to the LAN. When using a shared disk, start the<br />

server while it is also connected to the shared disk.<br />

4. When using the shared disk, on the new server, use Disk Management (On the Start menu,<br />

point to Settings, and click Control Panel. Double-click Administrative Tools and then<br />

Computer Management, and click Disk Management.) to confirm that the shared disk is<br />

visible, and set the same drive letter as the failed server.<br />

• At this point, access to the shared disk is controlled, so the disk data cannot be referred.<br />

5. Connect to a server in normal operation in the cluster by using the Web browser to start the<br />

Builder. When using a shared disk, click Properties, HBA tab and Connect on the new<br />

server to check or modify the in<strong>for</strong>mation on HBA and partitions.<br />

Important:<br />

On the HBA tab of Properties of the new server, set the SCSI controller or the HBA that is<br />

connected to the shared disk to be filtered. If the shared disk is connected when it has not<br />

been set to be filtered, data on the shared disk may be corrupted.<br />

6. When there is any mirror disk resource or hybrid disk resource in the resources used in the<br />

new server, stop the failover group containing these resources from the WebManager.<br />

7. Run “clpcl --suspend --<strong>for</strong>ce” from the command prompt on the server in normal operation<br />

in the cluster and suspend the cluster.<br />

• A server is recognized to have stopped, so the cluster cannot be suspended from the<br />

WebManager.<br />

<strong>ExpressCluster</strong> X <strong>2.0</strong> <strong>for</strong> <strong>Windows</strong> <strong>Reference</strong> <strong>Guide</strong>

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

Saved successfully!

Ooh no, something went wrong!