Hub and Spoke Replication Failover

Hey all,

I have a customer who has standard A<-->B replication and they are looking at adding 3rd cluster creating a hub and spoke replication, so there would be A<-->B & A<-->C. once this is complete they want to retire cluster A.

I think they need to create new SyncIQ policies B<-->C and allow a complete resync, I would have preferred to use a cascaded policy but they are concerned with bandwidth.

Do the spokes have any type of consistency maintained by SyncIQ or are they completely oblivious to their existence?