Error Message

VCS ERROR V-16-10150
Group <group_name> cannot be frozen when it is transitioning in a cluster

This error will only be seen with a Campus Cluster or Global Cluster that is utilizing Veritas Volume Replicator (VVR). This error is ideally seen in scenarios when a transition (failover) is occurring. However, this article is for scenarios when there is no transition happening, making this a false error.

This can occur in rare scenarios when the in-memory configuration of the cluster believes there is a pending transition occurring, even when it is not.

To resolve this issue, the false information needs to be cleared, so the cluster refreshes the status of the Service Groups (SG). This will allow the Freeze operation to complete successfully.
 

Let us assume a configuration wherein the Production (PROD) site is a 2 node cluster while the Disaster Recovery (DR) site is a single node cluster.

We will assume the above configuration as the steps are slightly different when it comes to a single-node cluster compared to a cluster with 2 or more nodes.

______________________________________

Note: The below steps will not cause a cluster outage (i.e. using the -force operation when stopping High Availability Engine (HAD))

______________________________________

Steps for PROD Site:

1. Open a Command Prompt > Run as Administrator
    
2. Run the following commands:

• haconf -dump -makero

If this returns an error: VCS WARNING v-15-1-10367 Cluster not writeable. This can be ignored.

This command is to simply ensure the in-memory cluster configuration is dumped to disk to ensure if there are any pending cluster changes in memory, they are not lost when stopping HAD.
 

• hastop -all -force
   
• hastart -all
   
• hasys -state (Run this command until both local nodes show the status of ‘Running’)

Look for the nodes that show localclus with the Value reporting as ‘Running’ 

Here is an example of the results from a 2-node cluster:

3. Once confirmed, the in-memory should be flushed. 

Steps for DR Site:
In this example, it can be observed that the -all option will not be used because there is only one node in the cluster.

1. Open a Command Prompt > Run as Administrator
    
2. Run the following commands:

• haconf -dump -makero

​​​​​​If this returns an error: VCS WARNING v-15-1-10367 Cluster not writeable. This can be ignored.

This command is to simply ensure the in-memory cluster configuration is dumped to disk to ensure if there are any pending cluster changes in memory, they are not lost when stopping HAD.

• hastop -local -force
   
• hastart
   
• hasys -state (Run this command until the local node returns ‘Running)

Look for the node that shows localclus with the Value reporting as ‘Running’ 

Here is an example of a single-node cluster on the DR side:

Once all above steps have been completed, the Freeze operation should now be successful.