Veritas Storage Foundation Release Notes

66
Storage Foundation Release Notes
Known issues
■
■
Upgrade the hosts running Storage Foundation 5.1 to Storage Foundation
5.1SP1 or later and re-run the vradmin verifydata command.
Follow the offline verification procedure in the "Verifying the data on the
Secondary" section of the Veritas Storage Foundation and High Availability
Solutions Replication Administrator's Guide. This process requires ensuring
that the secondary is up-to-date, pausing replication, and running the vradmin
syncrvg command with the -verify option.
Replication hang when VVR logowner is on CVM slave node
(2405943)
When VVR is used for asynchronous replication in shared disk group environment,
one of the nodes of the cluster at the primary site is chosen as the logowner. When
the logowner node is on a node which is a slave node for the underlying CVM
cluster, in the presence of heavy I/O from a node that is not the logowner, it is
possible to get into a replication hang. This is due to an internal defect which will
be fixed in later releases.
Workaround: Enable the PreOnline trigger of the RVGLogOwner agent so that
the VVR logowner will always reside on the CVM master node. For the detailed
procedure, refer to the RVGLogowner agent notes section in the Veritas Cluster
Server Bundled Agents Reference Guide.
Cannot relayout data volumes in an RVG from concat to
striped-mirror (2162537)
This issue occurs when you try a relayout operation on a data volume which is
associated to an RVG, and the target layout is a striped-mirror.
Workaround:
To relayout a data volume in an RVG from concat to striped-mirror
1 Pause or stop the applications.
2 Wait for the RLINKs to be up to date. Enter the following:
# vxrlink -g diskgroup status rlink
3 Stop the affected RVG. Enter the following:
# vxrvg -g diskgroup stop rvg
4 Disassociate the volumes from the RVG. Enter the following:
# vxvol -g diskgroup dis vol