1. VERITAS Global Cluster Manager™
Addressing Global Application Availability
Good afternoon. And thank you for joining us today on our discussion of Global Cluster Manager, selling for success.

2. First Step: Assessing Your Disaster Recovery Needs
Mins
Days
Hrs
Secs
Wks
Recovery Point
Recovery Time
HA Zone
What is your Recovery Point Objective (RPO)?
What is your Recovery Time Objective (RTO)?
But as with any HA solution, it comes down to how much HA do they need and how much can they afford (both downtime and the technology needed to maintain their HA goals).
One way of looking at HA and downtime is this diagram developed by Gartner.
Recovery Point Objective
Recovery Time Objective
So mapping this out, we can see how certain DR solutions correlate to RPO and RTO.
Traditional DR with tapes …
Remote copy (via replication) …
The combination of GCM/VCS/replication …
***
As addressed by DR consulting:
Many of you are already familiar with RPO and RTO.
RPO is, how old can the data be before it starts to significantly impact business functions in terms of a goal. For example, If you are an online brokerage and you lose 1.2 million every six seconds that you are down and you’re vulnerable to significant litigation, your RPO for trading data may be zero.
RTO is, how long can end users wait before they need to access systems and data before there is significant impact to the viability and success of the business. Again, in terms of a goal. If you are a retail firm and you have a decentralized system with many stores, some only two blocks away from each other, your RTO may be three days. It may be possible to reroute business or do transactions using a manual method while waiting for systems to be restored.
Availability is a modern term for disaster recovery used among some DR professionals and DR services providers. Your clients will probably call it DR, but some of your real experienced clients such as those in finance might refer to it as availability. Usually though, your clients will stick to DR as a term they are comfortable with. I recommend you stick to the term DR since that’s what our marketing folks have chosen and most clients understand this term best.
Okay, this next term is going to be a switch for some of you from the software world, but this is to educate you on the DR world perspective of clients and competitors who have been doing this for 20 years.
High availability is a mitigation strategy. We implement high availability solutions in order to prevent an actual business interruption event. High availability can not replace DR. Remember that DR includes escalation procedures, detailed recovery tasks, site migration and testing. High availability solutions are an integral part of an overall DR strategy for many clients, but this term only refers to technology and it does not replace a DR program. You can have everything clustered and replicated but that’s not a complete DR strategy.
So, when you think high availability, think of things you do ahead of time like clustering and replication technology.
When you think DR, think of the symphony of processes including people, facilities, and technology that’s required to bring about complete recovery. This definition is supported by Gartner by the way and you can find the article on our DR VNET site.
Traditional
DR with Tapes
Remote Copy
(Replication)
GCM & VCS & Replication
RPO: hours RTO: hours
RPO: <5 minutes
RTO: <6 hours
RPO: < 5 minutes RTO: <1 hour

