1. Migrating from GCM 3.5.1 to VCS/CCA 4.0
Proposed path
28 April 2004

2. Background: Licensing structure of VCS, GCM, and CC Availability
GCM base license
GCM DR option
GCM SRDF agent
GCM TrueCopy agent
VCS 4.0 license
VCS GC option
VCS SRDF agent
VCS TrueCopy agent
CommandCentral 4.0
Management Server
Cluster Monitor
Per site
Per cluster
Per server that is replicating
Per server
Per managed node

3. Migration path for HA Clustering products: Licensing
For customers with valid support contracts for the products on the left, they are entitled to the products on the right…
Out with the old…
And in with the new…
GCM base
CommandCentral Availability 4.0
GCM DR option
VCS 4.0 Global Cluster option
GCM SRDF agent
VCS 4.0 SRDF agent
GCM TrueCopy agent
VCS 4.0 TrueCopy agent
Costs associated with consulting services is NOT part of the free migration entitlement.

4. Overview of License Migration
License migration is managed by Sales Ops. For complete information, please look here:
License migration does not include consulting services or education.
License entitlement could fluctuate, depending on the customer’s production environment, and exceptions will be handled on a case-by-case basis by Sales Ops.
The following guidelines are subject to change.

5. Preliminary Guidelines of Entitlement
For each GCM base license that a customer has purchased, they will receive:
1 license for CommandCentral Availability Management Server
5 licenses for CommandCentral Availability Cluster Monitors
For each GCM base license and GCM DR option that a customer has purchased, they will receive:
1 license of VCS 4.0 Global Cluster option for each server that is already part of the DR failover cluster (up to 32)
For each GCM agent license for SRDF and Hitachi TrueCopy, they will receive:
1 license equivalent for the respective agent in the VCS 4.0 version

6. Migration path for HA Clustering products: Technologically
Installing VCS 4.0 with Global Cluster option
VCS will automatically replace all the old GCM files with the new VCS Global Cluster option files
Configuration and validation are still necessary to ensure proper cluster setup
Installing CommandCentral Availability 4.0
CommandCentral Availability cannot reside on the same server as the GCM master
CommandCentral Availability will be installed as a new product and won’t swap out any existing files

7. Additional resources…
PMMs:
VCS: Michelle Mol Kerby, Robin Gertsen
GCM: David Kwan
CC Availability: David Kwan
WW Sales Ops:
Solaris Release Train: Gowri Grewal
CommandCentral Release Train: Ryan Foster
Windows Release Train: Shawna Meyer