82 lines
5.4 KiB
HTML
82 lines
5.4 KiB
HTML
<?xml version="1.0" encoding="utf-8"?>
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
|
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<meta name="dc.language" scheme="rfc1766" content="en-us" />
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
|
<!-- US Government Users Restricted Rights -->
|
|
<!-- Use, duplication or disclosure restricted by -->
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
|
<meta name="dc.date" scheme="iso8601" content="2005-09-13" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="security" content="public" />
|
|
<meta name="Robots" content="index,follow"/>
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
|
<title>Problems hot sparing between servers</title>
|
|
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
|
|
<link rel="stylesheet" type="text/css" href="ic.css" />
|
|
</head>
|
|
<body>
|
|
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
|
|
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
|
|
|
|
<img src="delta.gif" alt="Start of change" />
|
|
<a name="rzahqprobhotspare"></a>
|
|
<h3 id="rzahqprobhotspare">Problems hot sparing between servers</h3>
|
|
<p>The main reason that hot sparing between integrated servers might fail
|
|
is hardware compatibility. Windows Server 2003 activation may also cause
|
|
problems. See the following sections for details.</p>
|
|
<p><span class="bold">Hot spare hardware compatibility</span></p>
|
|
<p>Switching a Windows server from one set of integrated server hardware to
|
|
another is like migrating the Windows system drive from one PC to a second
|
|
PC. Differences in the required hardware abstraction layer (HAL), the basic
|
|
input/output system (BIOS) level, or the devices that are installed on the
|
|
two PCs can cause problems with the migration. During the initial boot of
|
|
Windows on the second PC, hardware differences are detected and are handled
|
|
in one of several ways:</p>
|
|
<p></p>
|
|
<ul>
|
|
<li>Some hardware differences can be automatically handled via plug and play.</li>
|
|
<li>Some hardware differences may require manual intervention. For example
|
|
a new device driver may need to be installed.</li>
|
|
<li>If the hardware differences are great enough, they can prevent the second
|
|
PC from booting. For example, the two PCs may require incompatible versions
|
|
of the HAL.</li></ul>
|
|
<p>These same hardware compatibility considerations apply when hot sparing
|
|
between IXS servers, between IXA attached xSeries® servers and between iSCSI attached IBM® xSeries or BladeCenter™ servers. In order for the hot spare migration
|
|
to work successfully, the hardware configurations of the two servers should
|
|
be closely matched.</p>
|
|
<p><span class="bold">Integrated xSeries Server (IXS) hot spare</span></p>
|
|
<p>In order to use hot spare between IXS servers, they should be compatible
|
|
types and they should have a comparable configuration of LAN adapters, etc.
|
|
The Integrated xSeries server configurations table on the following web
|
|
page gives the specific IXS hot spare configurations that are supported: <a href="http://www.ibm.com/servers/eserver/iseries/integratedxseries/ixs_system_config.html">http://www.ibm.com/eserver/iseries/integratedxseries/ixs_system_config.html</a>.</p>
|
|
<p><span class="bold">xSeries or IBM BladeCenter server hot spare</span></p>
|
|
<p>In order to use hot spare between IXA attached xSeries servers
|
|
or between iSCSI attached xSeries or IBM BladeCenter servers, it is strongly recommended
|
|
that you use the same type of xSeries or IBM BladeCenter blade servers. For example, an xSeries model 236 can be a hot spare for another xSeries model 236.
|
|
In addition, the xSeries servers should have a similar configuration of
|
|
PCI adapters, and so on.</p>
|
|
<a name="wq426"></a>
|
|
<div class="notetitle" id="wq426">Note:</div>
|
|
<div class="notebody">It may be possible to hot spare between two xSeries or blade
|
|
server models that are not the same type. However, there are often significant
|
|
hardware differences between xSeries or blade models. Therefore, you should
|
|
test the specific combination of xSeries or blade server models that you plan
|
|
to use for hot spare in this case. You should test to verify that the xSeries or blade server models have compatible hardware configurations
|
|
and can be migrated seamlessly between each other before you use them for
|
|
hot spare server backup in a production environment.</div>
|
|
<p><span class="bold">Windows Server 2003 activation</span></p>
|
|
<p>Each time a Windows Server 2003 server's storage spaces are switched to
|
|
another hot spare integrated server, Windows Activation may be triggered.
|
|
There are a limited number of free activations per license key. If activation
|
|
is triggered enough times, this may require a phone call to Microsoft in order
|
|
to re-activate. This can limit the speed that a server can be re-activated.
|
|
Volume licenses of Windows Server 2003 can help in this case, since activation
|
|
is not required.</p><img src="deltaend.gif" alt="End of change" />
|
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
|
</body>
|
|
</html>
|