# Best Practices for Managing Gateway Backup Versions Across Environments?

**URL:** <https://forum.inductiveautomation.com/t/best-practices-for-managing-gateway-backup-versions-across-environments/108640>\
**Category:** General Discussion\
**Created:** [July 17, 2025, 6:57pm UTC](https://forum.inductiveautomation.com/t/best-practices-for-managing-gateway-backup-versions-across-environments/108640 "2025-07-17T18:57:55Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ziddihoon228](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ziddihoon228/32/77822_2.png) [@ziddihoon228](https://forum.inductiveautomation.com/u/ziddihoon228)\
**Post date:** [July 17, 2025, 6:57pm UTC](https://forum.inductiveautomation.com/t/best-practices-for-managing-gateway-backup-versions-across-environments/108640/1 "2025-07-17T18:57:55Z")

</div>

Hey folks,

Curious what strategies you all use to manage gateway backups across dev, test, and prod environments [tool](https://calculadoradedias.com/sueldo/).

We’re currently saving backups manually with timestamped filenames, but it’s getting messy, and there’s some risk of restoring the wrong version.

Do you use a naming convention, Git-based backup systems, or automated scripts via GCU or CLI?

Would love to hear your workflow—or any tools or scripts you recommend.

Cheers,  
Jhonn Mick

---

<div class="post-metadata">

**Author:** ![Alejandro\_Alaco](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/alejandro_alaco/32/59849_2.png) [@Alejandro\_Alaco](https://forum.inductiveautomation.com/u/Alejandro_Alaco)\
**Post date:** [July 17, 2025, 7:31pm UTC](https://forum.inductiveautomation.com/t/best-practices-for-managing-gateway-backup-versions-across-environments/108640/2 "2025-07-17T19:31:25Z")

</div>

You may know already, this can help with you backup.

Gateway can backup itself with sheduled backup settings.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/3/a3133f30d5b41aac72fa197bfdeec5a881cd2cc1.png)  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/e/7eb0e9b9ec3eabc021fc1adcff17d07cc6f94c1b.png)

I do automatic backups of my gateway every week. Your needs may be others.

Cheers.

---

<div class="post-metadata">

**Author:** ![Spencer\_Lommel1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/spencer_lommel1/32/78679_2.png) [@Spencer\_Lommel1](https://forum.inductiveautomation.com/u/Spencer_Lommel1)\
**Post date:** [July 17, 2025, 8:15pm UTC](https://forum.inductiveautomation.com/t/best-practices-for-managing-gateway-backup-versions-across-environments/108640/3 "2025-07-17T20:15:59Z")

</div>

On each of our servers that host a gateway we mount a remote network drive that we save to similar to how @Alejandro_Alaco mentioned.

So each gateway gets saved to  
`/<remoteBackupServer>/<gatewayName>/<${gatewayName}_Ignition-backup-${edition}${timestamp}.gwbk>`

so if you had 2 different gateways both saving to the same remoteNetwork drive it would look like

/remote-server/gateway-1/  
and  
/remote-server/gateway-2/

This seems to be the most manageable because all your backups are in one central location but they're still in separate folders so it's easy to sort through them once you get a bunch of gateways =D