1 / 38

VCS Agents SE Interlock ‘06

VCS Agents SE Interlock ‘06. Q1’06. Roger Davis Product Manager, HA Solutions Todd Ruhl Technical Product Manager, HA Solutions. Agent Agenda. Roadmap Agent Strategy Selling HA Solutions for ISV Applications Competition. (+SLES). Standardization: Major Apps & DBs. Q2’06.

Download Presentation

VCS Agents SE Interlock ‘06

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. VCS Agents SE Interlock ‘06 Q1’06 Roger Davis Product Manager, HA Solutions Todd Ruhl Technical Product Manager, HA Solutions

  2. Agent Agenda • Roadmap • Agent Strategy • Selling HA Solutions for ISV Applications • Competition

  3. (+SLES) Standardization: Major Apps & DBs Q2’06 -- Today -- 10gR2 , 15 , .10 NetWeaver , 7.8 , 9.0 , 9.0

  4. Primary Source of Agent Information: The Agent Matrix and Roadmap • VNET\Products\Cluster Server\Agents & Options\ VERITAS Cluster Server Agents List • http://eval.veritas.com/mktginfo/products/Sales_Docs/High_Availability/agent_list.xls • Continually updated – a living document • Lists all the VCS agents, for all the platforms • Categorizes agents • Lists key compatibility information • Authoritative roadmap: reasonably up-to-date • It is no longer a download site for agent binaries • ICG’s are downloadable

  5. Future of Agents: Our Strategy • Dominate large, fast growing sectors identified with HA • Increase primary application focus on ERP (SAP) space • Leverage Consulting and generic “Solution Bundles” • Extend strategy for current DB and Application agents • Continue with quarterly Agent Pack CD as release vehicle • Ensure that agent portfolio is compatible with VAD and VCS

  6. TPM Support for ISV Solutions • Paul Belk • SAP • Manuel Braun • SAP and SAP/RAC certifications • Kevin Barth • WebLogic, WebSphere, Oracle App Server • Todd Ruhl • Siebel, PSFT, Oracle E-Business, MQ, Tuxedo, Sun Messaging Server

  7. Deeper Dive on ISV AgentsTodd Ruhl • A few HA/DR configurations – SAP • Common objections • Suggestions for selling • Competitive notes

  8. Example: SAP HA Configuration VERITAS Cluster Central Svc NFS Svc Central Svc NFS Svc Web Disp Router (ECC & EP) Database Server (ECC & EP) Dialog Instance Dialog Instance Enqueue Replication Enqueue Replication DB Web EnqRep Dialog SCS EnqRep Dialog SCS ERP Central Component (ECC) Enterprise Portal (EP)

  9. DB Web EnqRep Dialog SCS EnqRep Dialog SCS Rockwell SAP HA Configuration Veritas Cluster Web Dispatcher & SAP Router (ECC, SCM, XI & EP) Dialog/Application Server Instance Dialog/Application Server Instance Dialog/Application Server Instance Dialog/Application Server Instance Central Svc & Enqueue Replication Central Svc & Enqueue Replication Central Svc & Enqueue Replication Central Svc & Enqueue Replication Central NFS Services Database Services (ECC, SCM, XI & EP) ERP Central Component (ECC) Enterprise Portal (EP) Supply Chain Mgmt (SCM) Exchange Infrastructure (XI)

  10. Common ObjectionsWhy Cluster All Tiers of My Application? • Why clustering redundant or HA-capable services? • Multiple instances of the service may exist • SAP dialogue instances • PeopleSoft application servers and web servers • Siebel application servers • Service already has HA capabilities • WebLogic and WebSphere clustering • Tuxedo domains • Sun Messaging Server watcher process • MQ parent process restarts child processes

  11. Why Cluster Redundant or HA-Capable Services • Limitations of HA-capable application services • They enhance HA for that app service only • They are unaware of other app services—no coordination • Their response to failure is often limited (e.g. service is removed from the load-balancer only—no restart attempted) • The feature helps, but cannot achieve the overall level of HA offered by VCS • Reasons to cluster all application services • To manage interdependencies among services at all tiers • To facilitate and expedite system maintenance • To simplify application management (start, stop, and monitor all services from the same interface) • To ensure performance capacity (get the failed app or web server back online ASAP) • Clustering all services is essential to a reliable DR solution • Some single points of failure are “grey” (e.g. Siebel Gtwy)

  12. Example: Ferrellgas HA Configuration

  13. Example: Ferrellgas HA Configuration

  14. Selling Tools • Immerse yourself in the customer’s application requirements (their pain, problems, objectives, and issues related to HA). • Capture them in diagrams and descriptions • Summarized list of driving requirements • Diagram of existing or “currently planned” environment • List of hardware and application software to deploy • Diagrams of proposed environment • HA use cases

  15. Selling ToolsDiagrams of Existing/Planned Environment CIC Example

  16. Selling ToolsList of Hardware and Software to Deploy

  17. Selling ToolsDiagrams of Proposed Environment Veritas Cluster Msg Srvr LDAP Msg Srvr MMP Hot Standby Msg Srvr1 POP/IMAP Msg Srvr2 POP/IMAP Msg Srvr3 POP/IMAP Msg Srvr MTA - In Msg Srvr MTA - Out MMP Msg1 LDAP MTAout Msg2 MTAin Msg3

  18. Selling ToolsDiagrams of Proposed Environment

  19. WAN Selling ToolsDiagrams of Proposed Environment Global Cluster SAP Deployment at AIG Site A Site B App Srvr 1 App Srvr 2 App Srvr 3 App Srvr 1 FTP App Srvr 2 App Srvr 3 FTP CI CI Hot Stand-by DB Server Hot Stand-by TE Server DE Server DB Server TE Server DE Server App2 App3 App1 App2 App3 App1 Volume Replication FTP CI FTP CI IP Network TE DE DB TE DE DB

  20. Selling ToolsProof Point – Ferrellgas Deal - TOC Requirements and proposal captured in one document

  21. Selling ToolsProof Point – Ferrellgas Deal - Events Sample of detail event/response requirements in the proposal

  22. Selling ToolsVNet Agents & Options http://prod.veritas.com/Products/vnet?c=optionlisting&refId=20

  23. Selling ToolsVNet Agents & Options – Example Detail Page This section visible from public web site: http://www.veritas.com/Products/www?c=optionlisting&refId=20

  24. Selling ToolsVNet Agents & Options – Example Detail Page Internal only, you see this information: Sales Tools

  25. Selling ToolsVNet Agents & Options http://prod.veritas.com/Products/vnet?c=optionlisting&refId=20 If questions remain, use AskPM or contact the TPM directly

  26. Other Selling Suggestions • Engage early in the application planning process • Influence number, type, usage of servers, SAN, etc. • Engaging after key decisions have been made may constrain the solution • Beware of consultants from SI’s and the ISV. Strong knowledge of application, but limited knowledge of HA/DR • Engage a SME as needed (ECS or TPM) • To facalitate capturing requirements • To create proposal • Engage ECS for an HA design project • 1-3 days for smaller app deployments • 5-10 days for larger • Be sure to secure an experienced architect for this • For deployment, engage a consultant with experience in clustering the application

  27. Competitive Notes • Platform Vendors • Most have the major packaged apps covered (agents) and have better relationships (eng and sales) with the ISVs • Application Vendors • SAP developed their own HA solution using MSCS; VCS not a supported configuration for SAP on Linux & Windows • WebLogic continues to add features which enhance HA and DR • PeopleSoft has a HA/DR solution whitepaper which suggests clustering software is unnecessary • Symantec has more off-the-shelf, supported agents • Generally, ISV agents more robust and intelligent in all entry points • Intelligently delaying first-monitor event until fully instantiated • Multiple levels of monitoring and custom monitoring • Ability to control and tune performance impact of monitoring • Latitude in monitor entry point that allows a service having temporary problems to self-correct before faulting it • First failure data capture • Thorough and reliable methods to clean the system after a fault occurs

  28. Backup Slides

  29. MC/SG

  30. HACMP Application Enablers Orderable Enablers Smart Assists HACMP Smart Assist for WebSphere Downloadable enablers HACMP plug-ins DNS plug-in DHCP plug-in Print server plug-in HTTPServer plug-in HACMP XD (Extended Distance) Tools GMDSizing tool Application Integrators Application Server Oracle Application Server 10g - Cold Failover Cluster Database DB2 Universal Database EE v5.0 DB2 Universal Database v5 and beyond (now include HA Scripts!) Oracle Release 7.3/8 Oracle Release 7.3/8/8i Transaction Monitoring Tivoli Enterprise 3.6 Enterprise Availability Management Candle Command Center DB2 UDB EE v5.0

  31. Red Hat Cluster Service failover: Red Hat Cluster Suite not only ensures hardware shutdowns or failures are detected and recovered from automatically, but it also monitors applications to ensure they are running correctly and restarts them automatically if they fail. For high-volume open source applications, such as NFS, Samba, and Apache, Red Hat Cluster Suite provides a complete ready-to-use failover solution. For most other applications, customers can create custom failover scripts using provided templates. Red Hat Professional Services can provide custom Red Hat Cluster Suite deployment services where required.

  32. Microsoft Cluster Server (MSCS) Scripting Existing applications can be made Server cluster-aware using scripting (VBScript and Jscript) rather than writing resource dlls in C or C++. Benefits Easier Development – makes it much simpler to write specific resource plug-ins for applications so they can be monitored and controlled in a Server cluster. Supports resource specific properties, allowing a resource script to store Server cluster-wide configurations that can be used and managed in the same way as any other resource.

  33. Potential New Application Markets for Agents: > ~$1B Size, with CAGR > ~8% “Current agent coverage”

  34. Outside of Application Space, Market Targets: > ~$1B Size, with CAGR > ~8% Application Management Markets ($M) System Infrastructure Markets ($M)

  35. Future Directions • New Agents • How do we determine which markets to target? • Which need HA? • Timeframes…

  36. Increase Revenue with Current Agents • Expand commitment to SAP • Leverage Consulting Agents • Leverage Bundled Agents • GenericService Agent • Application Agent • Process Agent

  37. Address SAP-related Product Issues • Solve the Linux issue: VCS without kernel components • Get support for Windows SAP agents (need new API calls) • Increase coverage of types of SAP servers. Build new: • Agent for SAP DB/MaxDB database (on the roadmap) • Agent for LiveCache (on the roadmap) • Enqueue Replication agent (on the roadmap) • Partner with SAP to coordinate requirements and releases • E.g., need shipping agent in sync with coming versions of SAP NetWeaver-s. • Coordinate Symantec product solution efforts across departments and product groups • I.e., Data Protection, Availability, Performance, Storage Management

More Related