[FR] ensure restore of backups only works in correct enviroments

[matmair]

Please verify that this feature request has NOT been suggested before.

• I checked and didn't find a similar feature request

Problem statement

User might restore backups in too old environments. This can cause unreliability and data loss

Suggested solution

Use Archmonger/django-dbbackup#663 once it is merged and released to enrich backup metadata with data around api and software version as well as plugin state

Describe alternatives you've considered

Write docs

Examples of other systems

No response

Do you want to develop this?

• I want to develop this.

[SchrodingersGat]

Is there scope here for performing backup / restore of plugin tables? This is a current blocker for extracting data from setups with custom DB tables

[matmair]

@SchrodingersGat not really with this mechanism but we can certainly look into it.

Have you ever checked if the plugin model data is included in backups? Maybe it is just a question of ensuring plugins are loaded during backup/restore - which would be nice and easy to do, compared to anything else that I can imagine being the issue.

[SchrodingersGat]

I think we just have to ensure that the correct plugins are enabled before updating.

So we may need to ensure that the data is re-imported in a correct sequence:

1. Run InvenTree table migrations
2. Import core InvenTree data
3. Load plugin configs (to ensure the plugins are enabled to allow generation of tables)
4. Re-run migrations (to create the plugin tables)
5. Import plugin data from the backup

[matmair]

sounds reasonable; can we shift that to another issue?

[SchrodingersGat]

If you would like to scope it do a different issue, that's fine :)