HP StorageWorks 8000 NAS - Manual (Page 29)

NAS 8000 Concepts 27
NA
S 80
00
C
on
cep
ts
Failover Packages
Failover packages are the smallest unit of failover within the cluster. A
package contains necessary definitions and configuration information
relating to resources and their processes that must be failed over to the
secondary server in the event the primary server fails. Each cluster can have a
maximum of 30 packages running concurrently. For NAS, the package
defines the volumes (file systems) and their associated CIFS shares and NFS
exports that should be failed over. A given volume group can be defined in
only one package at a time, but a package can contain multiple volume
group definitions. The packages can fail over automatically when a server
fails, or they can be manually failed over one at a time. A given package can
be running on only one cluster node at a time.
Think of a package as a group of one or more volume groups (with their file
systems and shares/exports) that will fail over as a single unit. To fail over a
package manually, you need to:
■ Stop the existing package (in the case of a service, network, or resource
failure).
■ Start the new instance of the package on a different node.
You can manage failover packages on the Storage tab of the Command View
NAS web interface.
Eliminating Single Points of Failure
Most problems that result in service outages are single-level failures. High-
availability lets you quickly detect and handle these failures and minimize
downtime. Examples of single-level failures include:
■ NIC failures
■ NFS failure
■ SMB failure
■ Operating system failure
■ Power failure