Mendocino Software

1. Mendocino Software Tony Del Favero – Sales Director Mendocino Software, Inc. HP Continuous Information Capture (CIC)

2. Agenda • Partnership Premise • Why Continuous Data Protection (CDP) • HP Continuous Information Capture (CIC) • Beyond CDP • Data Anywhere • Architecture • Use Cases • Customer/Organizational Targets • WIFM • Customer Examples

3. Partnership Premise • Directly aligned with HP growth strategy • Enhances ability to extend server and storage leadership • Attack competitively held storage accounts Provides Hewlett-Packard and their partners with a first-mover opportunity to dominate in the rapidly emerging $4 billion CDP market.

4. ACROSS ENTERPRISE DATABASE ENVIRONMENTS Basic cost 27% Other 10% SW Infra structure 11% Application Maintenance 32% DBA & System Administration 20% 52% of database costs are in areas that can require application downtime Source: Ground Up: An Independent Assessment of Sybase ASE 15, The Standish Group International, March 2006 Why Continuous Data Protection? ACROSS ALL APPLICATION ENVIRONMENTS Other 3% Computer Virus 4% Human Error 26% Software corruption or system problem 9% Hardware or system problem 56% Natural Disasters 2% Despite massive investments in Hardware redundancy, 42% of downtime still not well covered Source: ProgresSmart, Storageworld Conference, June 2005

5. Market Trends Gartner “It will dramatically change the way data is protected, decreasing the recovery time and the amount of data lost.” “Hype Cycle for Storage Software Technologies, 2005”, Gartner, June 3, 2005 Taneja Group “What is undeniable now is that CDP technologies, working in direct conjunction with the application, are going tochart the future of information recovery.” “Application Recovery: The Case for CDP”, Taneja Group, June 2005 "There is no question in my mind that CDP technology is vastly more transformational than most folks realize today. It will not only transform the way we protect and recover data but its ability to provide point in time copies will have a major impact on a variety of off host processing areas.” Arun Taneja, March 2006 Enterprise Strategy Group “ The concept of CDP is one of the smartest things ever in the computer business. Prior to CDP, we accepted our pathetic fate in backup: We know it’s awful. . . we know we’re going to throw good money after bad, year after year. CDP is the first significant technological change in backup and recovery in a lot of years. . .” Steve Duplessie, Enterprise Strategy Group, April2006

6. “Vanilla” CDP • Target: • Data Recovery is important • Medium SLA requirements • Very small # of active data copies required • Small # of Servers Time addressable Any point in time Replication – Current point in time • Replication • Target: • Disaster protection for physical site problems Snapshots Daily backup TIMELINE Example 12 AM 12 AM HP CIC – Beyond CDP • CIC Solution • Target: • Protection for physical site problems • Logical corruption • Application Recovery is very important • Short recovery time, minimal loss • High SLA requirements • Multiple data copies required • Zero Host Impact Any customer Configurable event Pre-patch Post-patch Database checkpoint Quarterly close Event addressable Any point in time, plus Annotated business/application processes BUSINESS VALUE • Point in Time • Target: • Data Recovery is somewhat important • Minimal SLA requirements • Small # of data copies required • Some application interruption / degradation is acceptable

7. Optimized Recovery Window Newer Older CIC Architecture Any Selected Server(s) Production Server(s) Multiple Historical Views Data Tap Metadata FC SAN attached Writes Metadata Event marker HP CIC Server RedHat Linux Dual CPU Historical View creation, presentation and use completely de-coupled from production applications Production Storage Recovery Storage

8. Search through error/system logs Recovery Today Step 1 Troubleshooting Find backup & archive logs Step 2 Restore or move data to Recovery or Production Server Step 3 Step 4 Start DB & run archive logs Are you modifying your only non-production copy? Verify recovery point Was diagnostic determination accurate? Step 5 If not… start over…

9. Patch Step 1 Troubleshooting Optimized Recovery Window Review event markers for likely cause Select Event Marker(s)and present historical views to one or more Alternate Servers Step 2 Start application from each historical view and verify optimal recovery point Step 3 Rollback productionto verified recovery point and start application Step 4 View View Recovery Using CIC Production Server(s) Data Tap Production Storage Recovery Storage Alternate Server(s)

10. Beyond Recovery • A variety of users require access to current business-critical data • Test and development • Audit, compliance • Data analytics, reporting • Data protection and recovery • But, conventional copy creation technologies have issues • Copy creation impacts production application • Limited number of copies available • Suboptimal copy creation points to meet all possible needs • Copies take time, disk space, and require planning • What if you could • Instantly create one or more copies of your production environment • To any previous point you select at the time most convenient for you • Without impacting your production applications • Rely on these views (copies) to be readable, writable, write ordered and recoverable images that reliably represent the application state at the chosen time?

11. Virtual Historical Views Any Server(s) Multiple points in time to any point without multi-view storage overhead 8 am View Database View 7 pm View Database View CIC Appliance Transactions written to new locations without modifying existing capture storage CIC Storage

12. Backup Recovery Recovery Servers Database Upgrades Testing Data Warehouse Loading Recovery Storage Data Anywhere Oracle Exchange • Rapid recovery to optimal recovery point • Removes B/U window, reduces frequency • Facilitates testing and upgrades • Enables efficient and frequent data warehouse loading for analytical reporting • Supports heterogeneous storage tiers, volume managers, file systems, and applications Other

13. Database Database View Use Case - Off-host Backup Step 1 Historical Views created and presented on Backup Client Leverage traditional backup to VTL or Tape Step 2 Non-Production Environment Production Environment Datatap Backup Client Tape Production Server Database Sessions Database Sessions CIC Storage CIC Appliance Virtual Tape Library Backup flexibility with no impact on Production

