• EVA 8400
• P6300 (FC and iSCSI)
• P6500 (FC and iSCSI)
• MSA P2000 G3 FC
• MSA P2000 G3 (FC and iSCSI)
• MSA P2000 G3 SAS
• MSA P2000 G3 10GbE iSCSI
• MSA P2000 G3 1GbE iSCSI
• MSA 2300/2400 series G2 (FC and iSCSI)
• MSA 2300/2400 series SAS G2
The following technical brief addressing SCSI-3 persistent reservations is accessible from the Red Hat
Customer Portal (subscription required):
How to Control Access to Shared Storage Devices Using SCSI Persistent Reservations with Red
Hat Enterprise Linux Clustering and High Availability
https://access.redhat.com/knowledge/techbriefs/how-control-access-shared-storage-devices-
using-scsi-persistent-reservations-re
Disaster tolerant configurations
Cluster technology is commonly used for maintaining application availability during loss or failure of
a physical site, fire cell, or other localized collection of computing resources. This capability is often
referred to as disaster tolerance or disaster recovery. Disaster tolerant systems can be constructed
using the High Availability Add-on and its associated products, and Red Hat supports two different
general system topologies for this purpose. HP offers storage array products designed to make
storage volumes disaster tolerant, and these products can be used in RHEL clusters in specific
circumstances.
The following Knowledgebase article describes the supported disaster-tolerant RHEL cluster
configurations:
Support for Red Hat Enterprise Linux Cluster and High Availability Stretch Architectures
https://access.redhat.com/kb/docs/DOC-58412
Multi-site disaster recovery cluster configurations
The preferred Red Hat disaster tolerant or multi-site configuration consists of two independent and
essentially identical clusters, each located at a physically separate location (this is sometimes referred
to as a multi-cluster). This configuration is active/passive, meaning that only one cluster (the active
cluster) is able to run services at a time; the other cluster is inactive. If shared cluster storage is used, it
must be replicated from the active to the passive site synchronously, using an array-based method.
Storage replicas are only accessible on the active site; they are not accessible on the passive site.
Red Hat does not impose a distance limitation between sites, though the storage array used will
typically impose a limit.
Site-level management of RHEL multi-cluster system configurations is largely manual, though selective
scripting and use of available tools can reduce workload and improve reliability and repeatability.
The cluster administrator must duplicate resource and service definitions and applications in the
clusters on each site and maintain them in synchrony. Site failover must be managed manually by the
cluster administrator; this includes powering up the passive cluster, storage array failover, and
resynchronization — as needed. The cluster administrator must also manually manage recovery from
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Kommentare zu diesen Handbüchern