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

227 views
192 views

Published on

Session on disaster recovery

Published in: Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
227
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Capacity == opportunityMakes some things easier
  • Mostly GE, some 10GE in metro centers
  • Data == 10s of TBLots of different databases, moving to consolidateLots of storage platforms, moving to consolidateComparison figure = approx 1GB of data transmitted across the network per second (international) = over 80tb / day (excludes local, e.g. google, akamai, tvnz, etc.
  • Billing systemStores all customer dataStores all service dataDebtors ledgerCustomer portalDrives websiteDrives signupsOSM – java/webobjects, oracle SE database, DBVisit replication3x application servers2x databasesAny 1 can run
  • Billing systemStores all customer dataStores all service dataDebtors ledgerCustomer portalDrives websiteDrives signupsOSM – java/webobjects, oracle SE database, DBVisit replication3x application servers2x databasesAny 1 can run
  • Auckland – hub of New Zealands technology. Highly vulnerable to failure of Harbour Bridge. Southern Cross – 2 landing stations in NZ, within 20km of each other.Japan earthquake – 5 completely independent cable systems damaged. NTT (Japan incumbent) able to route around on other cable systems.No such chance in NZ.US – westcoast = “center of the internet”Los Angeles / Palo Also = 1 Wilshire, PAIX, MAE West, Equinix, Coresite, etc.Peering point for all major telcos in the worldAnd most of the minor ones – many have their only US presence there
  • Auckland – hub of New Zealands technology. Highly vulnerable to failure of Harbour Bridge. Southern Cross – 2 landing stations in NZ, within 20km of each other.Japan earthquake – 5 completely independent cable systems damaged. NTT (Japan incumbent) able to route around on other cable systems.No such chance in NZ.US – westcoast = “center of the internet”Los Angeles / Palo Also = 1 Wilshire, PAIX, MAE West, Equinix, Coresite, etc.Peering point for all major telcos in the worldAnd most of the minor ones – many have their only US presence there
  • 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

    ×