What is AutoDisabled flag and how does a service group enter this state?

book

Article ID: 100018634

calendar_today

Updated On:

Description

There can be instances wherein a Service Group status may show as AutoDisabled. This article describes the possible conditions that can trigger an AutoDisabled state for the Service Group (SG).

Cause

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.

SG can enter AutoDisable state when one or more of the following conditions are met:

When the VCS engine/HAD is not running on the system but the system is up and running.
When one or more resources within the service group are not probed on the system.
When the system being a part of the SystemList attribute is rebooted. The reboot process kills all processes, including HAD. When the VCS process is killed, other
systems in the cluster mark all service groups that can go online on the rebooted system as Autodisabled

Under these conditions, all service groups that include the system in their SystemList attribute are autodisabled.

Resolution

The AutoDisable flag can be cleared by either of the below approaches:

From the VCS Java console, by right clicking on the impacted SG and selecting Autoenable -> Impacted system

Using the command hagrp -autoenable -sys where sys is the server name for which the AutoDisable flag is set.