A private fix is available which allows the VVR heartbeat timeout to be tuned using the vxtune command.  The default value remains 15 seconds, accepted values are between 1 and 60 seconds.

Example command:

> vxtune hb_timeout

The consequences of changing the heartbeat timeout are:

1. In the event of a disaster on the Primary, the Secondary Rlink will not disconnect until the timeout is completed.  VVR does not allow a takeover until the Rlink has disconnected so an increased value will lead to a longer period before a takeover can occur. 
2. VVR has a "blackout period" following an Rlink disconnect where it will not attempt to reconnect the Rlink.  This period is the heartbeat timeout +  2 seconds.  Therefore, increasing the timeout will also increase the blackout period.

To obtain the private fix, contact Veritas Enterprise Technical Support and reference this article during the call. A support representative will be available to assist in troubleshooting this issue. If it is determined that the private fix addresses the problem the support representative will further assist in obtaining the private fix.

Note: This fix specifically addresses the problem identified above. It has not been fully tested and should be applied in a test environment before placing into production. If the systems are not critically impaired, it is recommended to delay the installation of this private fix until the next scheduled maintenance release. Before applying this private fix, systems may be required to be upgraded to the latest code base. The support representative will help in determining the best course of action

File versions:

Filename	Version
vvrcli_msgs.dll	5.1.10047.584
vxio.sys	5.1.10047.584
vxtune.exe	5.1.10047.584

 

 

 

The Volume Replicator (VVR) heartbeat timeout is the amount of time VVR will wait for a heartbeat acknowledgement before declaring that the Replication Link (Rlink) is down and initiating a disconnect. In Storage Foundation for Windows, this is fixed at 15 seconds. If the VVR heartbeat is not received within this time then VVR will disconnect and reconnect the Rlink. Regular Rlink disconnect and reconnect operations can heavily impact replication performance.

ETrack: 2181955