- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- REdhat 5 cluster on hp r2600 with eva
Operating System - Linux
1752525
Members
4678
Online
108788
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-04-2010 10:29 PM
тАО08-04-2010 10:29 PM
Hi
New to clusters but company i am working for has grown and now wants to implment a cluster.
requirements are as follows redhat 5.4
2 r2600 itanium boxes.
2 eva's
the eva will replicate data from /data1 to /data1 area on second eva. Have hp continuous access
the nodes will be attached to both eva.
The cluster nodes when failing will failover to each other.
The caveat is that they want in the case of a total disaster that the node that is active with the active eva must fail over to the other node as well as the replicated data on the second eva or the replicated to eva.
Has anyone done this before and where would i find a how to or document to read to set this type of environment up in.
Thank you in advance
New to clusters but company i am working for has grown and now wants to implment a cluster.
requirements are as follows redhat 5.4
2 r2600 itanium boxes.
2 eva's
the eva will replicate data from /data1 to /data1 area on second eva. Have hp continuous access
the nodes will be attached to both eva.
The cluster nodes when failing will failover to each other.
The caveat is that they want in the case of a total disaster that the node that is active with the active eva must fail over to the other node as well as the replicated data on the second eva or the replicated to eva.
Has anyone done this before and where would i find a how to or document to read to set this type of environment up in.
Thank you in advance
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-05-2010 12:39 AM
тАО08-05-2010 12:39 AM
Solution
> The caveat is that they want in the case of a total disaster that the node that is active with the active eva must fail over to the other node as well as the replicated data on the second eva or the replicated to eva.
So, a storage failover in addition to the node failover. In the HP-UX world, this would be covered by the MetroCluster add-on to the Serviceguard cluster framework. But a RedHat Cluster does not have anything like that as a ready-to-use component, so you'll have to add this feature on your own if you want *automatic* storage failover.
(If a *manual* failover in case of a loss of EVA is acceptable, the problem is easier: just design and test the procedures required to switch the cluster [or what is left of it] to the replicated EVA, and *document those procedures in exhaustive detail*.)
To achieve MetroCluster-like functionality using RedHat Cluster, you'll have to find out the commands you'll need to give to the EVA in the event of a storage failover, create a script that sends those commands automatically and add that script as a resource to the definition of a RedHat cluster service (= package in Serviceguard terminology).
Because this action must be the first when starting up the clustered service, all the other resources of that service must be "children" of that resource.
For example:
<script name="switch_eva_replication" file="/usr/local/sbin/switch_eva_replication.sh">
</script>
The /usr/local/sbin/switch_eva_replication.sh script should be written sort of like a /etc/init.d startup script: the cluster will invoke it with the "start" parameter when starting up the clustered service, and with the "stop" parameter when stopping it.
The script must assume that the other node may have failed abruptly: it might have burned to a crisp or been flooded by 10000 litres of raw sewage. Therefore, the "start" action of the script should be prepared to do all the necessary work, whatever it takes. The "stop" action can be empty.
You also cannot use a quorum disk. A quorum disk would have to be on a single EVA and would be a weak point in your cluster: if one node *and* the EVA that contains the quorum disk fails, your cluster cannot automatically failover to the remaining node.
If you're new to clusters in general, I'd strongly suggest you to go on a cluster administration course. I can recommend RedHat's RH436, "Clustering and Storage Management". While it does not cover storage failover, it will give you general RedHat cluster knowledge and some experience in its use.
MK
So, a storage failover in addition to the node failover. In the HP-UX world, this would be covered by the MetroCluster add-on to the Serviceguard cluster framework. But a RedHat Cluster does not have anything like that as a ready-to-use component, so you'll have to add this feature on your own if you want *automatic* storage failover.
(If a *manual* failover in case of a loss of EVA is acceptable, the problem is easier: just design and test the procedures required to switch the cluster [or what is left of it] to the replicated EVA, and *document those procedures in exhaustive detail*.)
To achieve MetroCluster-like functionality using RedHat Cluster, you'll have to find out the commands you'll need to give to the EVA in the event of a storage failover, create a script that sends those commands automatically and add that script as a resource to the definition of a RedHat cluster service (= package in Serviceguard terminology).
Because this action must be the first when starting up the clustered service, all the other resources of that service must be "children" of that resource.
For example:
<script name="switch_eva_replication" file="/usr/local/sbin/switch_eva_replication.sh">
</script>
The /usr/local/sbin/switch_eva_replication.sh script should be written sort of like a /etc/init.d startup script: the cluster will invoke it with the "start" parameter when starting up the clustered service, and with the "stop" parameter when stopping it.
The script must assume that the other node may have failed abruptly: it might have burned to a crisp or been flooded by 10000 litres of raw sewage. Therefore, the "start" action of the script should be prepared to do all the necessary work, whatever it takes. The "stop" action can be empty.
You also cannot use a quorum disk. A quorum disk would have to be on a single EVA and would be a weak point in your cluster: if one node *and* the EVA that contains the quorum disk fails, your cluster cannot automatically failover to the remaining node.
If you're new to clusters in general, I'd strongly suggest you to go on a cluster administration course. I can recommend RedHat's RH436, "Clustering and Storage Management". While it does not cover storage failover, it will give you general RedHat cluster knowledge and some experience in its use.
MK
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-05-2010 01:01 AM
тАО08-05-2010 01:01 AM
Re: REdhat 5 cluster on hp r2600 with eva
just checked they dont offer that training in my country.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-05-2010 09:02 PM
тАО08-05-2010 09:02 PM
Re: REdhat 5 cluster on hp r2600 with eva
I think what you really want is CLX (http://h18000.www1.hp.com/products/quickspecs/12456_na/12456_na.HTML ). It is now supported with native Red Hat clustering.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP