Volume Replicator 5.0 Release Notes - Storage Foundation ...

Veritas Volume Replicator Release Notes 19Known issuesSRL issuesTakeover issuesSRL overflow (152276)If the SRL overflows on the Primary, any IBC message that exists on the PrimarySRL is dropped and therefore not delivered to the Secondary.Secondary SRL failure during IBC could cause pending writes to be lost(541265)When an IBC suspends writes to the Secondary data volumes, the writes arestored in the Secondary SRL. These pending writes in the SRL could potentiallybe lost if all the mirrors of the SRL fail.Fast-failback synchronization after an SRL failure on the original Primarymay cause data corruption on the new Secondary (284372)After a takeover if fast-failback synchronization is performed and the newSecondary, which was the original Primary, has recovered from an SRL failure,the synchronization may not synchronize the updates that were lost because ofSRL failure. This results in data corruption on the new Secondary. To recover,synchronize the Secondary completely.Secondary hangs while taking over as failback Primary after receivingin-flight updates from a bunker (598288)If the bunker SRL write latency is comparable with the Primary SRL writelatency, it is possible for the bunker to be ahead of the Primary in terms of thedata logged. Such data termed as "in-flight writes" is logged on the Secondarywhen the Secondary is synchronized using the bunker after a Primary crash.If such a Secondary which has logged in-flight data writes is promoted tofailback Primary, the logged writes are flushed to its data volumes. However,because of uninitialized log end pointers, this can sometimes result in VxVMhanging on this Secondary node.Issues related to replication in a shared environmentSecondary checkpoint problem (607703)In rare situations, when lots of Secondary checkpoints have been created and deleted, VVR can panic when you run the vxrlink cplist command.Using verifydata command with the cachesize attribute (615728)The following situation may occur when you use the vradmin verifydatacommand with the cachesize attribute while there is I/O on the Primary. If