Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

5 Ways to Avoid Server and Application Downtime

6,163 views

Published on

Successfully maintaining server and application uptime requires a diligent watch. This presentation outlines five ways you can avoid server and application downtime to ensure your users are always connected to the programs vital to their success.

Published in: Technology
  • Be the first to comment

5 Ways to Avoid Server and Application Downtime

  1. 1. Webinar- 5 Ways to Avoid Server and Application Downtime Successfully maintaining server uptime requires a diligent watch. Join us for this informative talk to learn about what things you need to be watching for when assuring that your applications are always available. – Application Availability can be affected by: – Hardware & power failures – Operating system performance – Application configuration and stability – Network congestion and isolation – Data availability, corruption, and access1
  2. 2. 5 Ways to Avoid Server and Application Downtime Josh Mazgelis / Sr. Product Marketing Manager February 16th, 2012© 2012 Neverfail
  3. 3. Providing the Proper Focus User/Customer Applications DATA Network Hardware/OS3
  4. 4. Today’s Agenda 1. Power, cooling, and network services 2. Computing hardware, physical and virtual 3. Data availability, corruption, and access 4. Operating system issues and performance 5. Application stability and configuration – How Neverfail and Neverfail SRMXtender help to minimize application downtime and keep users connected to data – Questions and Answers4
  5. 5. 1) How do we Protect Power & Cooling? – Range of power solutions from small to enormous – Compact UPS for small number of components – Large UPS for small datacenters – Back-up generators for many loads and durations – Range of cooling options for varying loads – Ambient air-conditioned office for a couple of servers – Window/cabinet units may be portable – Dedicated units or dedicated building zones5
  6. 6. How do we protect Networks? – Networks have become a “basic service” – Sometimes taken for granted – Can contain redundant hardware – Can contain redundant network routes – More complex than traditional basic services – More than just “power is on” or “power is off” – Servers, users, storage… all network connected – Connections between servers in complex applications – Connection between users and application interface – Connection to resources like DC’s, GW’s, authentication…6
  7. 7. 2) How to we Maintain Hardware Availability? – Hardware, physical or virtual, is the Core of IT infrastructure – One of the most critical layers, and also the least likely to fail – Redundant server components for physical hosts – Dual power supplies, redundant CPU/memory/backplane – Failed components still need to be replaced – Expensive, single-host point solution – Server virtualization helps with hardware availability – Reduces immediate impact of hardware failures – VM’s can be quickly restored to a different host – vMotion & HA/FT minimize hardware downtime7
  8. 8. What About a Rock-Solid Hardware Environment? – Vulnerabilities to end-user availability still exist – Site failures / building maintenance – Operating system failures – Application failures – Planned downtime – Preserving a machine state does not guarantee uptime – If a VM image has a problem (OS/App/Maint) in one location, the VM image will have the same problem in any location – Troubleshooting the problem affects overall recovery time – Reverting to backups affects the recovery point8
  9. 9. How do we protect from Site Failures? – Put a second copy of everything somewhere else – Recovery point objectives dictate technology selection – Daily backups, hourly snapshots, or real-time change replication – Tools like VMware’s Site Recovery Manager (SRM) for virtual machines – Provides “good enough” protection for many applications (tier-2, tier-3) – Requires some kind of data-mover to maintain 2nd site – Application-based replication – Log shipping & DAG – Storage-based replication – SAN/volume/vSphere – Host-based replication – 3rd-party applications like Neverfail & others9
  10. 10. 3) Data Availability, Corruption, and Access – A company’s data is its second most valuable asset – It’s people, of course, are the most valuable asset – Companies who loose access to their data often go out of business – Protecting data is paramount to a company’s survival – Solutions offer varying recovery times and recovery points – How much time can you stand to be without data? – How much data can you stand to be without? – The more critical the data, the more important the RPO – Changes need to be tracked and preserved immediately – Also need ability to recover from “bad data events” (rollback)10
  11. 11. In what ways can we Protect Data? – Traditional tape or disk-based backups – Great for archival and compliance – Typically lower RPO/RTO – Snapshots, block level differentials (BLD) – Preserves system/data state at more frequent intervals – Better RPO/RTO than tape backups, more for recoverability – Built-in application-specific data movers – Log shipping, database mirroring, availability groups – Specific to database layer only, varying demands on architecture – Host-based replication software – Real-time change tracking at file-system for very low RPO – Works with any data type stored on disk volumes11
  12. 12. 4) What about the Operating System itself? – Just one (important) part of availability stack – Dependent on the hardware infrastructure – Supportive of the application – Susceptible to downtime from many angles – System halts and blue-screen faults – Patch management and conflict issues – Planned reboots and other maintenance – Clustering solutions begin to address this issue – Two similar computers, each with its own install of the OS – Either computer can be “active” when the other is down12
  13. 13. 5) Can the Application become the Issue? – Even at the top of the application stack problems can occur – Conflict with security update prevents services from starting – Missing or corrupted application files or content – Application performance degradation – Monitoring of the application is often overlooked – Traditional tools determine only if “hardware” is running – Application faults can exist even when the infrastructure is good – The end-user experience sees the entire availability stack – Issues at any of the layers affects application availability13
  14. 14. Neverfail & Neverfail SRMXtender
  15. 15. What is Neverfail? – Neverfail is a software-based HA/DR solution – Combines real-time replication with application management – Provides near-zero recovery points and low recovery times – Application-specific monitoring of KPI and environment – Supports both physical and virtual servers equally15
  16. 16. What is Neverfail SRMXtender? – Integration of Neverfail console into vSphere Client – No need to open a second console to manage availability – Supports vCenter versions 4.x and 5.x – Management of virtual and physical servers together – Single solution for applications spanning physical and virtual servers – Creates SRM plan steps for Neverfail-protect pairs – Support for true tier-1 RTO & RPO on virtual servers – Real-time change tracking for near-zero recovery point – Stand-by servers for true managed failover and low recovery time16
  17. 17. Can I Combine Solutions to Maximize Benefits? – Hypervisor provides local hardware availability – Neverfail provides: – Real-time data replication with zero data loss – Application-aware protection and recovery orchestration – Support for physical servers and different hypervisors within SRM WANSmart™ SAN Hypervisor Hypervisor Hypervisor17
  18. 18. SRM Recovery Plans can now include physical servers Corporate Messaging System Web Front End VMware Site Recovery Exchange Exchange Exchange Virtual Manager CAS CAS OWA Application Tier Inject recovery step for physical servers Exchange BES Anti-virus Anti-spam Hub Server Server Server Database / Storage Tier Physical SRMXtender MBX Server SQL Server File Server18
  19. 19. SRM coordinates physical server failover sequence SharePoint Farm SharePoint Farm Web Tier Web Tier Virtualized IIS+MOSS IIS+MOSS IIS+MOSS IIS+MOSS IIS+MOSS IIS+MOSS Array Replication or Application Tier Application Tier vSphere Replication Virtualized Query Index Excel Calc Central Query Index Excel Calc Central Server Server Services Admin Server Server Services Admin Database Tier Neverfail Replication Database Tier Physical & Failover/Failback SQL Server SQL Server SQL Server SQL Server Primary Site Secondary Site Co-ordination VMware Site Recovery Manager19
  20. 20. What are some Key Technology Differentiators? – Protects End-to-End Business Services – Neverfail aggregates & protects any set of multi-tier components, including applications, servers, services, and it maps all their interdependencies – Complete Protection Against the Widest Range of Failures – Leverages Application Awareness, Intelligence and Automation – Eliminates both planned and unplanned downtime – WAN Acceleration & Deduplication – Essential feature set to enable DR deployments – Heterogeneous Protection – Physical and Virtual Environments (P2P, P2V, V2P, V2V) – Any Combination of Physical Server and Storage Hardware20
  21. 21. Visit us Online to Learn More – See SRMXtender & the Virtual Availability Director – Video, datasheets, and download registration – http://srmx.neverfailgroup.com21
  22. 22. Thank you! Call or Visit for a personalized demonstration http://www.neverfailgroup.com US (512) 327-5777 UK (0) 870 777-1500© 2012 Neverfail

×