Edge backup turns into Full version

Ignition
1

Has anyone seen in issue where an edge backup(fully licensed) restoring onto another edge device, and the install turns into the full version. This is on an Opto22 Epic device, and I don't know how to force it BACK to edge..

2

There's a setting in ignition.conf for the "edition". See it it has been altered from what was in the backup.

Also, note that licenses (and modules) are not part of gateway backups.

4

I don't have access to a file structure. Its an Epic device from Opto 22

5

Get the ssh key so you can access the file structure.

6

Thats a lot of effort for a version that shouldn't even change...

7

Look inside the .gwbk you have, and a new .gwbk you collect from the Edge -> Standard device.
Compare/contrast.

Look in the logs (ideally, the wrapper.log) if the Edge -> Standard device to see if the restore even took effect or if it was ignored.

8

how do i look inside the gwbk file. If I try its garbled info

9

If the restore didn't take effect, why would it change its version?

10

Using SSH is a lot of effort? PuTTY and WinSCP are free and easy to use. Numerous management tasks, particularly emergency tasks, require filesystem access on the gateway.

But it did, so it requires intervention. :man_shrugging:

It is a ZIP file. A certain stupid OS only looks at file extensions to locate an app to use, where more intelligent OS's look at a bit of the content. If you are using a stupid OS, rename the file to include .zip at the end.

1 Like
11

My first point, yes, if the way your network is setup makes it to not work...

12

Perhaps you should fix that, too.

13

This is in the .conf file
wrapper.java.additional.7=-Dedition=edge

14

I don't run my IT department. I wish i could

15

I don't see the problem. Get your IT department to handle these tasks if they won't let you do them.

16

I truly appreciate your help in these forums, but i don't understand how this thread is helping me solve my issue?

17

Your issue has exposed a flaw in Ignition's restore process that appears to have yielded an improper state. Filesystem access is the right tool to fix it. Your IT department is somehow blocking this. Ergo, it is their problem to fix. I'm encouraging you to involve the necessary resources.

18

Which conf file?
Compare the one you're attempting to restore to a new one you obtain from the system that ended up standard edition.

If it didn't, then my theory is that the target gateway was never Edge.

I'm grasping at straws, because I'm just throwing out possible theories.

You may want to contact our support department officially at this point, for a live troubleshooting session.

2 Likes
19

That was in the ignition.conf inside the gwbk folder

20

In the backupinfo.xml file inside the gwbk folder is:

<?xml version="1.0" encoding="UTF-8"?>
<gateway-backup>
	<version>8.1.21.2022092908</version>
	<timestamp>2025-06-30 21:51:03</timestamp>
	<backup-type>DATA_ONLY</backup-type>
	<ts>1751320263918</ts>
	<edition>edge</edition>
</gateway-backup>
21

Can you upload your full ignition.conf file? I think another instance of this came up in support not too long ago and it was being caused by the edge parameter being overridden.

Edit:
I found the previous report and it can be encountered if the parameters are numbered out of order in the .conf file. Then during restore or upgrade there are some required params being added that could use the same number as a previous parameter which introduces the override. A ticket was put in to account for the parameters being out of order but it hasn't been implemented yet.

2 Likes