Hey folks,
Curious what strategies you all use to manage gateway backups across dev, test, and prod environments tool.
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
You may know already, this can help with you backup.
Gateway can backup itself with sheduled backup settings.
I do automatic backups of my gateway every week. Your needs may be others.
Cheers.
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
