A cluster consists of a pair of NetApp filers that are connected and configured in a special way to provide fault tolerance. When one filer in a cluster undergoes a system failure and can't reboot, the partner filer in the cluster can take over the failed filer's functions and serve the data on the failed filer's disks. This is known as a takeover. In addition to an automatic takeover, an operator may issue a cf takeover command at any time to force a takeover.
The filers in a cluster have the following characteristics:
If one filer in a cluster stops functioning physically, its partner filer:
When the failed filer is functioning again:
This chapter discusses the topics described in the following table.
| Read... | To learn about... |
|---|---|
| "Understanding cluster concepts" | What clusters are and how they work. |
| "Configuring interfaces for takeover" | How to configure interfaces to maintain connectivity if a takeover occurs. |
| "Understanding takeover" | How the takeover process works and its result. |
| "Understanding giveback" | How the giveback process works. |
| "Managing a cluster" | How to manage a cluster in general. |
| "Managing the cluster in normal mode" | How to manage a cluster when no takeover has taken place. |
| "Managing takeover" | How to manage a cluster after a takeover has taken place. |
| "Managing filers in takeover mode" | How to manage the filer that has taken over its partner. |
| "Managing a virtual filer" | How to manage the virtual filer that represents the filer that has been taken over. |
| "Performing a giveback" | How to restore a cluster to normal operation. |
Copyright © 1999, Network Appliance, Inc. All rights reserved.
Part No. 210-02334
File: clust.htm
Last updated: 02/24/99 12:16:47