Cloud DR: Leveraging Cloud Computing for Cheap Hot Sites

CLOUD DISASTER RECOVERY Leveraging Cloud Computing for Cheap Hot Sites

MESenior Linux System Administrator for MNX Solutions; MSP in Monroe

MESenior Linux System Administrator for MNX Solutions; MSP in MonroeBuilt/taught Linux curriculum for Eastern Michigan University

MESenior Linux System Administrator for MNX Solutions; MSP in MonroeBuilt/taught Linux curriculum for Eastern Michigan UniversityPreviously the cloud computing subject matter expert for ePrize

MESenior Linux System Administrator for MNX Solutions; MSP in MonroeBuilt/taught Linux curriculum for Eastern Michigan UniversityPreviously the cloud computing subject matter expert for ePrize Deployed multi-cloud provider scalable infrastructure to handle Super Bowl advertising traffic for two digital promotions in 2010

MESenior Linux System Administrator for MNX Solutions; MSP in MonroeBuilt/taught Linux curriculum for Eastern Michigan UniversityPreviously the cloud computing subject matter expert for ePrize Deployed multi-cloud provider scalable infrastructure to handle Super Bowl advertising traffic for two digital promotions in 2010Hold the Certificate of Cloud Security Knowledge (CCSK) from theCloud Security Alliance

MESenior Linux System Administrator for MNX Solutions; MSP in MonroeBuilt/taught Linux curriculum for Eastern Michigan UniversityPreviously the cloud computing subject matter expert for ePrize Deployed multi-cloud provider scalable infrastructure to handle Super Bowl advertising traffic for two digital promotions in 2010Hold the Certificate of Cloud Security Knowledge (CCSK) from theCloud Security AlliancePresent at events on configuration management & scalability in cloudcomputing and other elastic infrastructure

Disaster Recovery Plans

Disaster Recovery PlansCold Site: Location is prepared to service a failure without anyexisting hardware or backup data deployed

Disaster Recovery PlansCold Site: Location is prepared to service a failure without anyexisting hardware or backup data deployedWarm Site: Location is prepared to service a failure withhardware on the ready but not likely to have backup data there orat a smaller scale of capacity than a hot site

Disaster Recovery PlansCold Site: Location is prepared to service a failure without anyexisting hardware or backup data deployedWarm Site: Location is prepared to service a failure withhardware on the ready but not likely to have backup data there orat a smaller scale of capacity than a hot siteHot Site: Full production setting with near-complete backupdata already deployed and ready to turn the key if there’s a failure

DRP: Cost Versus Benefit

DRP: Cost Versus BenefitA hot site is obviously the most cost prohibitive as you want fullparity to your existing environment in order to supportproduction needs on a whim; this is rarely cheap!

DRP: Cost Versus BenefitA hot site is obviously the most cost prohibitive as you want fullparity to your existing environment in order to supportproduction needs on a whim; this is rarely cheap!A warm site gives you a middle ground between preparednessand savings in that you may not be fully able to sustain 100%production computing but you’re able to get back online fastwith some capacity much quicker than a cold site

DRP: Cost Versus BenefitA hot site is obviously the most cost prohibitive as you want fullparity to your existing environment in order to supportproduction needs on a whim; this is rarely cheap!A warm site gives you a middle ground between preparednessand savings in that you may not be fully able to sustain 100%production computing but you’re able to get back online fastwith some capacity much quicker than a cold siteA cold site is cheap as you basically just have a shell of a plandeployed and have to get the rest together only if there is a failure

Why Do Hot Sites Cost So Much?

Why Do Hot Sites Cost So Much?Considerations for Cost:

Why Do Hot Sites Cost So Much?Considerations for Cost: Server, network, and storage hardware duplication from main site

Why Do Hot Sites Cost So Much?Considerations for Cost: Server, network, and storage hardware duplication from main site Power needs are same as main site

Why Do Hot Sites Cost So Much?Considerations for Cost: Server, network, and storage hardware duplication from main site Power needs are same as main site Network costs are likely the same as the main site

