Parallels Virtualization Containers High Availability & Disaster Recovery Jamison Moore Sponsored by || Parallels Summit 2009 | Las Vegas | Mandalay Bay

Parallels – Optimized Computing TM 2 Agenda Parallels Virtuozzo Containers Overview Understanding & Planning for Disasters Introduce Parallels Virtuozzo Containers HA/DR Options Assumptions & Scope Generally familiar with clustering and relating terminology Detailed cluster and backup configuration is outside the scope Full Virtuozzo clustering & backup documentation is available

CONTAINERS OVERVIEW Parallels Virtuozzo Containers – HA/DR

Parallels – Optimized Computing TM 4 Parallels Virtualization Technologies Guest OS VM 1VM 2VM 3 Virtual Hardware Virtual Machine Monitor Hypervisor or Standard Host OS Hardware Hypervisor Virtualizes access to hardware Mix and Match Operating Systems Minimal / Moderate Overhead Parallels Server, Workstation, Desktop Virtualizes access to OS Single OS per server (Windows/Linux) Minimal Performance Overhead Parallels Virtuozzo Containers Container 1 Container 2 Container 3 Standard Host OS Hardware OS Virtualization Layer OS Virtualization (Containers) OS Virtualization (Containers) Hardware Virtualization (Hypervisors) Hardware Virtualization (Hypervisors)

Parallels – Optimized Computing TM 5 Parallels Virtuozzo Containers Comprehensive Management Global, Multi-server management Granular roles based permissions Powerful and Extensible Dynamic HTML, AJAX SOAP, XML, RPC, CLI, SNMP, AD & LDAP

Parallels – Optimized Computing TM 6 High Density Partitioning 100s+ of containers on a single server Complete Container Isolation Processes, sessions, users, files, registry/proc, pipes, NIC, IP addresses, ports, routing tables… Dynamic Resource Management CPU, memory, disk, I/O, & system resources Mass Patch & Application Management Streamlined OS updates, and deployments of containers and applications Parallels Virtuozzo Containers

DISASTERS Parallels Virtuozzo Containers – HA/DR

Parallels – Optimized Computing TM 8 Disasters Come in Many Forms Human Error Power Failure Hardware/Software Failure Network Failure Hackers/Worms/Viruses Burglary/Vandalism Terrorism/Sabotage Explosion Flooding Fire Lightening Earthquake Tornado Hurricane Disaster : any sudden, unplanned event that disrupts critical business functions.

Parallels – Optimized Computing TM 9 The Cost of a Disaster Average cost of downtime PER HOUR: –Retail brokerage - $6.45 mil –Credit card sales authorization - $2.60 mil –Airline reservation centers - $89,500 –Computer Networks - $42,000 43% of firms that suffer massive data loss will never re-open Disaster Recovery Journal *Gartner **Pepperdine University Report ** * 80% of failures are due to human error Gartner Average cost of data loss PER INCIDENT: –Technical services cost, lost productivity/data - ~ $4000

Parallels – Optimized Computing TM 10 Planning for Disasters Nobody plans to fail, they simply fail to plan Assess and Prioritize Requirements What is the uptime requirement for your critical workloads? What workloads or services need to back up and running first? Create a Disaster Plan Minimize service disruption Ensure an orderly recovery process Maintain Service Level Agreements

CLUSTERING Parallels Virtuozzo Containers HA/DR

Parallels – Optimized Computing TM 12 What is Parallels Virtuozzo Clustering? Servers working together to increase availability Cluster Achieve Higher Availability Automatic restart of failed Containers Automatic relocation of containers in the event of a hardware failure Minimize Scheduled Downtime System maintenance Rolling upgrades (OS & applications) Basic Requirements: FC/iSCSI connected SAN Microsoft Windows Server MSCS RedHat Enterprise Linux / CentOS 5 + RHCS

Parallels – Optimized Computing TM 13 Supported Clustering Modes Physical to Container BOOM A dedicated standby node is not required for either clustering mode Less hardware & maintenance = Substantial upfront & annual cost savings! Eliminate standby hardware for just 100 nodes and save ~$200K+ annually Physical to Physical Cluster BOOM

