1 / 17

Stratus ® SplitSite ®

Stratus ® SplitSite ®. Presenter Title. Presenter Name. Date. Agenda. The objectives of the workshop are: Understand what Stratus SplitSite is and isn ’ t Describe the supported configurations Understand the network requirements Describe how to deploy it.

lave
Download Presentation

Stratus ® SplitSite ®

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Stratus® SplitSite® Presenter Title Presenter Name Date

  2. Agenda The objectives of the workshop are: Understand what Stratus SplitSite is and isn’t Describe the supported configurations Understand the network requirements Describe how to deploy it

  3. An option for Stratus® everRun MX Express®, Stratus® everRun MX Enterprise®, Stratus® everRun FT®, Stratus® everRun HA®(note 1) It can be added at any time There is an additional cost for SplitSite Provides disaster resilience by maintaining application availability between systems located in different, independent sites These sites can be: In different rooms or floors of the same building In different buildings in a complex or campus In different cities or towns (note 1) SplitSite for everRun FT and HA are not covered in this workshop

  4. More About Stratus SplitSite SplitSite extends the core capabilities of the Stratus® everRun® software to support geographic separation with synchronization links routed over a switched LAN or WAN It is a disaster recovery (DR) solution that provides the same fault tolerance as non-SplitSite (note 1) RPO (Recovery Point Objective) of zero, and RTO (Recovery Time Objective) of zero No Single Point of Failure SplitSite is configured with two host pools (note 1) Requires Level 3 protection for zero RPO/RTO and No Single Point of Failure

  5. Stratus® everRun SplitSite® vs. Stratus® everRun MX Extend® Stratus everRun SplitSite • RPO/RTO of zero • Requires 155 Mb/sec and 10 ms RTT per PVM for L2 and L3 Uniprocessor • Requires 1 Gb/sec and 2 ms RTT per PVM for SMP L3 • Automatic recovery Stratus everRun MX Extend • RPO/RTO of minutes • Network bandwidth requirements can be tuned based on traffic and RPO requirements • Manual failoverand failback recommended Notes RPO: Recovery Point Objective RTO: Recovery Time Objective RTT: Round Trip Time Note MX Extend is an asynchronous data replication and high availability product

  6. How Does Stratus SplitSite Work? • SplitSite maintains continuous availability across sites using dual synchronization links over standard (1 or 10) Gigabit Ethernet • The traffic can be routed over a switched wide area network (WAN) • SplitSite requires: • Two hosts, one at each site • One or two (preferred) Quorum® servers at one or two additional sites • Network configuration, bandwidth, and latency to support the application load • Production network(s) on common subnet (or virtual local area network – VLAN) between sites

  7. Network Considerations andQuorum Placement • SplitSite allows site redundancy • Users need to have continuous access to both sites in the event of a site disaster • Users must use the same IP/MAC address to connect to both sites • A Layer 2 network is necessary between the sites (common subnet or VLAN) for client traffic • Network wiring cannot be a single point of failure • One conduit carrying all the traffic will fail at some point • Commonly referred to as a “backhoe event” • Locating the quorum servers at the same site as the hosts defeats their purpose • If the site goes down, so do the quorum servers • If both quorum servers fail, so do all applications

  8. Environment Stratus Confidential • SplitSite will be as reliable and redundant as the network infrastructure it is running on • Fault tolerance means having: • No Single point of failure • Redundant sites • Redundant virtual machines (VMs) • Redundant hosts • Redundant switches • Redundant gateways • Redundant network wiring (paths) • A single point of failure will fail eventually

  9. Option A:Local Two-Host Pool

  10. Stratus SplitSite Diagrams Stratus Confidential • Physical • Redundant connections • Network • Bandwidth and latency • Routing • Subnets and VLANs (note 1) SplitSite for everRun FT and HA are not covered in this workshop

  11. Stratus SplitSite Network Diagram Stratus Confidential

  12. Site Routing Tables Stratus Confidential

  13. Quorum Service Routing Stratus Confidential

  14. A-Link Performance Specifications Stratus Confidential • Latencies: • 10 ms RTT or less Uniprocessor L3 or L2 • 2 ms RTT or less SMP L3 • Speed/Bandwidth • Uniprocessor L3 or L2: 155 Mbps or greater per PVM • SMP L3: 2 x 1 Gbit full-duplex minimum • Each A-Link should exceed aggregated bandwidth of all production LANs for all PVMs, including storage and recovery traffic

  15. Benefits of Quorum Stratus Confidential • Quorum service prevents split-brain or dual master-ship (even when not in a SplitSite configuration) • Enables automatic start of CIs/AMs of one host when the other host does not power on

  16. Deployment Stratus Confidential • It is suggested to build the two servers in the same location first • Building and testing the hosts locally removes network issues during the initial setup • To remove variables, use the same switches and routers that will be used in production if possible • Confirm that SplitSite is configured correctly first • Then deploy the hosts to their respective sites • If there are any problems, you know it is the network, not SplitSite

  17. Summary Stratus Confidential • Stratus SplitSite provides disaster resilience by maintaining application availability between systems located in different, independent sites • Is an optional add-on for everRun MX Express or everRun MX Enterprise editions • SplitSite prevents data from becoming partitioned (corrupted) if the connections between sites fail

More Related