3. VERITAS Can Help You Meet Your Disaster Recovery Requirements
0 to 500m*
0 to 80km*
0 to  km
Local Clustering
Metropolitan Clustering
(I.e., Stretch/Campus Clustering & RDC)
Global Clustering
VVR
VVR
VVR
To address RTO and RPO, VERITAS offers a wide range of HA solutions.
Basically, we’re one of the few vendors out there who can cover the entire range of availability. And we’re just about the only one who can do this heterogeneously.
For local clustering, this is HA for clusters that are located in one data center right next to each other. This is most common and built on VCS + VM.
For metropolitan clustering, we offer two solutions:
Campus or stretch clustering:
VCS + VM (over SAN, DAS, or NAS)
1 VCS cluster, automatic failover.
With VM, you can have any storage devices.
Some marketing initiatives driven by Michelle Mol, PMM for VCS.
Collateral: bulleted whitepaper detailing benefits and features of each architecture, particularly stretch clustering.
Some performance testing, additional information is forthcoming. We’re testing performance for distance intervals of 10km, 20km, 30km, 50km, up to 80km.
Replicated data cluster:
More of an architecture, vs actual product offering (we do have V-SKUs for this tho)
VCS + replication
1 VCS cluster, therefore automatic failover
1 for 1 matching of service groups
For the current release, we support VVR on Solaris only; EMC SRDF support for Solaris, Windows, HP-UX, and AIX; Hitachi TrueCopy on Solaris only.
Data is replicated over IP.
Customers choose this option because they can’t afford a SAN or dark fibers. Cost of IP network is cheaper.
Finally, we have wide area clustering. Ultimate in disaster recovery. And perfect for customers who can’t afford any downtime but can afford such a sophisticated solution. The GCM solution isn’t for every customer out there, mind you. But even if your customer doesn’t want it, it’s worth mentioning because it demonstrates the maturity of our solutions. And as demonstrated from the blackout on the east coast, corporations and government agencies who want to stay up and running need a solution like GCM.
***
Note that for application and data availability, VERITAS supports a complete range of architectures that match your needs. From local to metropolitan to global protection.
VCS supports local clustering and metropolitan disaster recovery today. For wide area disaster recovery, Global Cluster Manager is required.
VERITAS recognizes that not all data center environments are alike.
Using VERITAS Cluster Server as a stand alone solution or in combination with other VERITAS products, availability can be achieved in almost any environment.
Three primary architectures are used as the foundation for application availability in a Windows environment:
·        Local area clustering using shared SCSI or SAN attached storage
·        Stretch clustering for campus or metropolitan area environments using SAN attached storage
·        Wide area clustering for disaster recovery spanning larger geographic distances
The key to this architecture slide is to emphasize that a customer who purchases Volume Manager and Cluster Server (or Foundation Suite/HA) can achieve local availability as well as metropolitan disaster recovery for no additional costs. Metropolitan Disaster Recovery (also known as Campus Clustering or Stretch Clustering) has been a prominent deployment for several companies who’s service level agreements don’t require a disaster recovery site to be across the country. Rather than investing in a disaster recovery site thousands of miles away, a customer can invest in a disaster recovery data center in the same city. The cost savings are tremendous! The minimal requirements is that the customer has a SAN infrastructure. The distance limitations depend on the latency that the customer is willing to afford. VERITAS recommends within 100 km. Remote Mirroring technology found in Volume Manager is used to replicate the data between the two sites synchronously. If the customer has already purchased Volume Manager and Cluster Server, this is a bonus that is part of the feature set.
A customer example using metropolitan disaster recovery is a large bank in NYC who has fiber under the Hudson. Their remote site is in New Jersey. This is sufficient to meet their disaster recovery needs at an affordable price.
VM/VCS
Local Mirror
SAN or Direct Attached
VM/VCS
Remote Mirror
SAN or Direct Attached
SRDF-HTC-VVR/VCS
Replica
IP, DWDM,
ESCON
SRDF-HTC-VVR/VCS/GCM
Replica
IP, DWDM,
ESCON
(Metropolitan DR)
(Replicated Data Cluster)
* Indicates distance guidelines. Actual depends on latency.

4. Global Cluster Manager: Elevator Pitch
Site Migration
Application
Volume Manager
Volume Replicator
Cluster Server
Global Cluster Manager
Global Cluster Manager is the industry-leading, out-of-the-box HA solution that allows you to automate entire site takeover of mission critical applications and data in the event of a major disaster
KEY: Monitoring AND Action
Application
Volume Manager
Volume Replicator
Cluster Server
Global Cluster Manager
So the bottomline: GCM extends the app failover…
The key is that with GCM, it allows for real time monitoring and directs action to affect global failover.
***
Synchronous replication is more or less mirroring over some sort of network.
The data is not acknowledged as written (committed) at the primary, until it is sent to the secondary, acknowledged to have arrived, and then posted as completed at the primary.
The strength of synchronous is that the data is fully current (or up to date) at the secondary. With synchronous there is NO chance for ANY data loss. Not even a few milliseconds of data loss. The ultimate RPO.
However, the big downside is that network latency may directly impact application performance at the primary.
“The speed of light is not just a good idea, it’s the law.”
However, this application performance impact is highly application dependent. We’ve seen people replicating over fairly long distances with relatively low application impact. For write intensive or very long distance replication scenarios, synchronous is probably not the optimal choice.
At VERITAS, we see about 50% of our customers that deploy replication solutions going with synchronous.

5. Key Product Benefits and Features
FAST, AUTOMATED DATA CENTER RECOVERY
One-click site failover across subnets
Automatic DNS update to re-direct client traffic
No distance limitation
ROBUST, COMPLETE MANAGEMENT SOLUTION
Centralized management control for clustering and replication
Manage VCS clusters running all major open systems platforms
Trusted solution that is deployed worldwide
OPEN SOLUTION
Supports AIX, HP-UX, Linux (limited), Solaris, Windows
Compatible with VVR, EMC SRDF, and Hitachi TrueCopy
Expanded application coverage for Exchange 5.5/2000, Oracle 8i/9i, SAP, Siebel, SQL 2000 (just to name a few)
Key benefits:
If I had three key take aways with GCM, it’s these:
Fast, automated data center recovery
Centralized management
Most of the time, our customers are looking at GCM for the DR capabilities, but don’t forget to also tout the multi-cluster management associated with DR and regular VCS clusters
Finally, open solution with multiple vendors. Also, “out of the box” support for key applications like Exchange, Oracle, SAP, Siebel, and SQL Svr.