Why Do Hot Sites Cost So Much?Considerations for Cost: Server, network, and storage hardware duplication from main site Power needs are same as main site Network costs are likely the same as the main site Man power to stage, manage, and sanity check second environment

Why Do Hot Sites Cost So Much?Considerations for Cost: Server, network, and storage hardware duplication from main site Power needs are same as main site Network costs are likely the same as the main site Man power to stage, manage, and sanity check second environment Courier costs for off-site backups to be brought to the hot site

So What About ‘The Cloud’?

So What About ‘The Cloud’?Cloud computing allows for on-demand, elastic, measured,pooled service (infrastructure, platform, software) with broadnetwork access

So What About ‘The Cloud’?Cloud computing allows for on-demand, elastic, measured,pooled service (infrastructure, platform, software) with broadnetwork accessA hot site needs resources that are ready to implement, canquickly scale-up, able to provide adequate network connectivity,and has data at the ready

So What About ‘The Cloud’?Cloud computing allows for on-demand, elastic, measured,pooled service (infrastructure, platform, software) with broadnetwork accessA hot site needs resources that are ready to implement, canquickly scale-up, able to provide adequate network connectivity,and has data at the readyWith the essential tenets of ‘cloud computing’ (as defined byNIST) being thought of in relation to hot sites, there’s anobvious correlation that could be leveraged

Cloud Hot Site Benefits

Cloud Hot Site BenefitsYou can stage resources, put them ‘offline’ and pay minimal datastorage costs until you need to deploy them (‘spin them up’)

Cloud Hot Site BenefitsYou can stage resources, put them ‘offline’ and pay minimal datastorage costs until you need to deploy them (‘spin them up’)Data storage costs are rather cheap: $0.10/GB at Amazon WebServices; $0.15/GB at Rackspace Cloud

Cloud Hot Site BenefitsYou can stage resources, put them ‘offline’ and pay minimal datastorage costs until you need to deploy them (‘spin them up’)Data storage costs are rather cheap: $0.10/GB at Amazon WebServices; $0.15/GB at Rackspace CloudNo overhead data center, power, networking, or hardware costs

Cloud Hot Site BenefitsYou can stage resources, put them ‘offline’ and pay minimal datastorage costs until you need to deploy them (‘spin them up’)Data storage costs are rather cheap: $0.10/GB at Amazon WebServices; $0.15/GB at Rackspace CloudNo overhead data center, power, networking, or hardware costsDeployment of cloud resources are not relegated to one datacenter; stage your resources in many states or even countrieswith one provider and the same methodologies

Making the Business Case

Making the Business CaseLet’s talk about the Small and Medium Business (SMB):

Making the Business CaseLet’s talk about the Small and Medium Business (SMB): Don’t necessarily have the money to duplicate their 10 or 20 servers + networking + storage + power + facility costs

Making the Business CaseLet’s talk about the Small and Medium Business (SMB): Don’t necessarily have the money to duplicate their 10 or 20 servers + networking + storage + power + facility costs Want to be fault-tolerant and have a DRP/BCP that works

Making the Business CaseLet’s talk about the Small and Medium Business (SMB): Don’t necessarily have the money to duplicate their 10 or 20 servers + networking + storage + power + facility costs Want to be fault-tolerant and have a DRP/BCP that works Pleasing customers is of the utmost priority; can’t afford to lose people due to downtime

Making the Business CaseLet’s talk about the Small and Medium Business (SMB): Don’t necessarily have the money to duplicate their 10 or 20 servers + networking + storage + power + facility costs Want to be fault-tolerant and have a DRP/BCP that works Pleasing customers is of the utmost priority; can’t afford to lose people due to downtime Can make the leap to a public cloud provider more easily due to the limited scope of computing resources needed

Framing Our Scenario

Framing Our ScenarioCompany Type: Web radio streaming for regional FM stations

Framing Our ScenarioCompany Type: Web radio streaming for regional FM stationsInfrastructure: Five servers @ $200/mo each 1 Load Balancer, 3 Web Servers, 1 Database Server

