The following are the procedural highlights required to modify the existing VCS configuration on the primary site:
Configure two service groups:
Add the RVGSharedPri resource to the existing application database service group and define this group as a global group by setting the ClusterList and ClusterFailOverPolicy attributes.
Move the CVMVolDg resource from the existing application database service group to the newly created RVG group.
Note: |
The example procedure illustrates the configuration process using a manual file editing method. If you are using the Java Console, some steps do not apply in the same order. |
To modify VCS on the primary site
# haconf -dump -makero
# cd /etc/VRTSvcs/conf/config # cp main.cf main.orig
Add a failover service group using the appropriate values for your cluster and nodes. Include the following resources:
RVGLogowner resource. The node on which the group is online functions as the log owner (node connected to the second cluster for the purpose of replicating data).
IP resource
NIC resources
The following are examples of RVGLogowner service group for the different platforms.
group rlogowner ( SystemList = { galaxy = 0, nebula = 1 } AutoStartList = { galaxy,nebula } ) IP logowner_ip ( Device = bge0 Address = "10.10.9.101" NetMask = "255.255.255.0" )
NIC nic ( Device = bge0 NetworkType = ether NetworkHosts = "10.10.8.1" )
RVGLogowner logowner ( RVG = rac1_rvg DiskGroup = oradatadg ) requires group RVGgroup online local firm logowner requires logowner_ip logowner_ip requires nic
Example RVGgroup service group:
group RVGgroup ( SystemList = { galaxy = 0, nebula = 1 } Parallel = 1 AutoStartList = { galaxy,nebula } )
RVGShared racdata_rvg ( RVG = rac1_rvg DiskGroup = oradatadg ) CVMVolDg racdata_voldg ( CVMDiskGroup = oradatadg CVMActivation = sw ) requires group cvm online local firm racdata_rvg requires racdata_voldg
Modify the application service group using the appropriate values for your cluster and nodes:
Define the application service group as a global group by specifying the clusters on the primary and secondary sites as values for the ClusterList group attribute. See the attribute in bold in the example that follows.
Add the ClusterFailOverPolicy cluster attribute. Symantec recommends using the Manual value. See the attribute in bold in the example.
Add the RVGSharedPri resource to the group configuration.
Remove the CVMVolDg resource, if it has been configured in your previous configuration. This resource is now part of the RVG service group.
Specify the service group (online, local, firm) to depend on the RVG service group.
Remove the existing dependency of the Database service group on the CVM service group. Remove the line:
requires group CVM online local firm
Remove the existing dependency between the CFSMount for the database and the CVMVoldg for the application database. Remove the line:
oradata_mnt requires oradata_voldg
group database_grp ( SystemList = { galaxy = 0, nebula = 1 } ClusterList = { clus1 = 0, clus2 = 1 } Parallel = 1 ClusterFailOverPolicy = Manual Authority = 1 AutoStartList = { galaxy,nebula } OnlineRetryLimit = 3 TriggerResStateChange = 1 OnlineRetryInterval = 120 ) CFSMount oradata_mnt ( MountPoint = "/oradata" BlockDevice = "/dev/vx/dsk/oradatadg/rac1_vol" ) Process vxfend ( PathName = "/sbin/vxfend" Arguments = "-m sybase -k /tmp/vcmp_socket" ) RVGSharedPri ora_vvr_shpri ( RvgResourceName = racdata_rvg OnlineRetryLimit = 0 ) requires group RVGgroup online local firm oradata_mnt requires ora_vvr_shpri
# hacf -verify /etc/VRTSvcs/conf/config
# hastop -all -force
Wait for port h to stop on all nodes, and then restart VCS with the new configuration on all primary nodes:
# hastart