1 of 1 people found this helpful
You need to "fan" your data to both members of your collective by using buffering. If you are not buffering your data the data will not reach the secondary.
To move the tag you could use PIConfig, custom code, or even PI-to-PI. You also could be extreme and copy all the archives over.
Thank you for your reply. Yes buffering was set on the webserver, which is responsible for archiving the data on both primary and secondary collective which was working fine. But after sending this request noticed that there was an error in buffering after restart of PI buffer subsystem service the error went.
But now my concern is to replicate the data on secondary collective, I am not sure how will I be able to do that (as you mention To move the tag you could use PIConfig, custom code, or even PI-to-PI. You also could be extreme and copy all the archives over.) Could you give me some steps or any reference link to achieve this.