• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
SRM versus Stretched Clusters: Choosing the Right Solution
 

SRM versus Stretched Clusters: Choosing the Right Solution

on

  • 14,937 views

 

Statistics

Views

Total Views
14,937
Views on SlideShare
3,144
Embed Views
11,793

Actions

Likes
1
Downloads
123
Comments
1

11 Embeds 11,793

http://blog.scottlowe.org 11586
http://feeds.scottlowe.org 151
http://www.newsblur.com 19
http://localhost 13
http://translate.googleusercontent.com 10
http://feeds.feedburner.com 4
http://127.0.0.1 3
http://webcache.googleusercontent.com 3
http://core.traackr.com 2
http://radar.metrica.net 1
https://www.google.com 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Apple Keynote

Usage Rights

CC Attribution License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

11 of 1 previous next

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • Would love the audio for this also but I am not sure how to accomplish that.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n

SRM versus Stretched Clusters: Choosing the Right Solution SRM versus Stretched Clusters: Choosing the Right Solution Presentation Transcript

  • Before we start• Get involved!• If you use Twitter, feel free to tweet about this session (use hashtag #AusVMUG or #VMUG)•I encourage you to take photos or videos of today’s session and share them online• Thispresentation will be made available online after the event
  • Comparing SRM withStretched ClustersFinding the right solution for your organisation’s needs Scott Lowe, VCDX 39 vExpert, Author, Blogger, Geek http://blog.scottlowe.org / Twitter: @scott_lowe
  • Agenda• Quick review of terminology• Comparing SRM and vMSC requirements• Comparing SRM and vMSC advantages• Comparing SRM and vMSC disadvantages• Mixing SRM and vMSC
  • RPO versus RTO• RPO = Recovery Point Objective• RPO is a measure of how much data loss the organisation is willing to sustain• RTO = Recovery Time Objective• RTO is a measure of how long of a wait the organisation is willing to tolerate before recovery is complete
  • DR versus DA• DA = Disaster avoidance • Seeks to protect apps/data before a disaster occurs • Howoften do you know before a disaster is going to occur?• DR = Disaster recovery • Seeks to recover apps/data after a disaster occurs• Think of DA as vMotion and DR as vSphere HA
  • Requirements for vMSC• Some form of supported synchronous active/active storage architecture• Stretched Layer 2 connectivity between sites• 622 Mbps bandwidth (minimum) between sites• Lessthan 5 ms latency between sites (10 ms with vSphere 5 Enterprise Plus/Metro vMotion)•A single vCenter Server instance
  • Requirements for SRM• Some form of supported storage replication (synchronous or asynchronous)• Layer 3 connectivity• Nominimum inter-site bandwidth requirements (driven by SLA/RPO/RTO)• No maximum latency between sites (driven by SLA/RPO/ RTO)• At least two vCenter Server instances
  • Advantages of vMSC• Thepossibility of non-disruptive workload migration (disaster avoidance)• No need to deal with issues changing IP addresses• Potentialfor running active/active data centres and more easily balancing workloads between them• Typically a near-zero RPO with RTO of minutes• Requires only a single vCenter Server instance
  • Advantages of SRM• Defined startup orders (with prerequisites)• No need for stretched Layer 2 connectivity (but supported)• Theability to simulate workload mobility without affecting production• Supports multiple vCenter Server instances (including in Linked Mode)
  • Disadvantages of vMSC• Greaterphysical networking complexity due to stretched Layer 2 connectivity requirement• Greater cost resulting from higher-end networking equipment, more bandwidth, active/active storage solution• No ability to test workload mobility• Operational overhead from management of DRS host affinity groups• Supports only a single vCenter Server instance
  • Disadvantages of SRM• Typically higher RPO and RTO than stretched clusters• Workload mobility is always disruptive• Requires at least two vCenter Server instances• Operationaloverhead from managing protection groups and protection plans
  • What about a mixedarchitecture?• It can be done, but it has its own set of design considerations• For any given workload, its an “either/or” situation
  • Diagram of a mixedarchitecture
  • Additional Resources• BCO2479 from VMworld 2011 also takes up comparing SRM and vMSC• Any of my stretched cluster presentations (all available on my site, blog.scottlowe.org) discuss pros/cons and design considerations
  • Questions &Answers
  • Thank you!