John Day Worldwide SE – Product Operations Interlock Clustering

1. UK John Day Worldwide SE – Product Operations Interlock Clustering VERITAS Worldwide Backup Exec & NetBackup Pro SE Conference February 26 - March 1, 2002

2. Overview of Territory UK 552 employees 176 Sales in total of which 35 PreSales SE’s (Traditional VRTS & APM) & BDM’s • AstraZeneca, BSkyB, BT • Centrica, Egg, H3G, HBoS, Insinet • Norwich Union, PowerGen (eon) • RBS, Reuters, Vodafone Usual Suspects: Sun, HP, IBM, Microsoft & RedHat is emerging TSM, CommVault, HP Data Protector (if incumbent, we tend to lose)

3. Strengths Platform Coverage:- Both OS and Hardware Support Ease of Installation And Use Application integration Market Share Cluster Configurations:- Local, Campus (stretched), DR # Reference Accounts Resellers: - Poor generally – VERITAS drive the deal & design Partner with Fujitsu-Siemens, SCC Competitors: Sun - easiest to kill, Microsoft, IBM, HP

4. Weaknesses Pricing – especially Linux, but CPU has made it better Less differentiation as competitors get better Integration with other VERITAS products i.e. SF for Oracle No forced umount of file systems with Storage Checkpoints No ability to easily clone applications (integrating with checkpoints) via GUI if using SF for Databases Trigger implementation is could be better /opt/VRTSvcs/bin/CLUSTERNAME/SG preonline, or resstatechange on resource name

5. Weaknesses Our documentation can be poor Release notes – Should contain all info required i.e. Active Directory with SFW4.1 W2K VCS 4.0 I/O Fencing VxVM support HCL Poor Agents – MultiNICA i.e. AIX (default gateway) Lack of Agents to Support our own Products i.e. CC when released lack of agent platform coverage Pulling support for Agents between releases i.e. VCS2.0 Windows & Oracle supported in SFW/HA 4.1 its Consulting currently New Technology support i.e. iSCSI & VCS – more requirements with Windows

6. Opportunities For existing customers, VCS 4.0 gives us a complete story across platforms i.e. Unix with I/O Fencing or GCO across all (come on HxRT 4.0!!) IBM & HP – Still huge markets for us to go after Linux – Not many early adopters, but some are large:- TPG with large requirements 64 clusters with GCO Linux on pSeries?

7. Threats Competitive blocking: Microsoft, HP & Sun Big issue with negative attitude of Microsoft (esp. Centrica & DHL) Potentially EMC acquisition of Legato Support for new OS features i.e. Micro partitioning or VirtualSCSI with AIX

8. Wins • TPG: FST/HA on Linux with WebSphere HP, RedHat Each Vendor had 3 days to install test environment VERITAS – Completed in 1.5 days with no issues HP – Couldn’t get cluster working and got 2 extra days! Completed install just in time. Also wanted customer to use VxFS! RedHat – Working config, issues of replicating cluster XML config file and no central management, came in second place

9. Wins VERITAS was the superior product, customer has stated that the ease of install (parallel), ease of use, central admin console, unified logs where distinguishing factors. Hoping to close $800,000 for European rollout of RedHat end of Q404 • Fidelity on AIX platform.  Long range clustering capabilities • Lloyds TSB (Create Services).  Simplicity and speed of configuration • Depart of Works and Pensions (DWP) because Oracle told them so

10. Losses DWP (another part) because SUN gave the software free on the back of a large hardware deal and guaranteed zero downtime (“I nearly fell of my chair laughing!!!!!” Simon Gregory)  Lost at Citigroup to Sun Cluster. VCS/RAC had won technically and commercially, unfortunately in the US the project was running Sun Cluster and seeing that this was a US led project Citigroup are being force to go Sun Cluster in the UK DHL to MSCS due to (then) lack of timely W2K3 support & Microsoft attitude

11. Top 10 – no particular order 1. Integration with our product stack – Storage Checkpoints etc This is a must, customers want to use check pointing in clusters but currently have to script or have customized procedures. 2. Triggers – Preonline, offline etc /opt/VRTSvcs/bin/ClusterName/SG – more granularity 3. Inter OS Service Group dependencies. We do not need to fail over service group between OS, but often we have a application running on 1 OS that has dependencies on a machine running a different OS. Although we would not failover between OS’s, it would be nice to be able to put Service Group dependences between them, also would give us a massive competitive advantage over the opposition. 4. Pull in V4.0 Release Train on HP-UX

12. Top 10 5. Routable heartbeats 6. vrtserr command – Like oerr in Oracle; Our error messages aren’t documented that well – should provide meaningful information on problem and resolution; Good for customer and support 7. –wait option for ha commands i.e. hares, rather than exit after execution, waits until complete of online period for resource/service group, enabling checking of exit status for custom scripts 8. GUI Enhancements i.e. cut and paste for moving resources. Agents should use drop downs should & contain only supported options i.e. VxFS, UFS, JFS etc on a platform basis otherwise we are too free form. Flag mandatory attributes in GUI i.e. with a color. For LogLevels again use dropdowns

13. Top 10 9. Debugging/sizing tools for SFRAC - better than lmxstat 10. A scheduler for managing downtime.