Framing Our ScenarioCompany Type: Web radio streaming for regional FM stationsInfrastructure: Five servers @ $200/mo each 1 Load Balancer, 3 Web Servers, 1 Database ServerBandwidth Usage: 5 TB/Month (167GB/Day)

Framing Our ScenarioCompany Type: Web radio streaming for regional FM stationsInfrastructure: Five servers @ $200/mo each 1 Load Balancer, 3 Web Servers, 1 Database ServerBandwidth Usage: 5 TB/Month (167GB/Day)Storage Usage: 400GB total across servers

Framing Our ScenarioCompany Type: Web radio streaming for regional FM stationsInfrastructure: Five servers @ $200/mo each 1 Load Balancer, 3 Web Servers, 1 Database ServerBandwidth Usage: 5 TB/Month (167GB/Day)Storage Usage: 400GB total across serversOther: 2 Static IPs; Linux Servers (8GB RAM; 4 x 2GHz Cores)

Framing Our Scenario, Cont.

Framing Our Scenario, Cont.General Amazon Web Services Cost Factors:

Framing Our Scenario, Cont.General Amazon Web Services Cost Factors: Static IP: In use is free; $0.01/hr if not, per IP

Framing Our Scenario, Cont.General Amazon Web Services Cost Factors: Static IP: In use is free; $0.01/hr if not, per IP Storage: $0.10/GB + $0.10/million I/O requests

Framing Our Scenario, Cont.General Amazon Web Services Cost Factors: Static IP: In use is free; $0.01/hr if not, per IP Storage: $0.10/GB + $0.10/million I/O requests Bandwidth: $0.125/GB (In/Out Cost Average)

Framing Our Scenario, Cont.General Amazon Web Services Cost Factors: Static IP: In use is free; $0.01/hr if not, per IP Storage: $0.10/GB + $0.10/million I/O requests Bandwidth: $0.125/GB (In/Out Cost Average) Load Balancer: $0.025/hr + $0.008/GB transfer

Framing Our Scenario, Cont.General Amazon Web Services Cost Factors: Static IP: In use is free; $0.01/hr if not, per IP Storage: $0.10/GB + $0.10/million I/O requests Bandwidth: $0.125/GB (In/Out Cost Average) Load Balancer: $0.025/hr + $0.008/GB transfer Servers: TBD based on which option is in use

Cheap and Dirty Cloud DR

Cheap and Dirty Cloud DR1. Use a single t1.micro EC2 instance (1.7GB RAM, 1 x 1.8Ghz Core)

Cheap and Dirty Cloud DR1. Use a single t1.micro EC2 instance (1.7GB RAM, 1 x 1.8Ghz Core)2. Build an EC2 Linux volume with ~500GB of storage + OS installed

Cheap and Dirty Cloud DR1. Use a single t1.micro EC2 instance (1.7GB RAM, 1 x 1.8Ghz Core)2. Build an EC2 Linux volume with ~500GB of storage + OS installed3. Install the database and web server software + configs and starting data points

Cheap and Dirty Cloud DR1. Use a single t1.micro EC2 instance (1.7GB RAM, 1 x 1.8Ghz Core)2. Build an EC2 Linux volume with ~500GB of storage + OS installed3. Install the database and web server software + configs and starting data points4. Register 1 static IP address for the database server

Cheap and Dirty Cloud DR1. Use a single t1.micro EC2 instance (1.7GB RAM, 1 x 1.8Ghz Core)2. Build an EC2 Linux volume with ~500GB of storage + OS installed3. Install the database and web server software + configs and starting data points4. Register 1 static IP address for the database server5. Create a rudimentary script that will:

Cheap and Dirty Cloud DR1. Use a single t1.micro EC2 instance (1.7GB RAM, 1 x 1.8Ghz Core)2. Build an EC2 Linux volume with ~500GB of storage + OS installed3. Install the database and web server software + configs and starting data points4. Register 1 static IP address for the database server5. Create a rudimentary script that will: 1. Boot the EC2 instance on a given schedule (likely once an hour)

