Veritas Cluster Server Release Notes

Veritas Cluster Server Release Notes
Software limitations
82
is in a leaving state and then removes the lock file. The agent’s monitor function
declares that the resource is offline. After the node restarts, the disk group site still
remains detached.
Workaround:
You must take the fire drill service group offline using the hagrp -offline command
before you shut down the node or before you stop VCS locally.
If the node has restarted, you must manually reattach the fire drill site to the disk
group that is imported at the primary site.
If the secondary node has crashed or restarted, you must manually reattach the
fire drill site to the target disk group that is imported at the primary site using the
following command: /opt/VRTSvcs/bin/hares -action $targetres joindg
-actionargs $fdsitename $is_fenced -sys $targetsys.
Limitations with DiskGroupSnap agent [1919329]
The DiskGroupSnap agent has the following limitations:
■
■
The DiskGroupSnap agent does not support layered volumes.
If you use the Bronze configuration for the DiskGroupSnap resource, you could
end up with inconsistent data at the secondary site in the following cases:
■
■
After the fire drill service group is brought online, a disaster occurs at the
primary site during the fire drill.
After the fire drill service group is taken offline, a disaster occurs at the
primary while the disks at the secondary are resynchronizing.
Symantec recommends that you use the Gold configuration for the
DiskGroupSnap resource.
System reboot after panic
If the VCS kernel module issues a system panic, a system reboot is required
[293447]. The supported Linux kernels do not automatically halt (CPU) processing.
Set the Linux “panic” kernel parameter to a value other than zero to forcibly reboot
the system. Append the following two lines at the end of the /etc/sysctl.conf
file:
# force a reboot after 60 seconds
kernel.panic = 60