SM-B09: Confidently Virtualize Business Critical Applications On VMware, KVM, LPAR and LDOM with ApplicationHA 6.0

Transcription

1 SM-B09: Confidently Virtualize Business Critical s On VMware, KVM, LPAR and LDOM with 6.0 Bob Goodyear Regional Product Manager Lorenzo Galelli Technical Product Manager Blog :

2 Welcome! SM-B SYMANTEC VISION

3 What You Will Learn 1 Availability Challenges w/virtualization 2 w/vmware 3 w/kvm, LDOM, & LPAR 4 Managing Multi-Tier Apps w/ SM-B SYMANTEC VISION

4 Virtualization adoption Ensuring Availability with VMware The Problems Key Challenges: Ensuring Key Challenges Availability Low adoption beyond Tier 3 TIER 3 TIER 2 TIER 1 IIS Apache Print WebLogic WebSphere File SQL, Oracle SAP Exchange Criticality of applications VM up up VM boot up or recovered started or recovered processes up functional VM boot up order startup order SM-B Source: IDC, October Choosing Storage for Virtualized Servers. For companies with > 1,000 employees. SYMANTEC VISION

5 Current tools and processes force challenging trade-offs Ensure everything O/S based clustering in the guest Prevents use of vmotion, DRS, DPM Increases cost + complexity Virtualize everything Minimize Ensure App admin Complexity Availability Infrastructure admin Exploit Virtualization Monitoring tool + scripting Longer RCA and recovery time Burden to maintain scripts Delay virtualization Slows down virtualization initiatives Increases operational complexity SM-B SYMANTEC VISION

6 High Availability in Virtual Environments Availability High Availability Infrastructure Availability SM-B SYMANTEC VISION

7 3 w/vmware SM-B SYMANTEC VISION

8 Symantec + VMware : Virtualize without compromise VM1 VM2 VM2 Symantec protect application components App Components Resources c2 c1 c3 c1 c2 c1 c2 c3 c4 VMware protect infrastructure components VM ESX Server VMware ESX Site SM-B SYMANTEC VISION

9 Coordinated recovery between and VMware App monitoring Show health status Detect app failures Coordinated recovery VM1 ORA VM2 SQL Restart applications Force reboot Trigger VMware for further recovery Integration via App Monitoring API Protects against wide range of failures Infrastructure failures VM is up but app is down VMware VMware ESX VM recovers after a server failure but app doesn t App is up but not functional SM-B SYMANTEC VISION

10 Coordinated recovery between & Veritas Cluster Server or VMware Deep understanding of the apps VM App specific modules start, stop, recover apps Eg: SQL DB instances, FileStream, Analysis, Storage mount points, dependencies Functional testing based on SQL queries Broad support for & apps App support updated every quarter Customizable recovery behavior App or VM restart limit App Agent Pack ORA DB2 In-guest remediation only - Enable/Disable App Heartbeat Turn off remediation during planned maintenance - Enter/Exit Maintenance mode VMware Host SM-B SYMANTEC VISION

11 Ensuring Availability for Custom s A Choose Custom B Configure Process Parameters SM-B SYMANTEC VISION

12 Visualize and control apps from vsphere client - screenshot VM Selected Status Operation Detailed Monitoring SM-B SYMANTEC VISION

13 Dashboard for Visualizing Status and Controlling s Dashboard also available on cluster level. Data Center Level Batch Operations Aggregated Statistics Alert Details SM-B SYMANTEC VISION

14 + Backup Exec Taking Availability to a New Level via Integration with Backup Exec Escalation of Remediation Mechanism Restart Virtual Machine Reboot Virtual Machine Image Recovery Automatically restore, or trigger a prompt for consent to restore, a failed virtual machine in order to recover lost application services once has exhausted the steps available to remediate the failure. SM-B * 6.0 feature.

15 Backup Exec Virtual Machine Auto Recovery Authenticated and encrypted communication VM1 Console Auto Recovery Enabled VM2 SQL VM3 EXCH vcenter Server Configuration 1. Backup Exec virtual machine backup and monitoring configured separately. 2. Enable Auto Recovery from within Backup Exec tab VMware VMware ESX VMware VMware ESX Remediation Escalation Path 1. restart BE Media Server vsphere Client Tab 2. Virtual machine restart 3. Virtual machine image recovery BackUp Exec Client Backup Exec UI VM 2 Backup VM 1 Backup VM 3 Backup SM-B * 6.0 feature.

