HP LH4r Novell NetWare Cluster Services for NetWare 5 Installation guide - Page 10

Web Site A moves to Web Server 2 and Web Site B moves to Web Server 3. IP

Page 10 highlights

Web Site A moves to Web Server 2 and Web Site B moves to Web Server 3. IP addresses and applicable licenses also move to Web Server 2 and Web Server 3. When you configured the cluster, you decided where the Web sites hosted on each Web server would go should a failure occur. In the previous example you configured Web Site A to move to Web Server 2 and Web Site B to move to Web Server 3. This way, the workload once handled by Web Server 1 is evenly distributed. When Web Server 1 failed, NetWare Cluster Services software • Detected a failure. • Restarted applications (that were running on Web Server 1) on Web Server 2 and Web Server 3 as specified. • Transferred IPaddresses to Web Server 2 and Web Server 3 as specified. • Remounted the shared data volumes (that were formerly mounted on Web server 1) on Web Server 2 and Web Server 3 as specified. In this example, the failover process happened quickly and users regained access to the Internet, Web site information, and e-mail within seconds, and in most cases, without having to log in again. Now suppose the problems with Web Server 1 are resolved, and Web Server 1 is returned to a normal operating state. Web Site A and Web Site B will automatically failback, or be moved back to Web Server 1, and Web Server operation will return back to the way it was before Web Server 1 failed. NetWare Cluster Services also provides resource migration capabilities. You can move applications, Web sites, etc. to other servers in your cluster without waiting for a server to fail. For example, you could have manually moved Web Site A or Web Site B from Web Server 1 to either of the other servers in the cluster. You might want to do this to upgrade or perform scheduled maintenance on Web Server 1, or just to increase performance or accessibility of the Web sites. 4 Overview and Installation

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34

4
Overview and Installation
Web Site A moves to Web Server 2 and Web Site B moves to Web Server 3. IP
addresses and applicable licenses also move to Web Server 2 and Web Server 3.
When you configured the cluster, you decided where the Web sites hosted on
each Web server would go should a failure occur. In the previous example you
configured Web Site A to move to Web Server 2 and Web Site B to move to
Web Server 3. This way, the workload once handled by Web Server 1 is evenly
distributed.
When Web Server 1 failed, NetWare Cluster Services software
Detected a failure.
Restarted applications (that were running on Web Server 1) on Web
Server 2 and Web Server 3 as specified.
Transferred IPaddresses to Web Server 2 and Web Server 3 as specified.
Remounted the shared data volumes (that were formerly mounted on
Web server 1) on Web Server 2 and Web Server 3 as specified.
In this example, the failover process happened quickly and users regained
access to the Internet, Web site information, and e-mail within seconds, and in
most cases, without having to log in again.
Now suppose the problems with Web Server 1 are resolved, and Web Server 1
is returned to a normal operating state. Web Site A and Web Site B will
automatically failback, or be moved back to Web Server 1, and Web Server
operation will return back to the way it was before Web Server 1 failed.
NetWare Cluster Services also provides resource migration capabilities. You
can move applications, Web sites, etc. to other servers in your cluster without
waiting for a server to fail.
For example, you could have manually moved Web Site A or Web Site B from
Web Server 1 to either of the other servers in the cluster. You might want to do
this to upgrade or perform scheduled maintenance on Web Server 1, or just to
increase performance or accessibility of the Web sites.