# Same Gateway, different Server - DRV table entry?

**URL:** <https://forum.inductiveautomation.com/t/same-gateway-different-server-drv-table-entry/99534>\
**Category:** Ignition\
**Created:** [December 6, 2024, 4:28pm UTC](https://forum.inductiveautomation.com/t/same-gateway-different-server-drv-table-entry/99534 "2024-12-06T16:28:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![justin.huggins](https://avatars.discourse-cdn.com/v4/letter/j/d07c76/32.png) [@justin.huggins](https://forum.inductiveautomation.com/u/justin.huggins)\
**Post date:** [December 6, 2024, 4:28pm UTC](https://forum.inductiveautomation.com/t/same-gateway-different-server-drv-table-entry/99534/1 "2024-12-06T16:28:30Z")

</div>

We are currently going to a new OS for our Windows Server. Our process is building out a brand new gateway on the new server and once ready, we are going to power down the old server then power up the server. We have pulled the backup from the original and placed on the new gateway. My question is, will this create a new entry in the dbo.sqlth\_drv table? If so, is there a way to prevent this? For example, our history is hitting dbo.sqlth\_11\_data, I do not want this to change once standing up the new gateway. Will Ignition just comb the DRV table and see that the name and providers already exist and will just use the existing entry in the DRV table?

In addition, we use redundancy on all of our gateways. Can we allow the backup to stay live for end users while powering down the original and powering up the new gateway without causing any issues?

---

<div class="post-metadata">

**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:** [December 7, 2024, 12:28am UTC](https://forum.inductiveautomation.com/t/same-gateway-different-server-drv-table-entry/99534/2 "2024-12-07T00:28:21Z")

</div>

Something to study:

> [@Migration Historical Data](https://forum.inductiveautomation.com/t/migration-historical-data/71479):
>
> I have a Ignition setup, which uses only one database connection. Historical data tables per month have more than 200 billion rows and size more than 50GB each one. How to correctly transfer historical data tables to another database without lost data? I would like to know the correct sequence of actions. Please help.

---

<div class="post-metadata">

**Author:** ![Chris\_Bingham](https://avatars.discourse-cdn.com/v4/letter/c/e5b9ba/32.png) [@Chris\_Bingham](https://forum.inductiveautomation.com/u/Chris_Bingham)\
**Post date:** [December 7, 2024, 5:04pm UTC](https://forum.inductiveautomation.com/t/same-gateway-different-server-drv-table-entry/99534/3 "2024-12-07T17:04:33Z")

</div>

> [@justin.huggins](#):
>
> Can we allow the backup to stay live for end users while powering down the original

This is certainly the expected behavior, but lots of variables might prove otherwise. Should be easy to test...Connect as a client would, confirm no issues. Go to gateway config of the master and (if redundancy is active, no errors) then Force Failover. Verify everything continues to work as expected from your clent. If any issues arise, failover back to Master. Otherwise, should be able to perform all necessary maintenance on Master while Backup is the Active gateway.

[https://support.inductiveautomation.com/hc/en-us/articles/360047136192-Upgrading-or-Patching-a-Redundant-Ignition-Pair](https://support.inductiveautomation.com/hc/en-us/articles/360047136192-Upgrading-or-Patching-a-Redundant-Ignition-Pair)