Replication known issues

Last published : Sep 11, 2026
This section describes the replication known issues in this release of Arctera InfoScale Storage and Arctera InfoScale Enterprise.
Related information
Known issues
Upgrade causes disconnect between VVR primary and secondary on AIX (4116979)Switching the VVR logowner to another node causes the replication to pause (4114096)Secondary RVG creation using addsec command fails with a hostname not responding error (4113218)Syslog gets flooded with vxconfigd daemon V-5-1-15599 error messages (4115620)vradmind and vxcommands hang about 40 minutes after replication starts in CVR configurations (4050516)RVG goes into secondary log error state after secondary site reboot in CVR environments (4046182)Data corruption may occur if you perform a rolling upgrade of InfoScale Storage or InfoScale Enterprise from 7.3.1 or earlier to 7.4 or later during replication (3951527)vradmind may appear hung or may fail for the role migrate operation (3968642, 3968641)After the product upgrade on secondary site, replication may fail to resume with \"Secondary SRL missing\" errorvradmin repstatus command reports secondary host as \"unreachable\"(3896588)RVGPrimary agent operation to start replication between the original Primary and the bunker fails during failback (2036605)A snapshot volume created on the Secondary, containing a VxFS file system may not mount in read-write mode and performing a read-write mount of the VxFS file systems on the new Primary after a global clustering site failover may failIn an IPv6-only environment RVG, data volumes or SRL names cannot contain a colon (1672410, 1672417)vradmin functionality may not work after a master switch operationCannot relayout data volumes in an RVG from concat to striped-mirror (2129601)vradmin verifydata may report differences in a cross-endian environment (2834424)vradmin verifydata operation fails if the RVG contains a volume set (2808902)Bunker replay does not occur with volume sets (3329970)SmartIO does not support write-back caching mode for volumes configured for replication by Volume Replicator (3313920)During moderate to heavy I/O, the vradmin verifydata command may falsely report differences in data (3270067)While vradmin commands are running, vradmind may temporarily lose heartbeats (3347656, 3724338)Write I/Os on the primary logowner may take a long time to complete (2622536)DCM logs on a disassociated layered data volume results in configuration changes or CVM node reconfiguration issues (3582509)After performing a CVM master switch on the secondary node, both rlinks detach (3642855)The RVGPrimary agent may fail to bring the application service group online on the new Primary site because of a previous primary-elect operation not being run or not completing successfully (3761555, 2043831)A snapshot volume created on the Secondary, containing a VxFS file system may not mount in read-write mode and performing a read-write mount of the VxFS file systems on the new Primary after a global clustering site failover may fail (1558257)DCM plex becomes inaccessible and goes into DISABLED(SPARSE) state in case of node failure. (3931775)Initial autosync operation takes a long time to complete for data volumes larger than 3TB (3966713)