09-06-2015 11:02 PM
hi,
i have a geographic cluster made from cluster a and cluster b.in cluster a i have also an orac runing on 2 nodes.if orac in cluser a fails than automatically it is started on cluster b?
if cluster a fails then automatically all the services are sarted on cluster b?
tnx a lot.
Solved! Go to Solution.
09-07-2015 09:21 PM
Hi,
It depends on the configuration. On the service group there is a attribute that controls it. I generally never set it to Auto.
ClusterFailOverPolicy (user-defined)
Determines how a global service group behaves when a cluster faults or when a global group faults. The attribute can take the following values:
Manual - The group does not fail over to another cluster automatically.
Auto - The group fails over to another cluster automatically if it is unable to fail over within the local cluster, or if the entire cluster faults.
Connected - The group fails over automatically to another cluster only if it is unable to fail over within the local cluster.
Type and dimension: string-scalar
Default: Manual
09-09-2015 05:12 AM
Hi Tanislav,
ClusterFailOverPolicy attribute is decisive while failing-over ServiceGroups across clusters in case of Cluster fault. In case of ServiceGroups’ fault also, if it can’t failover within cluster, then it will failover across cluster(depending upon ClusterFailOverPolicy).
Snippet from Admin guide
ClusterFailOverPolicy
Determines how a global service group behaves when a cluster faults or when a global group faults. The attribute can take the following values:
Manual : The group does not fail over to another cluster automatically.
Auto : The group fails over to another cluster automatically if it is unable to fail over within the local cluster, or if the entire cluster faults.
Connected : The group fails over automatically to another cluster only if it is unable to fail over within the local cluster.
Type and dimension: string-scalar
Default: Manual
But, there are few things to be considered…
1. While updating ClusterFailOverPolicy, update it on both clusters. As 2 clusters are kind of independent, VCS doesn’t synchronize value of ClusterFailOverPolicy. Mismatch in ClusterFailOverPolicy’s value across clusters may give inconsistent behavior.
2. Only global ServiceGroups will be failedover across clusters. Correctly update ClusterList across clusters.
3. If there are dependencies involved, please consult with Symantec TechSupport for recommended ClusterFailOverPolicy. You may also share configuration with us.
4. Only in case of cluster fault, ServiceGroups are failedover across cluster. System shutdown is not treated as fault and SGs won’t failover.
You can also refer to this thread: https://www-secure.symantec.com/connect/forums/fault-primary-node-global-cluster-0
Thanks & Regards,
Sunil Y
09-07-2015 09:21 PM
Hi,
It depends on the configuration. On the service group there is a attribute that controls it. I generally never set it to Auto.
ClusterFailOverPolicy (user-defined)
Determines how a global service group behaves when a cluster faults or when a global group faults. The attribute can take the following values:
Manual - The group does not fail over to another cluster automatically.
Auto - The group fails over to another cluster automatically if it is unable to fail over within the local cluster, or if the entire cluster faults.
Connected - The group fails over automatically to another cluster only if it is unable to fail over within the local cluster.
Type and dimension: string-scalar
Default: Manual
09-09-2015 05:12 AM
Hi Tanislav,
ClusterFailOverPolicy attribute is decisive while failing-over ServiceGroups across clusters in case of Cluster fault. In case of ServiceGroups’ fault also, if it can’t failover within cluster, then it will failover across cluster(depending upon ClusterFailOverPolicy).
Snippet from Admin guide
ClusterFailOverPolicy
Determines how a global service group behaves when a cluster faults or when a global group faults. The attribute can take the following values:
Manual : The group does not fail over to another cluster automatically.
Auto : The group fails over to another cluster automatically if it is unable to fail over within the local cluster, or if the entire cluster faults.
Connected : The group fails over automatically to another cluster only if it is unable to fail over within the local cluster.
Type and dimension: string-scalar
Default: Manual
But, there are few things to be considered…
1. While updating ClusterFailOverPolicy, update it on both clusters. As 2 clusters are kind of independent, VCS doesn’t synchronize value of ClusterFailOverPolicy. Mismatch in ClusterFailOverPolicy’s value across clusters may give inconsistent behavior.
2. Only global ServiceGroups will be failedover across clusters. Correctly update ClusterList across clusters.
3. If there are dependencies involved, please consult with Symantec TechSupport for recommended ClusterFailOverPolicy. You may also share configuration with us.
4. Only in case of cluster fault, ServiceGroups are failedover across cluster. System shutdown is not treated as fault and SGs won’t failover.
You can also refer to this thread: https://www-secure.symantec.com/connect/forums/fault-primary-node-global-cluster-0
Thanks & Regards,
Sunil Y
09-09-2015 09:49 PM
hi,
tnx so much and i like to close this but i do not have this option.
09-10-2015 02:44 AM
Looks like you have created 2 user profiles “tanislavm” and “tanislav”. Solution can be marked only by the user, who has started it. This particular discussion is started by “tanislav” and you might be trying to mark solution as “tanislavm” user. Please try with “tanislav” user.
Thanks & Regards,
Sunil Y