6. Global Cluster Manager is Ideal for Customers Who…
…Want high availability protection against catastrophic disasters
…Have a Recovery Time Objective of 1 hour or less
…Would like a way to automate the manual process of migrating services from one location to another for DR or maintenance purposes
…Want the ability to manage their disaster recovery solution from a single point
…Have EMC SRDF or Hitachi TrueCopy and want a solution that will integrate with existing investments for a complete disaster recovery solution
“I have an RTO objective of 1 hour or less”
Again, this is to identify the customers who need the absolute in application and data protection. These are generally customers with the most stringent uptime demands. Generally, from our sales data, we’ve observed these customers to be financial institution, government agencies, and certain telcos. We’ve of course also seen some customer demand from utilities and other companies that have 24x7 needs, like logistics companies.
“I would like a way to automate the manual process of migrating services from one location to another”
Another interesting way to position GCM is that it can also be used for site migration due to regular maintenance. I’ve actually seen some customer interest in this. Basically, the customer doesn’t want to have to manually migrate services to a different site when they’re doing upgrades and what not. Generally, these migrations are across the country or continents, but usually within the same county. Just additional thoughts on GCM’s application.
“I want the ability to manage my disaster recovery solution from a single point”
Single point of administration
“I have SRDF and and want a solution that will integrate with SRDF for my disaster recovery solution”
This goes back to the investment protection that our customers want from their EMC purchases. We don’t want to be shut out, just because the customer wants to use EMC SRDF. My engineers think that VVR is better technology, but it makes sense for us to accommodate what we find in the field when it relates to this.
When to walk…
Of course, we walk when the customer is talking mainframe. Goes without saying, but I thought I’d say it anyways.

7. Seeing the Business Benefits of VERITAS DR Solutions
DELIVER ON YOUR SERVICE LEVEL OBJECTIVES
Eliminate unplanned and planned downtime
Remove time-consuming manual processes after a disaster strikes to facilitate rapid recovery and resumption of business
Seamless client re-connection to IT services after failover
MANAGE ESCALATING COSTS
Faster deployment and ROI with wizard driven installation
Lower administrative costs through more efficient use of IT staff
More efficient problem isolation and troubleshooting with simplified, web GUI management
OPTIMIZE EXISTING INVESTMENTS
Better ROI on existing storage/server investments
Tight integration with other VERITAS HA products for better interoperability
What to tell the sys admins.
Alright, I won’t belabour this slide, since you can read on your own.
But our messaging is focused around three main areas:
Eliminate Downtime:
Simplify management:
And Build on your existing investments:
With the system administrators, you want to address the pains that they feel if something goes wrong.
For example, you highlight whiz-bang capabilities of GCM, like being able to recover in a matter of minutes, not hours.
You also want to emphasize automation: be it the actual failover, or the failback, or even client re-direction.
You might also highlight how this solution diminishes distractions and manual processes when a disaster strikes.

8. Advantages of Using VERITAS Global Cluster Manager
Competitors
What’s Unique with Global Cluster Manager?
Microsoft Cluster Server
(For Windows)
Our automated, global failover ensures that no split brain problems occur (unlike MSCS)
We support up to 32 servers per site (superior scalability)
Integration with industry-leading replication products ensure data integrity
GCM is designed specifically for wide-area application/data failover
IBM HAGEO
(For AIX)
Faster failover through web GUI
Wizard driven installation process to facilitate rapid deployment
Failback process is automated & simply managed with minimal downtime through the GUI (vs. scripts/CLI)
We support more robust replication: SRDF, TrueCopy, VVR, and soon PPRC (vs. IBM GeoRM)
Even IBM Global Services recommends VERITAS as the standard open systems DR solution
HP MetroCluster or ContinentalClusters
(For HP-UX)
GCM’s GUI offers one-click site failover (vs. command line)
GUI also offers simplified visual management of multiple clusters
Automated failback process
We support flexible configurations for multiple sites, failover directions, replication products, cluster configs
No Competition
(For Solaris)
GCM is the industry’s only cross platform, global clustering solution
Customer references attest to product robustness and effectiveness
(read the slide)
***
GeoRM: Geographic remote mirroring, not adopted by many customers