What is AutoDisable and how did the service groups become that way?

book

Article ID: 100018634

calendar_today

Updated On:

Resolution

When VCS does not know the status of a service group on a particular system, it autodisables the service group on that system. This functionality exists to increase the protection of the data when VCS does not completely know the states of the resources. It can be argued that the changes are on the conservative side, but when large amounts of critical data are being controlled by VCS, erring on the side of caution is wise.

Autodisabling occurs under the following conditions:

When the VCS engine, HAD, is not running on the system.
When all resources within the service group are not probed on the system.
When a particular system is visible through disk heartbeat only.

Under these conditions, all service groups that include the system in their SystemList attribute are autodisabled. This does not apply to systems that are powered off.

Using the command "hagrp -autoenable -sys " will clear the auto-disable flag for the listed system. Important note: The system name that should be used is that of the system which caused the auto-disable state. For instance, if there is a service group called "A" running on node 1 and it has nodes 2 and 3 in its system list, and node 3 is not running VCS for an upgrade, the command would be "hagrp -autoenable A -sys 3" to clear the autodisable. The other option is to remove the affected system from the service group's system list. To achieve this, use "hagrp -modify SystemList -delete ". For the above example, to change the system list for group A to remove node 3, the command would be "hagrp -modify A SystemList -delete 3", where node 1 has a priority of 0 and node 2 has a priority of 1.

Caution: To bring a group online manually after VCS has autodisabled the group, make sure that the group is not fully or partially active on any system that has the AutoDisabled attribute set to 1 by VCS. Specifically, verify that all resources that may be corrupted by being active on multiple systems are brought down on the designated systems. Then, clear the AutoDisabled attribute for each system