The Replication Monitor, in Veritas Enterprise Administrator (VEA), maintains a status of "activating" for replication. No blocks are being sent to the secondary site.
When replication is stuck in the "activating" state, it usually indicates that there is a network communication problem between the primay and secondary sites.
1. Use vxprint to determine that the Rlinks, hostnames and IP addresses for the primary and secondary replication partners match each other. Information on this can be found here: www.symantec.com/docs/TECH52571
2. Use pathping to test network connectivity between the primary and secondary sites. Pathping is a Microsoft utility that comes with Windows. More information on this utility is found here: technet.microsoft.com/en-us/library/ff963096(WS.10).aspx
Note: Test connectivity in both directions. Confirm that packets are being sent back and forth using the same route. If packets from the secondary take a different route to get to the primary, differences in timing problems may occur, causing the primary not to receive acknowledgements from the secondary in a timely manner.
3. Try to pause and then resume replication.
To pause replication:
4. Use vxrlink to detach and reattach the primary rlink from the primary site using the following syntax:
To detach the rlink:
vxrlink -g [disk group] -r [rvg] det [rlink]
To attach the rlink:
vxrlink -a -g [disk group] -r [rvg] att [rlink]
Note: The information required for these commands can be found using vxprint.