- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- StoreVirtual Storage
- >
- P4500 create cluster, standard or multi-stie, and ...
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
тАО06-03-2011 04:04 PM
тАО06-03-2011 04:04 PM
P4500 create cluster, standard or multi-stie, and other questions
Do I use a FOM and where do I put it. And how do I recover from a site disaster where lose 2 nodes and the fom @ the same time?
K
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2011 08:42 PM
тАО06-03-2011 08:42 PM
Re: P4500 create cluster, standard or multi-stie, and other questions
Ping times between the 2 sites should be less than 2 milli seconds.
Yes with MultiSite you should group Storage Nodes and Servers together based on Site.
FOM is recommended to be installed on the 3rd Site if possible.
--------------------------------------------------------------
How to assign points? Click the KUDOS! star!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-04-2011 01:33 AM
тАО06-04-2011 01:33 AM
Re: P4500 create cluster, standard or multi-stie, and other questions
Why do I need a multi-cluster for 2 local sites, with the sam subnet and in saniq9 I can have site notion win a standard cluster?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-04-2011 06:47 AM
тАО06-04-2011 06:47 AM
Re: P4500 create cluster, standard or multi-stie, and other questions
Typically the 2 "sites" are on different power circuits and/or backup sources.
Yes, the Failover Manager needs to be either at a 3rd (phys or logical) site, or at one of the primary 2 sites. (remember, the site that still has communication with the FOM is the site that will remain UP during a link failure)
Multi-Site SAN has to comprise of (2) subnets. I have done 2 stretched VLANs and presented BOTH subnets to BOTH sites. Each subnet has its own VIP for your iSCSI gateway, and if you design both subnets to stretch to both sites then you can use BOTH VIPs in your discovery. (this gives you some storage pathing redundancy if you are using virtualization for example).
Another consideration is that you cannot use Network RAID 5 within multi-site. You must use Network RAID 10 (2 way mirror) because of coure to maintain availability during a site or link failure there must always be 2 complete copies of your data.
If you are not concerned about distributing your SAN across multiple buildings within your campus, then the multi-site SAN may not be the configuration to employ.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-04-2011 02:13 PM
тАО06-04-2011 02:13 PM
Re: P4500 create cluster, standard or multi-stie, and other questions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-04-2011 06:53 PM
тАО06-04-2011 06:53 PM
Re: P4500 create cluster, standard or multi-stie, and other questions
When servers and storage nodes are assigned to sites using the HP P4000 CMC:
HP P4000 DSM sessions are automatically connected to only the storage systems that are in the same site as the host sever. This reduces overall session count and improves performance by favoring IO connections to storage systems that are more local to the host.
All other (non HP P4000 DSM) sessions are automatically load balanced to storage systems in the same site if the volume is not already being accessed at another site.
I would recommend using the MultiSite functionality so you can have you Hosts talking to local Nodes (which should have much lower ping times compared to the Other location)
--------------------------------------------------------------
How to assign points? Click the KUDOS! star!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-14-2012 10:54 AM
тАО10-14-2012 10:54 AM
Re: P4500 create cluster, standard or multi-stie, and other questions
hi, first we setup standart cluster with 2 node, when we add 2 node to our disaster side can we convert them to multi site cluster?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-15-2012 09:31 AM
тАО10-15-2012 09:31 AM
Re: P4500 create cluster, standard or multi-stie, and other questions
if they are in the same management group then you COULD convert it to a multi-site cluster, but unless you have a requirement for syncronous data replication offsite, I would highly suggest you stick with your DR site as asyncronous. There are just many complications to creating a multi-site cluster that you might not want to deal with. You will suddenly have to be very concerned about bandwith, LATENCY, and availability of your link. These issues are not as critical with a remote replication site as with a multi-site cluster. If you go multi-site, figure your SAN speed will be limited to the latency of your WAN connection as well as the bandwidth of the SAN connection. Typically a company that is only running off of two P4000 series systems doesn't want to pay for that kind of direct connection between locations unless you happen to have a campus and you control the fiber between "sites".
Its most likely best to just keep your two new VSAs in their own management group and run remote replication between the groups and read up on the failover/failback procedures for that setup.