14. Database Database View Database View Database View Database Sessions Use Case - Software Testing Create multiple virtual historical views and auto-present one to each of multiple “test” servers Step 1 Step 2 Run tests; record results Tear down the historical view(s) Step 3 Repeat as needed Non-Production Environment Production Environment Test Servers Datatap Production Server Database Sessions CIC Storage CIC Appliance Delivers Production Data to T&D with no production impact

15. Select Event Marker(s) Present historical views Step 2 Start application Verify optimal recovery point Step 3 Optimized Recovery Window Datatap Use Case - Database Roll-back/Repair Step 1 Review event markers Web App Knowledge Mgmt Analytics App Production Server(s) Recovery Option 1: Roll-back production to verified recovery point Database Views Recovery Option 2: Use historical view for database maintenance (e.g. restore dropped table) Production Storage CIC Storage Alternate Server(s)

16. SAN SAN WAN Use Case – Enhanced DR Primary Site Secondary Site MS Exchange Servers MS Exchange Servers Standby Recovery Servers Recovery Servers HP Continuous AccessSynchronous Replication Mirrored ProductionStorage ProductionStorage HP Continuous AccessSynchronous Replication Mirrored Recovery Storage Recovery Storage

17. 2 Use Case – Enhanced DR Secondary Site • Recovery from hardware failures • Point application to Mirrored Production Storage, make data available to users MS Exchange Clusters Standby Recovery Servers 4 • Recovery from corruption, virus, logical errors • Read mirrored metadata from CIC recovery storage • Capture all existing event markers and views 3 1 6 5 • Roll back to exact point in time required • No data loss • Present virtual LUN to servers, provide read/write access to users • AND/OR • Perform CIC Production Volume Rollback of incremental data to Mirrored Production Storage Mirrored ProductionStorage • Make data available to servers at full production performance Mirrored Recovery Storage

18. Customer Targets • Experienced a recent recovery event • Cannot meet RTO and RPO objectives (internal or regulatory) • Need to reduce/eliminate back up windows • Cannot test upgrades/releases with current data without production impact • Application Criteria • Applications that run 7 x 24 • Applications with high cost of downtime • Applications with a high change rate (i.e. high potential for data loss between snapshots/backups) • Heterogeneous operating systems (HP-UX, Windows, Solaris, AIX) • Application Type • Large Exchange environments (1500+ seats) • SAP Upgrades • RDBMS (Oracle, SQL, Sybase, etc.) test/dev environments • Medical Records • Financial Trading applications

19. Organizational Targets • Application “Owners” • Reside in the business unit, usually not IT • Responsible for integrity/availability of data • Held to SLAs by internal/external customers • Inundated with requests to share current data throughout the organization • Have budget to keep application running, will drive/fund IT to support • Database Managers/DBAs • Initially a tough sell, default to database tools • Once they understand it, quick to recognize value • Key selling points for DBAs • Complimentary to RDBMS tools • Spans multiple databases/OSs/servers (not RDBMS-specific) • Offers DBAs control of data, including full recoveries, without IT involvement • Traditional IT • Recognize shortcoming of tapes and snapshots (RTO/RPO) • Struggle with backup windows and media integrity • Understand/appreciate the technology • BUT, are swamped with priorities--contacts above assist in driving IT to adopt

20. Solution Components Application Server Software License Per Data Tap Software License Per Recovery Server Recovery Server • Hardware • Recovery Server • Recovery Storage • Service • HP installation • 1 year standard maintenance CIC Storage Production Storage Software License Per TB of Storage

21. Why Should I Sell CIC? • Differentiation through leading edge technology • Uncontested value • Existing technology not adequate • Few viable enterprise-class competitors • Access to application owners • Earlier in sales cycle, closer to business requirements • Competitive Entry • Insert CIC to protect competitive storage, gain footprint • Revenue opportunity • Hardware “drag-along” • ~ 3x production capacity for recovery storage • Multiple servers in larger configurations • Multiple use cases • SAN add-on to meet SLA requirements

22. Real Life CIC Examples

23. With CIC, the customer can Reduce the frequency of traditional backups Remove the backup window Instantaneously present historical views to surgically repair the database Standardize on a single solution that supports a heterogeneous environment (storage, storage tiers, volume managers, file systems, applications) SAP Backup Improvements An Entertainment & Media Company • Takes 58 hours to do a full backup of their SAP application • Cannot meet their service level agreements (SLAs) • Requires support for a heterogeneous environment

24. Exchange Recovery Services Cost Reduction A Telecommunication Company • Takes 2-2 ½ hours to backup each 200 GB Exchange database and 40-60 hours for the Exchange Server • Provides individual email restores 5-10 times a week • Experiences minimally 20 hours of data loss from Exchange recovery • With CIC, the customer can • Dramatically reduce recovery time and data loss • Enable infinite snapshot capability without production or storage overhead • Streamline brick-level backup and recovery services • eliminate the backup window • remove backup footprint from production server • reduce backup frequency requirements

25. HP CIC Summary • Unprecedented Recovery Capability • Single-write granularity • Retroactive selection • Unique Secondary Data Management • Remove backup window • Off-host processing • No impact on production applications • Disruptive, but complementary • Optimized for recovery, but widely applicable • Immediate ROI

26. InTechnology John Ward HP StorageWorks Product Manager 07789 178 763 john.ward@intechnology.co.uk HP Colin Westacott Sales Development Manager-ILM 07789 481 045 colin.westacott@hp.com Mendocino Tony DelFavero Director, Sales +1 510 461 0944 tony@mendocinosoft.com JR Moase HP Global Solutions Architecture Team +1 510 331 0603 globalarch@mendocinosoft.com

27. Thank You