# Remote tag history provider vs. remote tag provider + local history provider **URL:** \ **Category:** Ignition\ **Tags:** ignition81, perspective\ **Created:** [June 10, 2024, 6:00pm UTC](https://forum.inductiveautomation.com/t/remote-tag-history-provider-vs-remote-tag-provider-local-history-provider/91638 "2024-06-10T18:00:39Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Bushmatic](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bushmatic/32/87014_2.png) [@Bushmatic](https://forum.inductiveautomation.com/u/Bushmatic)\ **Post date:** [June 10, 2024, 6:00pm UTC](https://forum.inductiveautomation.com/t/remote-tag-history-provider-vs-remote-tag-provider-local-history-provider/91638/1 "2024-06-10T18:00:39Z")
We're preparing to launch a second gateway (for Perspective / IT) that will be connected to our current OT gateway through a gateway network. This OT gateway's default tag provider holds all the tags that drive our shop floor operations and has tag history enabled. We plan on setting up the OT gateway as the "remote tag provider" for the incoming IT gateway, so we can read all the production tags without affecting normal operations. We want the tag historian to also move to the IT gateway. Regarding the tag historian, it sounds like we can do one of two things: 1. Set up a local tag history provider on the new **IT** gateway to historize the remotely-provided tags that are coming from the OT gateway. Or... 2. Set up a remote tag history provider on the **OT** gateway to historize the local OT tags using the store and forward system into the IT gateway. Do I have this right? Is one option recommended over the other -- for example, maybe one is more performant? It seems like option 1 will do better if our main goal is to reduce load in the OT gateway, but this is all new to me so I can't be certain. All guidance is appreciated. > **[Remote History Provider Video at Inductive University](https://inductiveuniversity.com/videos/remote-history-provider/8.1)** > > A remote History Provider uses the Gateway Network to grab a History Provider from another Gateway on the Gateway Network, allowing you to share historical data between connected Gateways. A remote History Provider works like a normal History... ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [June 10, 2024, 8:58pm UTC](https://forum.inductiveautomation.com/t/remote-tag-history-provider-vs-remote-tag-provider-local-history-provider/91638/2 "2024-06-10T20:58:00Z")
1. Use continuous DB replication from OT to IT outside Ignition, and configure the IT gateway to perform history queries with the replica. Do **not** do #1--remote tag providers do not pass tag changes that happen very quickly, and you likely will not get the same historical result. #2 is OK, but doesn't reduce load as much as #3. ---
**Author:** ![hventer23](https://avatars.discourse-cdn.com/v4/letter/h/bbce88/32.png) [@hventer23](https://forum.inductiveautomation.com/u/hventer23)\ **Post date:** [September 13, 2024, 1:21pm UTC](https://forum.inductiveautomation.com/t/remote-tag-history-provider-vs-remote-tag-provider-local-history-provider/91638/3 "2024-09-13T13:21:55Z")
@pturmel, apologies for tailgating the post but it is related to: > [@pturmel](#): > > Do **not** do #1--remote tag providers do not pass tag changes that happen very quickly, and you likely will not get the same historical result. We possibly have a project where we have 50 sites (each with 1k tags) and one central Ignition gateway where the historian will also reside. I was thinking of adding all the sites as remote tag providers to the central gateway (they have a strong VPN network across sites). Then create 50k reference tags on the central gateway and historize them on the central historian. This will allow us to only have one historian license. I am just concerned about the off chance that the VPN does go down. Will Ignition's gatway network S&F properly send historical data through to the central historian once the VPN is restored? ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [September 13, 2024, 1:48pm UTC](https://forum.inductiveautomation.com/t/remote-tag-history-provider-vs-remote-tag-provider-local-history-provider/91638/4 "2024-09-13T13:48:25Z")
Option #2 is probably what you want, possibly with a splitter if you want efficient local access to history, too. On the central gateway, you'll have a local history provider where all of the edge remote history providers send their content. Then, also on the central gateway, configure all of the remote tag providers that point at the edge gateways to use database mode for history (with the central gateway's central history database). S&F will work as you expect. ---
**Author:** ![m.cornet](https://avatars.discourse-cdn.com/v4/letter/m/b5e925/32.png) [@m.cornet](https://forum.inductiveautomation.com/u/m.cornet)\ **Post date:** [October 2, 2024, 1:11pm UTC](https://forum.inductiveautomation.com/t/remote-tag-history-provider-vs-remote-tag-provider-local-history-provider/91638/5 "2024-10-02T13:11:39Z")
I've configured a history splitter on my central gateway (Ignition Standard). All of the Edge Gateways use are syncing their history data within this remote history splitter. Then I've created the remote tag providers which point at the Edge Gateways. The issue is that, for some reason, the remote tag provider's history datasource can not point to the splitter. Only datasource history providers seem to appear in the list. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [October 2, 2024, 1:14pm UTC](https://forum.inductiveautomation.com/t/remote-tag-history-provider-vs-remote-tag-provider-local-history-provider/91638/6 "2024-10-02T13:14:45Z")
> [@m.cornet](#): > > history splitter on my central gateway (Ignition Standard) The history splitter should be in each Edge gateway.