disaster recovery
DESCRIPTION
Session on disaster recoveryTRANSCRIPT
Disaster Recover
April 2011
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
About Orcon
Some 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
About Orcon
Some 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
About Orcon
International network
Image credit: San Diego History Centrehttp://www.sandiegohistory.org/education/light8/index.htm
About Orcon
New Zealand network
Image credit: Enchanted Learninghttp://www.enchantedlearning.com/oceania/newzealand/outlinemap/
About Orcon
Applications 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.)
Data and Applications
Example application - Cosmos
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
Design to Fail
Other 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
Design to Fail
Example – Christchurch
Scenario – Christchurch, but in AucklandScenario – Japan, but affecting western seaboard of USScenario – fire, malicious intent, network outage, loss of hardware/data loss
Wrapup
Design to fail, or expect failureConsider global eventsConsider global or regional coverageConsider local presence