17.08.2015 Views

Veritas Storage Foundation and High Availability Solutions Release Notes

Veritas Storage Foundation™ and High ... - SORT - Symantec

Veritas Storage Foundation™ and High ... - SORT - Symantec

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

About <strong>Veritas</strong> <strong>Storage</strong> <strong>Foundation</strong> <strong>and</strong> <strong>High</strong> <strong>Availability</strong> <strong>Solutions</strong>Known issues69vradmin syncvol comm<strong>and</strong> compatibility with IPv6 addresses (2075307)The vradmin syncvol comm<strong>and</strong> does not work with the compressed form of IPv6addresses if the target disk group <strong>and</strong> volume names are not specified.Workaround:In IPv6 environments, if you run the vradmin syncvol comm<strong>and</strong> <strong>and</strong> identifythe target host using the compressed form of the IPv6 address, then you also needto specify the target disk group <strong>and</strong> volume names.RVGPrimary agent operation to start replication between the originalPrimary <strong>and</strong> the bunker fails during failback (2054804)The RVGPrimary agent initiated operation to start replication between the originalPrimary <strong>and</strong> the bunker fails during failback – when migrating back to the originalPrimary after disaster recovery – with the error message:VxVM VVR vxrlink ERROR V-5-1-5282 Error getting information fromremote host. Internal Error.The issue applies to global clustering with a bunker configuration, where thebunker replication is configured using storage protocol. It occurs when the Primarycomes back even before the bunker disk group is imported on the bunker host toinitialize the bunker replay by the RVGPrimary agent in the Secondary cluster.Workaround:To resolve this issue1 Before failback, make sure that bunker replay is either completed or aborted.2 After failback, deport <strong>and</strong> import the bunker disk group on the originalPrimary.3 Try the start replication operation from outside of VCS control.Bunker replay did not occur when the Application Service Group wasconfigured on some of the systems in the Primary cluster, <strong>and</strong>ClusterFailoverPolicy is set to "AUTO" (2047724)The time that it takes for a global cluster to fail over an application service groupcan sometimes be smaller than the time that it takes for VVR to detect theconfiguration change associated with the primary fault. This can occur in abunkered, globally clustered configuration when the value of theClusterFailoverPolicy attribute is Auto <strong>and</strong> the AppGroup is configured on asubset of nodes of the primary cluster.This causes the RVGPrimary online at the failover site to fail. The followingmessages appear in the VCS engine log:

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!