Hi I've a query which need clarification request someone to assist please.
An source application is writing C-Clips to Centera source pool PoolA which is replicating to Target Centera pool PoolA.
What happen when an application at target site writing C-Clips to same pool PoolA at target location, do they replicate back to Source PoolA or not? Both source and target node are using CenteraStar 4.1 Version
I understand Centera support bidirectional replication. my question is we have enterprise vault application EV-pool at Site A which is replicating to Site B for DR purposes. we also have enterprise vault application at Site B writing clip to same EV-pool at Site B. now do they replicate back to site A EV-pool?
I've checked configuration of source replication details and target replication and I can see both side replication is configured
Source
Replication Enabled: Wednesday, 3 August 2005 15:13:18 BST Replication Paused: no Replication Address: 10.117.226.240:3218,10.117.226.241:3218 Failover Address: 10.117.226.240:3218,10.117.226.241:3218 Replicate Delete: yes Replicate incoming replicated Objects: no Replicated Pools: EV-Pool,
Profile Name: replication
Target
Replication Enabled: Tuesday, 8 June 2010 03:33:44 BST
Given that configuration info and the lack of errors or warnings it is very likely your content is being replicated to both Centeras. So the real question becomes 'why are my system clip counts not the same?'. EMC service may be able to provide some insight on this.
Also, my company Interlock Technology (www.interlock-tech.com) has extensive Centera/EV experience and we would be able to offer you an assessment service to confirm that all of your EV content is correctly protected.
mfh2
1 Rookie
•
208 Posts
576
0
Posted August 12th, 2014 07:00
Hello Kishore -
Centera supports bidirectional replication which, if configured, would replicate new clips from the target back to the source.
If you need this behavior you should check to see that the target is configured to replicate back to the source.
Good Luck,
Mike Horgan