16 Optimize Availability with VMware Exploit Virtualization in VMware environments vmotion Fault Tolerance DRS VMware SRM VMFS NAS RDM iscsi Support for virtualization features. Storage flexibility SM-B

17 Bringing Awareness to Site Recovery Manager Monitoring on Both Sites During Test and Real Recovery Test Recovery Site A Site B Real Recovery Automatic application monitoring enabled on both sites Automatic establishment of communication with VMware on recovery site Dashboard view on both sites with secured communication awareness in SRM audit trail Report application status in SRM audit trail Proof to auditors and/or management SM-B

18 working in SRM environment Protected Site Recovery Site vsphere Client vsphere Client dashboard dashboard DB DB DB DB SRM Server Console Console SRM Server getappstatus.bat VM1 VM2 VM3 VM1 VM2 VM3 EXCH SAP ORA SRM Failover EXCH SAP ORA VMware Resource Mapping VMware ESX ESX ESX ESX ESX SM-B

19 3 w/kvm, LDOM, & LPAR SM-B SYMANTEC VISION

20 Symantec + Veritas Cluster Server KVM / LDOM VM1 VM2 VM2 Symantec protect application components App Components Resources c2 c1 c3 c1 c2 c1 c2 c3 c4 Veritas Cluster Server VM Infrastructure VM Restart for App failures VM KVM / LDOM HT Control / Domain Site SM-B SYMANTEC VISION

21 Symantec + Veritas Cluster Server: LPAR VM1 VM2 VM2 Symantec protect application components App Components Resources c2 c1 c3 c1 c2 c1 c2 c3 c4 Veritas Cluster Server VM Management VM VM VM Restart for App failures LPAR Site SM-B SYMANTEC VISION

22 VCS + for Complete High Availability Modular monitoring monitors application VCS monitors VM/Infrastructure Joint application aware VM monitoring Coordinated application recovery restart VM restart on same server VM failover to standby server Simplified Management Veritas Operations Manager Host level clustering Communication between VCS & for fault remediation VM APP VCS HT VM ORA VM ORA VCS HT VM APP SM-B SYMANTEC VISION

23 Management of via Veritas Operations Manager Central management for Unix / Linux & VMware Hypervisors Tiering via Business Entities & Virtual Business Service Operation Detailed Monitoring Status SM-B SYMANTEC VISION

24 4 Managing Multi-Tier Apps w/ SM-B SYMANTEC VISION

25 Business Services in Virtualized Data Centers Billing Web server Service Start High Availability Status Summary Service Stop Disaster Recovery Security app app app Database Personnel unavailable? Different Tools Coordinated recovery Different Passwords Handle Virtualization SM-B

26 Multi Tier s & Services Billing Veritas Operations Manager Web server Service Group Service Group Web Web Symantec VM VM Service Group App app app app IP Veritas Cluster Server VCS Database Service Group DB IP VVR FS Veritas Cluster Server /DR VCS SM-B

27 Virtual Business Services Billing Web server Service Group Web Service Group Web Veritas Operations Manager VM VM Billing Virtual Business Service Service Group Web Server SG app app app App IP Server SG Database Service Group DB Database SG IP VVR FS Start/Stop Order Inter-cluster fault policy SM-B

28 SM-B

29 If you virtualize, you must Symantecize! SM-B

30 Summary: Virtualize business critical apps with confidence & without compromise Problem Solution Benefits Ensure availability Without trading off virtualization benefits Without taking on operational complexity VMware & Symantec bring best of breed technologies together to address this VMware + Recover from app & infra failures quickly Exploit virtualization benefits such as vmotion, DRS, DPM, Simplify operations for app & infra team with solution that is easy to deploy & manage Call to Action Review challenges in your virtualization initiatives with your business critical apps Download white paper & learn more Download trialware SM-B SYMANTEC VISION

31 Thank you! Copyright 2012 Symantec Corporation. All rights reserved. Symantec and the Symantec Logo are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. This document is provided for informational purposes only and is not intended as advertising. All warranties relating to the information in this document, either express or implied, are disclaimed to the maximum extent allowed by law. The information in this document is subject to change without notice. SM-B