Cheap and Dirty Cloud DR1. Use a single t1.micro EC2 instance (1.7GB RAM, 1 x 1.8Ghz Core)2. Build an EC2 Linux volume with ~500GB of storage + OS installed3. Install the database and web server software + configs and starting data points4. Register 1 static IP address for the database server5. Create a rudimentary script that will: 1. Boot the EC2 instance on a given schedule (likely once an hour) 2. Synchronize server files + SQL data + configurations files (deltas only)

Cheap and Dirty Cloud DR1. Use a single t1.micro EC2 instance (1.7GB RAM, 1 x 1.8Ghz Core)2. Build an EC2 Linux volume with ~500GB of storage + OS installed3. Install the database and web server software + configs and starting data points4. Register 1 static IP address for the database server5. Create a rudimentary script that will: 1. Boot the EC2 instance on a given schedule (likely once an hour) 2. Synchronize server files + SQL data + configurations files (deltas only) 3. Shut the EC2 instance back down

Example DRP Run Book

Example DRP Run Book1. Take the existing one EC2 instance and create three more copies

Example DRP Run Book1. Take the existing one EC2 instance and create three more copies2. Change the instance type from t1.micro to m1.large 1. m1.large provides 7.5GB of RAM, 4 x 1.8GHz cores

Example DRP Run Book1. Take the existing one EC2 instance and create three more copies2. Change the instance type from t1.micro to m1.large 1. m1.large provides 7.5GB of RAM, 4 x 1.8GHz cores3. Assign the database server its static IP address

Example DRP Run Book1. Take the existing one EC2 instance and create three more copies2. Change the instance type from t1.micro to m1.large 1. m1.large provides 7.5GB of RAM, 4 x 1.8GHz cores3. Assign the database server its static IP address4. Associate the three web server instances with an elastic load balancer

Example DRP Run Book1. Take the existing one EC2 instance and create three more copies2. Change the instance type from t1.micro to m1.large 1. m1.large provides 7.5GB of RAM, 4 x 1.8GHz cores3. Assign the database server its static IP address4. Associate the three web server instances with an elastic load balancer5. Edit DNS to point hosts to the new load balancer + database server

Example DRP Run Book1. Take the existing one EC2 instance and create three more copies2. Change the instance type from t1.micro to m1.large 1. m1.large provides 7.5GB of RAM, 4 x 1.8GHz cores3. Assign the database server its static IP address4. Associate the three web server instances with an elastic load balancer5. Edit DNS to point hosts to the new load balancer + database server6. Alter configurations as needed and restore recent SQL data

Example DRP Run Book1. Take the existing one EC2 instance and create three more copies2. Change the instance type from t1.micro to m1.large 1. m1.large provides 7.5GB of RAM, 4 x 1.8GHz cores3. Assign the database server its static IP address4. Associate the three web server instances with an elastic load balancer5. Edit DNS to point hosts to the new load balancer + database server6. Alter configurations as needed and restore recent SQL data7. Start services and execute some sort of sanity check script

Breaking Down Costs Monthly Carrying CostsServer $0.085/HR 120 HRS $10.20Storage $0.100/GB 500 GB $50.00Bandwidth $0.125/GB 250 GB $31.25Static IPs $0.010/HR 720 HRS $7.20Balancer Time $0.025/HR 0 HRS $0.00Balancer Data $0.008/GB 0 GB $0.00 Monthly Total: $98.65 10 minutes of ‘server time’ per hour for data synchronization 250GB of deltas a month for production data versus EC2 DR site

Breaking Down Costs, cont. DR Cutover Costs for ONE WEEKServer $0.340/HR 4 x 168 HRS $228.48Storage $0.100/GB 4 x 500 GB $46.66Bandwidth $0.125/GB 1.176TB $147.00Static IPs $0.010/HR 0 HRS $0.00Balancer Time $0.025/HR 168 HRS $4.20Balancer Data $0.008/GB 1.176TB $9.41 One Week Total: $435.75 ...or $1,867 a month; $867 more a month than usual

