Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Disaster Recover   April 2011
About Orcon…first and foremost, an Internet Service Provider     Over 50 thousand broadband connections, with our own acc...
About OrconSome technical detail:     Our own voice and broadband access network – 60 exchanges in 8 cities     POPs in ...
About OrconSome technical detail:     Our own voice and broadband access network – 60 exchanges in 8 cities     POPs in ...
About OrconInternational networkImage credit: San Diego History Centrehttp://www.sandiegohistory.org/education/light8/inde...
About OrconNew Zealand networkImage credit: Enchanted Learninghttp://www.enchantedlearning.com/oceania/newzealand/outlinem...
About OrconApplications and data...     Most applications developed internally           BSS (billing           OSS (pr...
Data and ApplicationsExample application - Cosmos
Design to Fail…using Cosmos as our example application:     Multiple application frontends     GSLB system in front of i...
Design to FailOther ideas we’ve had     cloud-based frontends     cloud-based databases?     challenges – local perform...
Design to FailExample – ChristchurchScenario – Christchurch, but in AucklandScenario – Japan, but affecting western seaboa...
WrapupDesign to fail, or expect failureConsider global eventsConsider global or regional coverageConsider local presence
Upcoming SlideShare
Loading in …5
×

Disaster Recovery

298 views

Published on

Session on disaster recovery

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

Disaster Recovery

  1. 1. Disaster Recover April 2011
  2. 2. About Orcon…first and foremost, an Internet Service Provider  Over 50 thousand broadband connections, with our own access network  Over 100 thousand total internet and voice customers  Several thousand business customers, including:  Datacenter services  Metro Ethernet  Voice (SIP)  International data  Hosting
  3. 3. About OrconSome technical detail:  Our own voice and broadband access network – 60 exchanges in 8 cities  POPs in 13 New Zealand locations  2 datacenters – Auckland and Wellington  Large international presence – sites in Australia and the United States  Lots of network capacity!  10Gb international network AKL-SYD-LOS  Multiple Gb nationally  Multiple 10Gb metro AKL
  4. 4. About OrconSome technical detail:  Our own voice and broadband access network – 60 exchanges in 8 cities  POPs in 13 New Zealand locations  2 datacenters – Auckland and Wellington  Large international presence – sites in Australia and the United States  Lots of network capacity!  10Gb international network AKL-SYD-LOS  Multiple Gb nationally  Multiple 10Gb wavelengths metro AKL
  5. 5. About OrconInternational networkImage credit: San Diego History Centrehttp://www.sandiegohistory.org/education/light8/index.htm
  6. 6. About OrconNew Zealand networkImage credit: Enchanted Learninghttp://www.enchantedlearning.com/oceania/newzealand/outlinemap/
  7. 7. About OrconApplications and data...  Most applications developed internally  BSS (billing  OSS (provisioning)  “Other”  Housed in our own datacenters in Auckland and Wellington  Lots of data  Financial and accounting (billing, GL, debtors, etc.)  Business data (products, services, processes, IP, etc.)  Customer-centric data (CDRs, usage logs, personal data)  Customer-owned data (email, websites, databases, etc.)
  8. 8. Data and ApplicationsExample application - Cosmos
  9. 9. Design to Fail…using Cosmos as our example application:  Multiple application frontends  GSLB system in front of it  Load balance sessions to different frontends  Any can fail – sessions will be dropped, can log into another instance  Replicated database behind it
  10. 10. Design to FailOther ideas we’ve had  cloud-based frontends  cloud-based databases?  challenges – local performance, soveregncy, service levels, security, isolation  room for local cloud?These may or may not turn into products that we sell to others as well 
  11. 11. Design to FailExample – ChristchurchScenario – Christchurch, but in AucklandScenario – Japan, but affecting western seaboard of USScenario – fire, malicious intent, network outage, loss of hardware/data loss
  12. 12. WrapupDesign to fail, or expect failureConsider global eventsConsider global or regional coverageConsider local presence

×