VCS-256 Administration of Veritas InfoScale Availability 7.1 for UNIX/Linux Questions and Answers

VCS automatically rejects all hastop commands when the cluster configuration is open.

VCS is stopped and any configuration changes made since the cluster configuration was saved are lost.

VCS automatically writes the in-memory cluster configuration to the main.cf file then stops HAD.

VCS prompts the administrator to save the configuration when stopping HAD on all cluster nodes.

only one

one for each ServiceGroup

one for each node

two resources (one for SMTP, one for SNMP)

hastop

hastop -all

hastop –all -force

hastop –all -freeze

All nodes remain in regular GAB membership, but are also in jeopardy membership.

The cluster is in a split-brain condition until at least one other LLT link is working.

The fencing race is initiated and service groups are failed over the winning nodes.

Service groups are unable to failover when resource faults occur, but can failover if a system fault occurs.

vSphereDisk agent and Application HA

Veritas High Availability Plug-In and VMwareDisks agent

Dynamic Multi-Pathing and Veritas InfoScale Operations Manager

Cluster Management Console and Enterprise Administrator

The cluster was started first on the node where the changes were made.

The haconf –save command needs to be run after making the manual changes.

The cluster was started first on a node other than the one where the changes were made.

The haconf –dump command needs to be run prior to starting the cluster.

hares –refreshinfo Log02_Mount -sys server101

hares –modify Log02_Mount Enabled 1

hares –probe Log02_Mount –sys server101

hares –action Log02_Mount ProbeReTry

parallel

global

local

remote

Phantom

Proxy

VolumeSet

RemoteGroup