Replication V2 and network timeout

Question

We are replicating between two NS40 units (5.6.39) , recently we had a network issue that disrupted replication for about 12 hours ..as soon as the link came back online i was going to login to the control station and figure out how to restart replication (no experience with V2 yet ). To my surprise replication status was OK ..like it restarted on its own. When i checked it earlier it had a yellow bang ..and status said 'network communication problem'. So does replicator have a timeout before it times out replication ? Thanks

Rainer_EMC · Accepted Answer

works as designedUnless the network outage is so long that your savvol gets full and cant be auto-extended so that the internal checkpoints holding a common base get inactive it will automatically recover.You only need to restart if it cant do an incremental copy any longer for this reasonI believe it retries at at least at each max_time_out_of_sync intervalWelcome to Replicator V2 RainerP.S.: Did you notice that failovers are much faster now ?

dynamox · Answer

have not had a chance to play with failover, two NS40s were setup by GE (integrated solution) and now it has been tossed over the wall ...here ..support it . Time to read V2 manual, thanks for your help.

dynamox · Answer

GE PACS indeed, EMC PS guy set it up using special scripts and turned it over to GE, hence no play time for me.

Rainer_EMC · Answer

have funIf its a GE PACS solution with a standalone CIFS server just be carefull and not play around with the preconfigured local users there.It is setup in a special way to statically map a few local Windows users to Unix users, which is normally not possible with standalone CIFS serversAlso read the manual carefully to understand the difference between failover, switchover and reverse

Celerra

Was this post helpful?