Availability Considerations for SQL Server Deployments<br />Bob Roudebush, Neverfail<br />1/27/2010<br />
Neverfail Company Overview<br />Our Focus<br />Delivering world-class Continuous Availability software for High Availabili...
Is There A Better Option for Protecting SQL?<br />Need for Disaster Recovery Strategies is Undeniable.<br />61% of North A...
Degrees of protection for information systems:<br />So you need to make your SQL Server deployment bulletproof?<br />Data ...
Business Case for SQL Availability<br />High Availability<br />Disaster Recovery<br />Keep business-critical applications ...
What Should You Protect?<br />Application Data Stores<br />Databases<br />Files<br />Other data repositories<br />Database...
Big “D” or little “d” Disasters?<br />Physical Infrastructure Failures<br />Logical Data Failures<br />Storage Subsystem<b...
Database Backup / Recovery<br />Traditional backup types<br />Full backup<br />Differential backup<br />Transaction log ba...
Protecting User Databases Isn’t Sufficient<br />TechRepublic: “If the master database fails, Microsoft SQL Server can be b...
It’s the Recovery, Stupid. <br />What’s The Process Like?<br />Backup file sets<br />Full baseline, differential, and tran...
Evolution of Continuous Availability<br />Business<br />Emphasis<br />Continuous Availability<br />No User or Application ...
Shift Focus to Availability<br />Minimize/Avoid service downtime – planned or unplanned.<br />On failure, service interrup...
Transactional Log Shipping<br />Warm standby solution<br />Duplicate user database<br />Copy transaction logs to standby s...
SQL Database Mirroring<br />Redundancy at user database level<br />Duplicate copy of user database<br />Mirrored over priv...
SQL Server Failover Clustering<br />Redundancy at database instance level<br />All databases fail over together<br />Share...
Considerations for HA/DR Deployments<br />HA complements backup and recovery strategy<br />Does not replace data recovery ...
Business Service<br />Business-Central Approach to Protection<br />Traditionally, servers of like functionality are groupe...
Neverfail High-Level Architecture<br />ApplicationModules<br />Monitoring<br />Continuity<br />NeverfailContinuousAvailabi...
Secondary<br />Primary<br />Apps<br />Apps<br />Neverfail Heartbeat<br />Neverfail Heartbeat<br />Neverfail Channel<br />L...
High Availability and Disaster Recovery Deployment with WANSmart™<br />Application Server<br />Application Server<br />App...
How WANSmart™ Works<br />NeverfailWANSmart™<br />ACTIVE SERVER<br />PASSIVE SERVER<br />DuplicatesFound<br />WAN<br />Rest...
Comparison: SQL versus Neverfail for SQL<br />1Basic monitoring only i.e. can the witness server connect to the database?<...
Neverfail Customers<br />RIM BlackBerry® Enterprise Server and Lotus Domino<br />“British American Tobacco’s mobile platfo...
Summary<br />Protects End-to-End Business Services<br />Neverfail aggregates & protects any set of multi-tier components, ...
Questions or Comments?<br />
High Availability Deployment<br />Flexible Deployment Scenarios<br />Application Server<br />Application Server<br />Never...
Disaster Recovery Deployment with WANSmart™<br />Flexible Deployment Scenarios<br />Application Server<br />Application Se...
ClusterProtector Deployment with WANSmart™<br />Application Server<br />Application Server<br />Application Server<br />WA...
Virtualization-Based Deployments (P2V, V2V or V2P)<br />WANSmart™<br />Neverfail Channel<br />Disaster Recovery Site<br />...
Continuous Availability Director<br />SharePoint Farm<br />Web Tier<br />Index Server<br />IIS<br />IIS<br />IIS<br />Quer...
SQL Server<br />SQL Server<br />Commerce<br />Biztalk<br />Custom<br />Blackberry Server<br />Domino Server<br />Exchange ...
Scope: user DB<br />Standard hardware<br />One SQL license (unless querying snapshots on mirror)<br />Very fast failover (...
Upcoming SlideShare
Loading in …5
×

Availability Considerations for SQL Server

1,948 views

Published on

Content from 1/27/11 Corporate Webinar on Availability Considerations for SQL Server.

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

  • Be the first to like this

No Downloads
Views
Total views
1,948
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • This PowerPoint Template includes a series of slide masters with predefined layouts and color schemes for formatting slides Slide Masters are displayed when you right click on a slide and select Layout from menu
  • We are a global software company with operations split into 3 key territories: Asia Pac, EMEA and the Americas.We have sales offices in Sydney-Australia, Frankfurt-Germany, Theale-UK, Austin-Texas-USA and Dubai Internet City-UAE.We have a Development centre in Stirling, Scotland and a support and QA centre in Cluj, Romania. The US is our biggest market representing some 65% of the business.We now have around 2000 customers worldwide.We are a Microsoft Gold Partner in the US and UK and the Neverfail product is Microsoft Certified.The company started as a Disaster Recovery consultancy over 10 years ago and with time developed tools and techniques that it decided to turn into a software product, hiring developers from the Tandem non-stop kernel team to help bring the vision to fruition.
  • Colt&apos;s Manufacturing Company (CMC, formerly Colt&apos;s Patent Firearms Manufacturing Company) is a United Statesfirearms manufacturer originally founded in 1836.One of the first truly modern-style handguns, the Colt revolvers became known as &quot;The Great Equalizer&quot;, because they could be loaded and fired by anyone, whereas most previous guns had required sufficient strength and dexterity. In theory, anyone who had a modern-style revolver was equal to anyone else, regardless of their relative physical abilities. This term has since come to be used for firearms in general, as awkward weapons like muzzle-loaded muskets became a thing of the past.
  • External Datastore Examples…Identity column seedsFull-text indexes(SQL Server 2000)LDAP entriesFile system objectsOther databases
  • Mirror WitnessWith mirroring, more than one server is required to decide on failoverWitness automates failover from primary to mirrorWatches database availabilityReports observations back to principal and mirrorRuns in separate SQL Server instance (Express is OK)Prevents “split brain” scenarioVery low resource consumptionCan be witness for multiple databasesNot a single point of failureWhat They DOSimple data replication (application data only – log shipping)Verify installation pre-requisitesData compression (SQL Server 2008 only)What They DON’T DOImplement easilyRequires a complete manual build of the secondary server, including all apps and patchesRequires a 3rd server (witness) for High Availability modeFailover seamlesslyEnd users will need to restart certain applications, unless they’re coded with ADO.NETMonitor the entire environmentAutomatic failover only supported in synchronous replication mode, Enterprise version onlyOnly protect at individual DB level (not all DBs on the server, nor SQL jobs, DTC, etc.)Application monitoring only checks for running services, so they won’t catch hung servicesNo network or performance monitoringNo protection for auxiliary applicationsReplicate registry changesOnly replicate data on disk, so application config changes won’t be copied acrossData rollbackComplete environment health checkMicrosoft employees (NY MTC) will recommend Neverfail in DR /large data scenarios
  • What They DOServer monitoring (heartbeat)Seamless high-availability failover and failbackWhat They DON’T DOImplement easilyRequires expensive SAN storage, which introduces a single point of failureMonitor the entire environmentApplication monitoring only checks if services are running, so they won’t realize if a service is hungNo network or performance monitoringNo protection for auxiliary applicationsProtect against disastersOnly by implementing another cluster and SAN replication technology can DR be achievedData rollback
  • Traditionally, servers of like functionality are grouped together for availability/protectionNeverfail takes a Business-Centric approach and manages and protects the completeBusiness application.
  • Neverfail’s Continuous Availability Suite ensures that end users remain connected to their business-critical applications, regardless of the type of outage.Neverfail achieves this by protecting the entire application ecosystem, to provide a complete HA and DR solution, that spans physical and virtual systems, across multiple sites.Neverfail’s application-aware management framework (AMF) continuously monitors the health, state and performance of individual applications and services, as well as Windows management instrumentation.In the event of a failure, Neverfail automatically detects the failure and attempts to heal the application, to ensure continuous availability and maximum uptime. If the application cannot be healed for whatever reason, the system can be configured to failover automatically (or manually) to ensure that users remain connected.
  • This slide shows that our logical architecture can be deployed to operate in various physical topologies. High Availability is our LAN Topology DUO configuration and we will walk you through its installation and operation shortly. Disaster Recovery is our WAN Topology which applies the same DUO configuration across a Wide Area Network. We can then extended the same powerful core capability of Neverfail to provide Disaster Recovery for Microsoft Active/Passive Clusters running Exchange or SQL. This is our ClusterProtector product which would merit a separate presentation to go into any level of detail. And finally we can now extend the same core architecture to combine the HA and DR capability into a Continuously Available linked TRIO of servers. Along with TRIO we have introduced a “WANSmart” capability that dramatically improves bandwidth utilization between local and remote sites, as well as reducing replication time. Depending on application type, WANSmart achieves up to 30x improved bandwidth utilization by using advanced data de-duplication algorithms prior to normal compression. Using WANSmart offers the potential to avoid costly WAN upgrades. Since our failover process is fully symmetrical, Neverfail’s Active/Passive architecture can be deployed in pretty much any Physical or Virtualised Primary and Secondary server configuration. And in any virtualized VMware environment, if the resilience of your virtual management tool is important, we even protect VMware’s VirtualCentre which is an acknowledged single point of failure. In fact VMware have licenced Neverfail’s technology which is embeded in their vCenter Heartbeat product. An equivalent level of protection for Microsoft’s VMM is in development.
  • Our value proposition is about keeping users permanently connected to their applications. Allowing access to what they need when they need it.Our Total Cost Of Ownership equation = No loss of productivity + meeting or exceeding SLA’s + preventing reputational damage. Service interruptions cause a loss of productivity; the cost of one minute of downtime multiplied by the number of business users in an organization can be surprisingly costly. As can the financial penalties associated with not meeting Service Level Agreements. And service interruptions can also lead to a loss of confidence in the IT function and damage the credibility of the CIO with the business. Reputational damage is hard to put a price on.Our technology will enable reputations to be protected and SLA’s to be maintained or even exceeded by maintaining service continuity through interruptions and application maintenance windows that normally require downtimeIn summary Neverfail enables Enterprise Data Centre levels of high availability and disaster recovery based on cost effective “Wintel” commodity technology.
  • This slide shows that our logical architecture can be deployed to operate in various physical topologies. High Availability is our LAN Topology DUO configuration and we will walk you through its installation and operation shortly. Disaster Recovery is our WAN Topology which applies the same DUO configuration across a Wide Area Network. We can then extended the same powerful core capability of Neverfail to provide Disaster Recovery for Microsoft Active/Passive Clusters running Exchange or SQL. This is our ClusterProtector product which would merit a separate presentation to go into any level of detail. And finally we can now extend the same core architecture to combine the HA and DR capability into a Continuously Available linked TRIO of servers. Along with TRIO we have introduced a “WANSmart” capability that dramatically improves bandwidth utilization between local and remote sites, as well as reducing replication time. Depending on application type, WANSmart achieves up to 30x improved bandwidth utilization by using advanced data de-duplication algorithms prior to normal compression. Using WANSmart offers the potential to avoid costly WAN upgrades. Since our failover process is fully symmetrical, Neverfail’s Active/Passive architecture can be deployed in pretty much any Physical or Virtualised Primary and Secondary server configuration. And in any virtualized VMware environment, if the resilience of your virtual management tool is important, we even protect VMware’s VirtualCentre which is an acknowledged single point of failure. In fact VMware have licenced Neverfail’s technology which is embeded in their vCenter Heartbeat product. An equivalent level of protection for Microsoft’s VMM is in development.
  • This slide shows that our logical architecture can be deployed to operate in various physical topologies. High Availability is our LAN Topology DUO configuration and we will walk you through its installation and operation shortly. Disaster Recovery is our WAN Topology which applies the same DUO configuration across a Wide Area Network. We can then extended the same powerful core capability of Neverfail to provide Disaster Recovery for Microsoft Active/Passive Clusters running Exchange or SQL. This is our ClusterProtector product which would merit a separate presentation to go into any level of detail. And finally we can now extend the same core architecture to combine the HA and DR capability into a Continuously Available linked TRIO of servers. Along with TRIO we have introduced a “WANSmart” capability that dramatically improves bandwidth utilization between local and remote sites, as well as reducing replication time. Depending on application type, WANSmart achieves up to 30x improved bandwidth utilization by using advanced data de-duplication algorithms prior to normal compression. Using WANSmart offers the potential to avoid costly WAN upgrades. Since our failover process is fully symmetrical, Neverfail’s Active/Passive architecture can be deployed in pretty much any Physical or Virtualised Primary and Secondary server configuration. And in any virtualized VMware environment, if the resilience of your virtual management tool is important, we even protect VMware’s VirtualCentre which is an acknowledged single point of failure. In fact VMware have licenced Neverfail’s technology which is embeded in their vCenter Heartbeat product. An equivalent level of protection for Microsoft’s VMM is in development.
  • This slide shows that our logical architecture can be deployed to operate in various physical topologies. High Availability is our LAN Topology DUO configuration and we will walk you through its installation and operation shortly. Disaster Recovery is our WAN Topology which applies the same DUO configuration across a Wide Area Network. We can then extended the same powerful core capability of Neverfail to provide Disaster Recovery for Microsoft Active/Passive Clusters running Exchange or SQL. This is our ClusterProtector product which would merit a separate presentation to go into any level of detail. And finally we can now extend the same core architecture to combine the HA and DR capability into a Continuously Available linked TRIO of servers. Along with TRIO we have introduced a “WANSmart” capability that dramatically improves bandwidth utilization between local and remote sites, as well as reducing replication time. Depending on application type, WANSmart achieves up to 30x improved bandwidth utilization by using advanced data de-duplication algorithms prior to normal compression. Using WANSmart offers the potential to avoid costly WAN upgrades. Since our failover process is fully symmetrical, Neverfail’s Active/Passive architecture can be deployed in pretty much any Physical or Virtualised Primary and Secondary server configuration. And in any virtualized VMware environment, if the resilience of your virtual management tool is important, we even protect VMware’s VirtualCentre which is an acknowledged single point of failure. In fact VMware have licenced Neverfail’s technology which is embeded in their vCenter Heartbeat product. An equivalent level of protection for Microsoft’s VMM is in development.
  • This slide shows that our logical architecture can be deployed to operate in various physical topologies. High Availability is our LAN Topology DUO configuration and we will walk you through its installation and operation shortly. Disaster Recovery is our WAN Topology which applies the same DUO configuration across a Wide Area Network. We can then extended the same powerful core capability of Neverfail to provide Disaster Recovery for Microsoft Active/Passive Clusters running Exchange or SQL. This is our ClusterProtector product which would merit a separate presentation to go into any level of detail. And finally we can now extend the same core architecture to combine the HA and DR capability into a Continuously Available linked TRIO of servers. Along with TRIO we have introduced a “WANSmart” capability that dramatically improves bandwidth utilization between local and remote sites, as well as reducing replication time. Depending on application type, WANSmart achieves up to 30x improved bandwidth utilization by using advanced data de-duplication algorithms prior to normal compression. Using WANSmart offers the potential to avoid costly WAN upgrades. Since our failover process is fully symmetrical, Neverfail’s Active/Passive architecture can be deployed in pretty much any Physical or Virtualised Primary and Secondary server configuration. And in any virtualized VMware environment, if the resilience of your virtual management tool is important, we even protect VMware’s VirtualCentre which is an acknowledged single point of failure. In fact VMware have licenced Neverfail’s technology which is embeded in their vCenter Heartbeat product. An equivalent level of protection for Microsoft’s VMM is in development.
  • Availability Considerations for SQL Server

    1. 1. Availability Considerations for SQL Server Deployments<br />Bob Roudebush, Neverfail<br />1/27/2010<br />
    2. 2. Neverfail Company Overview<br />Our Focus<br />Delivering world-class Continuous Availability software for High Availability and Disaster Recovery<br />Ensuring Business Continuity and IT Services Continuity by reducing both planned and unplanned downtime<br />Leveraging Application Awareness, Intelligence and Automation to deliver the highest levels of uptime<br />Company Background<br />3,000+ customers in over 40 countries<br />SMB to Global Enterprises across all major industry verticals<br />Worldwide Reach<br />North America, EMEA and Asia-Pacific<br />Strategic Relationships with Microsoft, VMware, Cisco, RIM, SolarWinds and others<br />
    3. 3. Is There A Better Option for Protecting SQL?<br />Need for Disaster Recovery Strategies is Undeniable.<br />61% of North American enterprises and 64% of European enterprises say that upgrading DR capabilities is either a critical or high priority for the next 12 months.1<br />Many Only Protect Mission-Critical Applications – Why?<br />The cost and complexity of the supporting infrastructure required at the recovery data center.<br />1 Forrester’s Enterprise and SMB Hardware Survey, NA and Europe, Q3 2009<br />2 Source: Mid-market Business Continuity Survey (N=230)<br />
    4. 4. Degrees of protection for information systems:<br />So you need to make your SQL Server deployment bulletproof?<br />Data Availability Continuum<br />4<br />
    5. 5. Business Case for SQL Availability<br />High Availability<br />Disaster Recovery<br />Keep business-critical applications available<br />Secondary:<br />Server maintenance<br />Protect against loss of data center<br />Secondary:<br />Application upgrades<br />Infrastructure upgrades<br />5<br />
    6. 6. What Should You Protect?<br />Application Data Stores<br />Databases<br />Files<br />Other data repositories<br />Database Services<br />DBMS availability for applications<br />Application Services<br />Application availability for users and external systems<br />Databases are the heart of most information systems;they deserve the highest affordable protection.<br />
    7. 7. Big “D” or little “d” Disasters?<br />Physical Infrastructure Failures<br />Logical Data Failures<br />Storage Subsystem<br />Disk<br />Controller<br />Network<br />Server<br />Power<br />Site-wide Outages<br />Operator Errors<br />DBMS interruption<br />Drops / Deletes<br />Application Defects<br />DBMS Defects<br />Data Corruption<br />
    8. 8. Database Backup / Recovery<br />Traditional backup types<br />Full backup<br />Differential backup<br />Transaction log backup<br />Disk is better than tape<br />First backup to disk (separate physical disk volume)<br />Detect exceptions encountered during backup<br />Verify backup files<br />Copy backup files to tape or remote disk<br />Backup everything!<br />External data stores<br />System databases<br />
    9. 9. Protecting User Databases Isn’t Sufficient<br />TechRepublic: “If the master database fails, Microsoft SQL Server can be brought to its knees.”1<br />SQL Server does not protect system databases<br />master, model, temp, msdb<br />Master db is most critical<br />Instance-wide meta data, system configuration, location of database files, initialization info for SQL server<br />SQL Server can not start if master is unavailable<br />master, model, temp, msdb<br />1 http://articles.techrepublic.com.com/5100-10878_11-5025441.html<br />
    10. 10. It’s the Recovery, Stupid. <br />What’s The Process Like?<br />Backup file sets<br />Full baseline, differential, and transaction logs<br />Retrieving backup files<br />Offsite storage<br />Tape<br />Network copy<br />Dependency on multiple people to get access to backup files<br />Does It Meet Your SLAs?<br />Recovery strategy depends on failure scenario<br />Create comprehensive failure matrix<br />Devise recovery strategy for each scenario<br />Does worst-case recovery scenario fit within SLA parameters?<br />Recovery Time / Recovery Point<br />Include future data growth in recovery plan<br />
    11. 11. Evolution of Continuous Availability<br />Business<br />Emphasis<br />Continuous Availability<br />No User or Application Downtime, Application-<br />Awareness, Automation, Local & Remote Availability<br />Availability<br />Centric<br />Application<br />Emphasis<br />Basic Failover<br />Clustering, Fault Tolerance, High Availability<br />Data Replication<br />Snapshot, Asynchronous, Synchronous, CDP<br />Data<br />Emphasis<br />Recovery<br />Centric<br />Backup & Restore<br />File, Block, Full, Incremental, On-site, Off-site<br />
    12. 12. Shift Focus to Availability<br />Minimize/Avoid service downtime – planned or unplanned.<br />On failure, service interruption is brief or non-existent<br />Automatic failover<br />Eliminate single points of failure (as affordable)<br />Redundant components<br />Fault-tolerant servers<br />
    13. 13. Transactional Log Shipping<br />Warm standby solution<br />Duplicate user database<br />Copy transaction logs to standby server & restore<br />Database available for read-only access<br />Users must disconnect for logs to be applied<br />Two database licenses required if querying standby<br />Manual application failover<br />Supported on standard hardware<br />Possible data loss (unapplied transactions)<br />
    14. 14. SQL Database Mirroring<br />Redundancy at user database level<br />Duplicate copy of user database<br />Mirrored over private network channel<br />Mirror replays transactions from principal<br />Multiple mirroring modes:<br />High-safety: commit @ log on mirror; automatic failover<br />High-safety: commit @ log on mirror; manual failover<br />High-performance: commit when logged on principal<br />Requires witness server<br />Mirror-aware application client connection<br />Provided by client library<br />Database connection string must specify both servers<br />
    15. 15. SQL Server Failover Clustering<br />Redundancy at database instance level<br />All databases fail over together<br />Shared copy of system databases<br />Single data copy on shared storage device<br />No I/O overhead reducing throughput<br />Storage unit is single point of failure for cluster<br />All database services are clustered<br />SQL Agent; Analysis Services; Full-Text engine, MS DTC<br />Automatic failover (up to minutes)<br />DBMS accessed over virtual IP<br />Requires hardware certified by Microsoft for Microsoft Cluster Service<br />
    16. 16. Considerations for HA/DR Deployments<br />HA complements backup and recovery strategy<br />Does not replace data recovery plan<br />Application service availability is often determined by a network of interdependent services<br />Availability can be difficult to define (e.g. partial failures)<br />Failure probability difficult to measure or compute<br />Additional Infrastructure Costs (Storage/WAN/Hardware)<br />Increased system complexity could lead to lower service availability!<br />Operator error a leading cause of availability issues<br />Increased number/types of system components<br />More complex to configure and administer<br />
    17. 17. Business Service<br />Business-Central Approach to Protection<br />Traditionally, servers of like functionality are grouped together for availability and protection, leading to multiple, standalone availability solutions and incomplete protection for the Business Service<br />Neverfail’s unique Business-Centric approach manages and protects the completeBusiness Service, including: <br />Load Balancing<br />Web Server<br />Web Server<br />?????<br />Complete Protection for Business Service<br />Application Server<br />Application Server<br />MS Clustering<br />Database Mirroring<br />Database Server<br />Database Server<br />
    18. 18. Neverfail High-Level Architecture<br />ApplicationModules<br />Monitoring<br />Continuity<br />NeverfailContinuousAvailabilityDirector<br />Application AwareManagement Framework (AMF)<br />Scope<br />Data<br />WANSmart<br />3rd PartyAdaptors<br />Manage availabilityfrom a single point across a wide variety of heterogeneous environments.<br />CLOUD<br />
    19. 19. Secondary<br />Primary<br />Apps<br />Apps<br />Neverfail Heartbeat<br />Neverfail Heartbeat<br />Neverfail Channel<br />LAN or WAN<br />Resync: Once the cause of the failure has been addressed, Neverfail will resynchronize the primary without any additional downtime.<br />How Failover and Failback Work<br />Step #1: Install 2nd server with 2nd network interface card. This will be known as the “Neverfail Channel” used for Neverfail traffic only.<br />Step #2: Run S.C.O.P.E. (Server Check Optimization & Performance Evaluation) Tool to check required components are available.<br />Step #3: Run Neverfail setup to clone the Windows OS, applications and data to the secondary server.<br />Step #4: Neverfail will begin replicating changes to both protected data and the application configuration in real-time.<br />Failover: Neverfail will detect failure of the application and can automatically failover the application to the secondary server.<br />Switchback: Once the data has been completely resynchronized, Neverfail will perform a switchback, returning the application to the operating state it was in prior to the failure.<br />
    20. 20. High Availability and Disaster Recovery Deployment with WANSmart™<br />Application Server<br />Application Server<br />Application Server<br />WANSmart™<br />Neverfail Channel<br />Neverfail Channel<br />Flexible Deployment Scenarios<br />Production Site<br />Disaster Recovery Site<br />Flexible, P2P, P2V , V2P or V2V operation<br />Local and remote deployment<br />Shared nothing architecture<br />Specific Microsoft Cluster, Hyper-V and vSphere Options <br />LAN<br />LAN<br />
    21. 21. How WANSmart™ Works<br />NeverfailWANSmart™<br />ACTIVE SERVER<br />PASSIVE SERVER<br />DuplicatesFound<br />WAN<br />RestoreDuplicates<br />Data ChangesIntercepted<br />Compression& De-duplication<br />TransmissionAcross WAN<br />Decompression& Re-constitution<br />Data ChangesApplied<br />Bandwidth optimization built-in Lower cost and latency reduction<br />Advanced de-duplication Up to 30x improvement<br />
    22. 22. Comparison: SQL versus Neverfail for SQL<br />1Basic monitoring only i.e. can the witness server connect to the database?<br />2Requires synchronous mirroring and an additional witness server<br />
    23. 23. Neverfail Customers<br />RIM BlackBerry® Enterprise Server and Lotus Domino<br />“British American Tobacco’s mobile platforms have come to lie at the heart of our business use of technology. The simple fact is that Neverfail keeps that heart beating.” <br />David Sampson, Head of Headquarters IT - British American Tobacco<br />RIM BlackBerry® Enterprise Server and Microsoft® SQL Server<br />“I have complete confidence that we now have a highly reliable solution in place which will keep our staff connected through any outage.”<br />Darren Unwin IS Services Manager DB Schenker Rail (UK) Ltd<br />Microsoft® Exchange and Microsoft® SQL Server<br />“The Neverfail solution supports our rigorous requirements for business continuity while respecting our technical and budgetary goals.”<br />PärPersson IT Manager, Stena Rederi AB Stena Bulk<br />Microsoft® SharePoint Server<br />“I am 100 percent confident that our entire legal team has continuous access to their business-critical documents anytime, anywhere.”<br />Andy Jurczyk CIO Sonnenschein Nath & Rosenthal LLP<br />RIM BlackBerry® Enterprise Server<br />“Neverfail is unique. Its nearest competitor only delivers 50 percent of the functionality.”<br />Timo Sillober Head of Office IT Vodafone Group Services GmbH<br />
    24. 24. Summary<br />Protects End-to-End Business Services<br />Neverfail aggregates & protects any set of multi-tier components, including applications, servers, services, and it maps all their interdependencies<br />Complete Protection Against the Widest Range of Failures<br />Leverages Application Awareness, Intelligence and Automation<br />Eliminates both planned and unplanned downtime<br />WAN Acceleration & Deduplication<br />Essential feature set to enable DR deployments<br />Heterogeneous Protection<br />Physical and Virtual Environments (P2P, P2V, V2P, V2V)<br />Any Combination of Physical Server and Storage Hardware<br />
    25. 25. Questions or Comments?<br />
    26. 26. High Availability Deployment<br />Flexible Deployment Scenarios<br />Application Server<br />Application Server<br />Neverfail Channel<br />Production Site<br />Flexible, P2P, P2V , V2P or V2V operation<br />Local and remote deployment<br />Shared nothing architecture<br />Specific Microsoft Cluster, Hyper-V and vSphere Options <br />LAN<br />
    27. 27. Disaster Recovery Deployment with WANSmart™<br />Flexible Deployment Scenarios<br />Application Server<br />Application Server<br />WANSmart™<br />Neverfail Channel<br />Neverfail Channel<br />Production Site<br />Disaster Recovery Site<br />Flexible, P2P, P2V , V2P or V2V operation<br />Local and remote deployment<br />Shared nothing architecture<br />Specific Microsoft Cluster, Hyper-V and vSphere Options <br />LAN<br />LAN<br />
    28. 28. ClusterProtector Deployment with WANSmart™<br />Application Server<br />Application Server<br />Application Server<br />WANSmart™<br />Neverfail Channel<br />Disaster Recovery Site<br />Production Site<br />Flexible, P2P, P2V , V2P or V2V operation<br />Local and remote deployment<br />Shared nothing architecture<br />Specific Microsoft Cluster, Hyper-V and vSphere Options <br />LAN<br />LAN<br />SAN<br />Cluster Storage<br />Flexible Deployment Scenarios<br />
    29. 29. Virtualization-Based Deployments (P2V, V2V or V2P)<br />WANSmart™<br />Neverfail Channel<br />Disaster Recovery Site<br />Flexible, P2P, P2V , V2P or V2V operation<br />Local and remote deployment<br />Shared nothing architecture<br />Specific Microsoft Cluster, Hyper-V and vSphere Options <br />LAN<br />Flexible Deployment Scenarios<br />Application Server<br />Application Server<br />Application Server<br />Neverfail Channel<br />Production Site<br />LAN<br />
    30. 30. Continuous Availability Director<br />SharePoint Farm<br />Web Tier<br />Index Server<br />IIS<br />IIS<br />IIS<br />Query Server<br />Exec Calc Server<br />Central Admin<br />ApplicationModules<br />Virtualized<br />Application Tier<br />NeverfailContinuousAvailabilityDirector<br />AMF<br />Scope<br />3rd PartyAdaptors<br />Database Tier<br />Physical<br />SQL Server<br />SQL Server<br />
    31. 31. SQL Server<br />SQL Server<br />Commerce<br />Biztalk<br />Custom<br />Blackberry Server<br />Domino Server<br />Exchange Server<br />Symantec A/V<br />IIS+MOSS<br />IIS+MOSS<br />IIS+MOSS<br />IIS+MOSS<br />Index Server<br />IIS+MOSS<br />IIS+MOSS<br />IIS+MOSS<br />IIS+MOSS<br />File Server<br />Query Server<br />Exec Calc Server<br />Central Admin<br />ApplicationModules<br />SharePoint Farm<br />Messaging Systems<br />Web Applications<br />Monitoring<br />Continuity<br />Web Front End<br />Web Front End<br />Web Front End<br />NeverfailContinuousAvailabilityDirector<br />AMF<br />Scope<br />Outlook Web Access<br />Virtualized<br />SQL Server<br />SQL Server<br />SQL Server<br />SQL Server<br />SQL Server<br />Application Tier<br />Application Tier<br />Application Tier<br />Data<br />WANSmart<br />3rd PartyAdaptors<br />Virtualized<br />Physical<br />CLOUD<br />Database Tier<br />Database Tier<br />Database Tier<br />Physical<br />Continuous Availability Director<br />
    32. 32. Scope: user DB<br />Standard hardware<br />One SQL license (unless querying snapshots on mirror)<br />Very fast failover (seconds)<br />OS flexible (e.g. 32/64)<br />Independent storage<br />Independent services<br />Reporting on mirror<br />Geographic separation OK<br />SQL Server Options for HA Comparison<br />Database Mirroring<br />Failover Clustering<br />Scope: DBMS Instance<br />Certified hardware<br />One SQL license (unless querying snapshots on mirror)<br />Automatic Failover (minutes)<br />Enterprise OS<br />Shared storage<br />Clustered services<br />Standby not available<br />Servers usually co-located<br />32<br />

    ×