Scale-on-Scale : Part 3 of 3 - Disaster Recovery

724 views

Published on

Published in: Technology
1 Comment
0 Likes
Statistics
Notes
  • http://lp.scalecomputing.com/scale_on_scale_webinar_pt_3.html

    Disaster Recovery: How Scale Computing Uses Its Own Storage Solutions for DR

    Watch a video of Scale Computing’s Director of IT, William Waller, present the disaster recovery slide deck above and the approach that Scale Computing takes for their DR procedures.

    http://lp.scalecomputing.com/scale_on_scale_webinar_pt_3.html
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

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

No notes for slide

Scale-on-Scale : Part 3 of 3 - Disaster Recovery

  1. 1. How Scale Computing uses Scale's ICOS Storage Webcast 3 of 3 – Using Scale for Disaster Recovery Bill Waller Director of IT
  2. 2. Agenda Server/Application Recovery Tips Disaster Recovery Plan Basics Who is Scale? ICOS Why have a DR Plan? Scale Production Environment Backup and Retention
  3. 3. Who is Scale? <ul><li>Founded in 2007, Scale Computing has led the way in unified, scale-out, enterprise class storage for small and medium-sized enterprises. The company is rapidly growing with offices in California, Indianapolis and London with global distribution partners. </li></ul>
  4. 4. Scale ICOS <ul><li>Every Scale storage cluster is powered by ICOS™ Technology: an advanced storage operating system combining powerful features with intelligence that makes storage easy-to-manage, even for novices. </li></ul>Generation 3.0 Storage Scale-Out Architecture Capacity Performance Density Agnostic Unified SAN/NAS No Controllers Thin Provisioning Global Namespace Replication Auto-load balancing Snapshots
  5. 5. Why Have a Disaster Recovery Plan? <ul><li>System/Data loss is very expensive </li></ul><ul><ul><li>Hardware Malfunction </li></ul></ul><ul><ul><li>Human Error </li></ul></ul><ul><ul><li>Software Corruption </li></ul></ul><ul><ul><li>Computer Virus </li></ul></ul><ul><ul><li>Natural Disaster </li></ul></ul><ul><li>Government Regulation Compliance </li></ul><ul><ul><li>Sarbanes-Oxley Act (SOA) </li></ul></ul><ul><ul><li>Health Insurance Portability and Accountability Act (HIPAA) </li></ul></ul><ul><ul><li>European Union Data Protection Directive </li></ul></ul><ul><ul><li>Patriot Act </li></ul></ul>Ontrack Survey 2006
  6. 6. Backup & Retention <ul><li>Disk and Tape both have a place for Backup/DR </li></ul><ul><li>Disk-Based Backup: </li></ul><ul><ul><li>Automated Process (No need to load/rotate media) </li></ul></ul><ul><ul><li>Scalable/Highly Available/Redundant storage </li></ul></ul><ul><li>Tape-Based Backup: </li></ul><ul><ul><li>Manual Process (Rotate media) </li></ul></ul><ul><ul><li>Multiple redundant backup sets </li></ul></ul><ul><li>For Disaster Recovery, you will want the most recent backups </li></ul><ul><li>Take regular backups of your Critical Data </li></ul><ul><li>Always retain multiple tested backups </li></ul>
  7. 7. Why Plans are Not Made $
  8. 8. DR Plan Basics <ul><li>“ Only half of all companies have a DR Plan. Of those that do, nearly half have never tested their plan, which is like not having one at all.” </li></ul><ul><li>Document all critical systems – Business will not function without them (first to recover) </li></ul><ul><li>Document system owners – Who is responsible for each system </li></ul><ul><li>Document support contracts, contact information, and SLA’s </li></ul><ul><li>Document system configurations </li></ul><ul><li>Store your DR Plan off-site </li></ul><ul><li>Backup System Data regularly </li></ul><ul><li>Test, Test, Test! </li></ul>
  9. 9. Steps to Plan
  10. 10. <ul><li>The measurements of data protection are: </li></ul><ul><ul><li>The acceptable amount of time spent to reinstate access to data following a disruption. </li></ul></ul><ul><ul><li>The acceptable amount of data lost in an outage event, measured in time </li></ul></ul>RTO and RPO RTO = Recovery Time Objective RPO = Recovery Point Objective
  11. 11. Scale Production Environment <ul><li>Multiple 3-Node R4 Scale Storage Cluster (12TB) </li></ul><ul><ul><li>Redundant Power and Network Interface Cards (NICs) </li></ul></ul><ul><li>Scale’s Production Environment </li></ul><ul><ul><li>100% Virtualized Environment (ESXi 4.1) </li></ul></ul><ul><ul><li>Exchange 2010 (DAG) </li></ul></ul><ul><ul><li>Windows 2008 R2 (Domain Controllers/Active Directory) </li></ul></ul><ul><ul><li>Linux/CentOS (Web Site/MySQL/Atlassian Tools) </li></ul></ul><ul><ul><li>45 Virtual Machines </li></ul></ul><ul><li>ICOS Snapshots/Replication Off-site </li></ul><ul><li>Symantec BackupExec 2010 </li></ul><ul><ul><li>Backup for Exchange 2010 </li></ul></ul><ul><ul><li>Backup for vmWare ESXi </li></ul></ul>
  12. 12. Server/Application Recovery Tips <ul><li>Keep multiple copies of your DR Plan and one off-site </li></ul><ul><li>Store copies of application software off-site </li></ul><ul><li>Document the application installation instructions in your DR plan </li></ul><ul><li>Determine remote or local restore (RTO) </li></ul><ul><li>Document support numbers, contract information, and SLA’s </li></ul><ul><li>Easily restore data to ICOS Scale Storage </li></ul>
  13. 13. January 2012 – Scale Production <ul><li>Scale Production </li></ul><ul><li>Physical/Virtualization </li></ul><ul><li>Unified Storage </li></ul><ul><li>Distributed Environment Strategies </li></ul><ul><li>ROBO (Remote/Back Office) </li></ul><ul><li>Monitoring </li></ul>
  14. 14. Questions? Bill Waller Director of IT [email_address] Twitter: WallerWilliam

×