Cheap and Dirty DR Review

Cheap and Dirty DR ReviewFor less than $100 a month you can scale from 1 meager, part-time instance up to 4 powerful instances with a load balancer inaround 10 minutes if needed

Cheap and Dirty DR ReviewFor less than $100 a month you can scale from 1 meager, part-time instance up to 4 powerful instances with a load balancer inaround 10 minutes if neededConfiguration and data are less than an hour old generally

Cheap and Dirty DR ReviewFor less than $100 a month you can scale from 1 meager, part-time instance up to 4 powerful instances with a load balancer inaround 10 minutes if neededConfiguration and data are less than an hour old generally$1,200 a year for an efficient, on-demand disaster recovery site;equivalent to just over 1 month of normal production operation

Cheap and Dirty DR ReviewFor less than $100 a month you can scale from 1 meager, part-time instance up to 4 powerful instances with a load balancer inaround 10 minutes if neededConfiguration and data are less than an hour old generally$1,200 a year for an efficient, on-demand disaster recovery site;equivalent to just over 1 month of normal production operationThis disaster recovery site isn’t going to be cheaper to run, butit’s not made for that purpose; only in an emergency!

Cheap and Dirty DR ReviewFor less than $100 a month you can scale from 1 meager, part-time instance up to 4 powerful instances with a load balancer inaround 10 minutes if neededConfiguration and data are less than an hour old generally$1,200 a year for an efficient, on-demand disaster recovery site;equivalent to just over 1 month of normal production operationThis disaster recovery site isn’t going to be cheaper to run, butit’s not made for that purpose; only in an emergency!But we can still do a bit better...

Improvements to Cloud DR

Improvements to Cloud DRLower DNS TTLs on records that will be changing; stage your CNAMEfor the load balancer and database static IP address so it’s ready to go

Improvements to Cloud DRLower DNS TTLs on records that will be changing; stage your CNAMEfor the load balancer and database static IP address so it’s ready to goUtilize configuration management solutions like Puppet to helpsynchronize data & configuration in a more organized, efficient way

Improvements to Cloud DRLower DNS TTLs on records that will be changing; stage your CNAMEfor the load balancer and database static IP address so it’s ready to goUtilize configuration management solutions like Puppet to helpsynchronize data & configuration in a more organized, efficient wayRun your t1.micro instance constantly and setup SQL slave replicationrather than copying SQL dumps (with SSL of course...)

Improvements to Cloud DRLower DNS TTLs on records that will be changing; stage your CNAMEfor the load balancer and database static IP address so it’s ready to goUtilize configuration management solutions like Puppet to helpsynchronize data & configuration in a more organized, efficient wayRun your t1.micro instance constantly and setup SQL slave replicationrather than copying SQL dumps (with SSL of course...)Create an autoscaling group that will continue to add resources toimprove your hot site as demand hits the servers

Potential Additional Savings

Potential Additional SavingsResize your Amazon volume to reasonable sizes and synchronize datato your new servers when you execute your run book; this will save onthe 500GB volumes for each host you’d otherwise have

Potential Additional SavingsResize your Amazon volume to reasonable sizes and synchronize datato your new servers when you execute your run book; this will save onthe 500GB volumes for each host you’d otherwise haveWith an autoscale group, start with one web server and add more/lesscapacity as needed to help reduce costs when you failover to cloud

Potential Additional SavingsResize your Amazon volume to reasonable sizes and synchronize datato your new servers when you execute your run book; this will save onthe 500GB volumes for each host you’d otherwise haveWith an autoscale group, start with one web server and add more/lesscapacity as needed to help reduce costs when you failover to cloudUtilize t1.micro instances for your web servers rather than m1.largeand auto-scale smaller units of capacity for more granular savings

