# Move backup from TEST to PROD in 8.3 **URL:** \ **Category:** Ignition\ **Tags:** ignition83\ **Created:** [September 29, 2026, 4:51pm UTC](https://forum.inductiveautomation.com/t/move-backup-from-test-to-prod-in-8-3/117248 "2026-09-29T16:51:34Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\ **Post date:** [September 29, 2026, 4:51pm UTC](https://forum.inductiveautomation.com/t/move-backup-from-test-to-prod-in-8-3/117248/1 "2026-09-29T16:51:34Z")
I have 2 env TEST and PROD. In TEST env: 2 redundant gateway and another gateway connected with GAN, and a DB In PROD env: 2 redundant gateway and another gateway connected with GAN, and a DB IP addresse are different in both env. OPCUA client are différent and some change on devices. **I would like to update PROD with gateway backups from TEST and a restore operation.** Is this a possibility in **8.3** , or do we have to wait for the **2027** version, which will include partial backup and restore? - TEST gateway have less memory than PROD gateway. ignition.conf is different. - Redundancy settings are different (master node address) redundancy.xml file is preserved ? - Gateway network for redundancy or for other gateway communication trusted cert are not the same ? - opcua client connection trusted cert are not the same ? With **gateway mode ENV = TEST or PROD** I can manage DB for example connection change but is it possible to use this for other settings ? Do I have to copy some data from PROD env to TEST env and associate them to env mode PROD to be able to restore a TEST env gateway backup to PROD ? I'm looking for best practice to update PROD env without having to change lots of parameters each times... ---
**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\ **Post date:** [September 29, 2026, 6:11pm UTC](https://forum.inductiveautomation.com/t/move-backup-from-test-to-prod-in-8-3/117248/2 "2026-09-29T18:11:47Z")
I wouldn't advise the backup/restore route, but this can be pretty easily managed today by making use of VCS. You'll need to trigger a config scan on the PROD Gateways after the placement of the resources in question, but you can get where you're trying to go today without waiting for the partial import/export feature in `2027`. ---
**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\ **Post date:** [October 3, 2026, 12:08pm UTC](https://forum.inductiveautomation.com/t/move-backup-from-test-to-prod-in-8-3/117248/3 "2026-10-03T12:08:22Z")
Ok, I see, Our **Ignition 8.3.9** gateways have no internet acces, VM (no docker) and the backup seemed like a good way to update PROD gateways from TEST gateways. When we want to restore a backup in PROD, I think that the issues are the Following files: - **ignition.conf** - **gateway.xml** for **redundancy.xml** , the doc mention: Notably, when restoring a Gateway backup on an existing Gateway, the following items are not changed or replaced by the backup: - Modules - License information/grants - **Redundancy settings** - Tag Reference Store Trusted cert are in the **data\config\local** , I think that restoring a backup doesn't change them ? @paul-griffith could confirm ? Other settings should be well managed with **deployement Mode**... But ignition.conf will receive the deployement Mode value of the TEST env ! * * * If I undestand correctly the other solution your mention is to copy: - **Ignition\data\config** from TEST gw to PROD gw (with settings according a deployement mode, for example core = PROD and TEST) - **Ignition\data\projects** from TEST gw to PROD gw (or project import) and do a **gateway scan** (and projects scan if necessary) ---
**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 3, 2026, 3:00pm UTC](https://forum.inductiveautomation.com/t/move-backup-from-test-to-prod-in-8-3/117248/4 "2026-10-03T15:00:15Z")
> [@mazeyrat](#): > > But ignition.conf will receive the deployement Mode You can have `ignition.conf` include a supplemental file that is **outside** the `data` folder, so it doesn't get included in any backup. Do this, with same name, in all environments. Have the deployment mode setting in this external file, and it won't be broken by a gateway restore. ---
**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\ **Post date:** [October 3, 2026, 4:37pm UTC](https://forum.inductiveautomation.com/t/move-backup-from-test-to-prod-in-8-3/117248/5 "2026-10-03T16:37:52Z")
Clever for ignition.conf 👍 I hope ignition would not try to modify the file on upgrade to adjust some settings I don't known if there are some solution for gateway.xml and if this file is always replaced when restoring a backup with the one in the gwbk.... ---
**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\ **Post date:** [October 7, 2026, 8:10pm UTC](https://forum.inductiveautomation.com/t/move-backup-from-test-to-prod-in-8-3/117248/6 "2026-10-07T20:10:54Z")
In my understanding, restoring a gateway backup is like: - unzip the gwbk - remove from the unzipped files **"local" folder and its subdirectories** - replace file in Ignition/data - restart gateway (or rescan gateway and rescan projets) **ignition.conf and gateway.xml should not be always replaced in a restore gateway backup operation ?** (redundancy.xml is ever not restored) or we should be able to **chose the action** for those files when we restore the backup on another gateway...it will be available in Ignition 2027 ! In 8.3, we have to run manually those operation ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [October 7, 2026, 10:17pm UTC](https://forum.inductiveautomation.com/t/move-backup-from-test-to-prod-in-8-3/117248/7 "2026-10-07T22:17:45Z")
`ignition.conf` and `gateway.xml` are always collected as part of the backup and always restored as part of the restoration. If you don't want them overridden, you could remove them from the backup, in theory. But it's very intentional that the simplest case of "take a gateway backup, restore it somewhere else" does its very best to recreate that exact same gateway state - `ignition.conf` included. The extra files/directory workaround Phil mentioned is described in more detail by Kevin C here: > [@Disable devices in Gateway Startup Script (v8.3.0)](https://forum.inductiveautomation.com/t/disable-devices-in-gateway-startup-script-v8-3-0/111599/6): > > Setting the deployment mode via an environment variable is not yet supported, you've got to supply the Java system property via a JVM argument, -Dignition.config.mode=yourdeploymentmode. As @paul-griffith mentions, we're going to be doing additional refinements in this area. However, I've got some guidance that might be useful in the meantime. Currently, at time of writing w/ 8.3.0, if you add the deployment mode arg explicitly to your data/ignition.conf, it will be within any gateway backup … Partial gateway backup/restore (using .gwex files) is indeed part of 2027.