Parallels – Optimized Computing TM 14 Dedicated Standby Node 14 While Parallels Virtuozzo Containers Supports clustering without it, a dedicated standby node is optional. More Hardware & Maintenance = Additional Upfront & Annual Costs Cluster Benefits Assuming like hardware, similar performance after fail-over Drawbacks Increased solution cost Requires regular maintenance

Parallels – Optimized Computing TM 15 Virtuozzo Clustering Best Practices Leverage fencing devices when possible Allow heartbeat over private and public NICs Virtuozzo Containers up to date with latest patches Patch level parity among nodes is recommended The Standby node is of equal or better performance Use separate disk resources for logs & Container data Use dedicated NIC for heartbeat, public & iSCSI networks Members should have matching server architecture –Required for Microsoft Windows, optional for Linux When using Active/Active, ensure capacity on fail-over node

BACKUP & REPLICATION Parallels Virtuozzo Containers HA/DR

Parallels – Optimized Computing TM 17 Container Backup 17 Included Free with Virtuozzo Online, snapshot based backup VSS aware (AD, Exchange, MSSQL, Oracle…) Define compression type, files to backup, start time, backup location (local, network share, Virtuozzo node) Build-in backup scheduler Minimal container backup size

Parallels – Optimized Computing TM 18 Supported / Tested 3 rd Party Backup Options Symantec Backup Exec Container and host backup IBM Tivoli Storage Manager EMC (Legato) Networker BrightStor ARCServer Windows NTBackup Backup Best Practices Leverage Volume Shadow Copy service when supported It is recommended to keep backup archives offsite Host & Container Backup

Parallels – Optimized Computing TM 19 Data Replication I’m creating regular backups, do I need replication? –Backups are typically hourly/daily –Can you afford to lose data for the last day or even the last hour? –How much would it cost to manually reproduce the lost data? SAN Based Replication –DataCore SANsymphony / SANmelody Software Based Replication –DoubleTake –PeerSync 19

Parallels – Optimized Computing TM 20 Summary Downtime, planned or not = Lost $$$ Carefully determine your HA & DR requirements Use a combined approach when possible You probably already own clustering software, use it Parallels Virtuozzo Containers includes cluster support

Parallels – Optimized Computing TM 21 Questions?

Thank You! Jamison Moore Fully functional trials of Parallels Virtuozzo Containers available at:

APPENDIX Parallels Virtuozzo Containers HA/DR

Parallels – Optimized Computing TM 24 Parallels Products Overview Virtualization Parallels Desktop Parallels Workstation Parallels ServerParallels Virtuozzo Containers The best of both worlds with Hypervisor and OS Virtualization Automation Complete automation & management of IT systems and processes Parallels System Automation Parallels Business Automation Parallels Infrastructure Manager Parallels Plesk Products

Parallels – Optimized Computing TM 25 Clustering does not protect against: –Loss of, or damage to shared storage –Data(base) corruption –Network or Site-level disasters –All application failures –Human configuration errors Clustering does not support: –Moving running applications –Maintain session(s) state What Does Clustering Not Provide?

Parallels – Optimized Computing TM 26 Networking - Bridged Mode 26 UsageAdvantages  MAC-dependent applications  Cross-Container traffic using external router  DHCP based IP assignment  Support of all dedicated server network features  Raw packet support  Support of MAC-address dependent applications (like load-balancers)  DHCP client and server support

Parallels – Optimized Computing TM 27 Network Load Balancing (NLB) This cluster configuration can be used to distribute client requests among cluster nodes according to the current network load, thus, greatly increasing your application and service availability and performance. 27 Minimal Requirements 2 active nodes / containers Benefits Load Distribution: If a container fails, the load is automatically redistributed among the remaining active Containers. Capacity on Demand: As the traffic increases or as your applications require more server power, you can dynamically add capacity by adding additional containers/nodes. Limitations Server load is not factored in, only network traffic is considered.

Parallels – Optimized Computing TM 28 Related Sessions Parallels Virtualization Roadmap Update (online) Tuesday 3:55 / Technology Track Parallels Technology Roadmap Wednesday 11:35 / General Session Parallels Virtualization Containers Best Practices: High Availability/Clustering Wednesday 1:00 / Enterprise IT Track Parallels Virtuozzo Containers Hands-on Lab