Potential Additional SavingsResize your Amazon volume to reasonable sizes and synchronize datato your new servers when you execute your run book; this will save onthe 500GB volumes for each host you’d otherwise haveWith an autoscale group, start with one web server and add more/lesscapacity as needed to help reduce costs when you failover to cloudUtilize t1.micro instances for your web servers rather than m1.largeand auto-scale smaller units of capacity for more granular savingsBuy a reserved EC2 instance and save even more on carrying-cost

Potential Additional SavingsResize your Amazon volume to reasonable sizes and synchronize datato your new servers when you execute your run book; this will save onthe 500GB volumes for each host you’d otherwise haveWith an autoscale group, start with one web server and add more/lesscapacity as needed to help reduce costs when you failover to cloudUtilize t1.micro instances for your web servers rather than m1.largeand auto-scale smaller units of capacity for more granular savingsBuy a reserved EC2 instance and save even more on carrying-costConsider a different off-site storage provider who may be cheaper

Who This is Good For?

Who This is Good For?If you or a client needs to have a reliable infrastructure but doesn’tnecessarily have a budget to match their necessity, look into doing acloud disaster recovery site

Who This is Good For?If you or a client needs to have a reliable infrastructure but doesn’tnecessarily have a budget to match their necessity, look into doing acloud disaster recovery siteIf you don’t have a situation where public cloud infrastructure is aregulatory no-no or other legal impediments would prevent it

Who This is Good For?If you or a client needs to have a reliable infrastructure but doesn’tnecessarily have a budget to match their necessity, look into doing acloud disaster recovery siteIf you don’t have a situation where public cloud infrastructure is aregulatory no-no or other legal impediments would prevent itYou or your IT staff can feel comfortable with a given cloud provider,Amazon or otherwise, to implement a solution that leverages the bestthey have to offer for the least cost

Who This is Good For?If you or a client needs to have a reliable infrastructure but doesn’tnecessarily have a budget to match their necessity, look into doing acloud disaster recovery siteIf you don’t have a situation where public cloud infrastructure is aregulatory no-no or other legal impediments would prevent itYou or your IT staff can feel comfortable with a given cloud provider,Amazon or otherwise, to implement a solution that leverages the bestthey have to offer for the least cost...or you’re just looking for a reason still to use a real cloud provider ;)

Oh, and Don’t Forget... ...New AWS Customers Get... For FREE for the ﬁrst year! http://aws.amazon.com/free/

Oh, and Don’t Forget... ...New AWS Customers Get...750 hours of EC2 running Linux/Unix Micro instance usage For FREE for the ﬁrst year! http://aws.amazon.com/free/

Oh, and Don’t Forget... ...New AWS Customers Get...750 hours of EC2 running Linux/Unix Micro instance usage750 hours of Elastic Load Balancing plus 15 GB data processing For FREE for the ﬁrst year! http://aws.amazon.com/free/

Oh, and Don’t Forget... ...New AWS Customers Get...750 hours of EC2 running Linux/Unix Micro instance usage750 hours of Elastic Load Balancing plus 15 GB data processing10 GB of Amazon Elastic Block Storage (EBS) plus 1 million IOs, 1GB snapshot storage, 10,000 snapshot Get Requests and 1,000snapshot Put Requests For FREE for the ﬁrst year! http://aws.amazon.com/free/

Oh, and Don’t Forget... ...New AWS Customers Get...750 hours of EC2 running Linux/Unix Micro instance usage750 hours of Elastic Load Balancing plus 15 GB data processing10 GB of Amazon Elastic Block Storage (EBS) plus 1 million IOs, 1GB snapshot storage, 10,000 snapshot Get Requests and 1,000snapshot Put Requests15 GB of bandwidth in and 15 GB of bandwidth out aggregated acrossall AWS services For FREE for the ﬁrst year! http://aws.amazon.com/free/

Thank You! Questions?mark.stanislav@gmail.com@markstanislavuncompiled.com

Cloud DR: Leveraging Cloud Computing for Cheap Hot Sites

by Mark Stanislav on May 18, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

1 Embed 1

Statistics

Cloud DR: Leveraging Cloud Computing for Cheap Hot Sites — Presentation Transcript