Vision Project Import - best practice

Ignition
1

Vision 8.1.32

I believe the plant inadvertently exported some resources that overwrote like named windows/ templates across projects. I was able to restore some specific windows from an older backup I had while the plant contacted IT to get a restore of the server backup. In that time, another integrator made some project and gateway changes that I don't want to lose.

So, I restored the server backup onto a VM, did a gateway restore, and exported the projects that were affected.

My plan is to import those today.

What is the best method. What happens to the actively running clients during the restore.

My plan was to rename each affected project incase the new imports go haywire, import the backed up projects, and then once everything looks correct, delete the backups.

I guess my question is what happens to the clients when I rename the project in the gateway before importing the backups? Should I stop the gateway before doing this and terminate all clients?

2

I don't think I'd rename projects. Too much risk of breaking things. I'd personally rebuild everything on an offline server to get it where it needs to be, then export all the resources (or just affected ones if you know which ones) and import/overwrite the ones on the project. That way your clients just get an update notification and you're done.

3 Likes
3

I was only going to rename the suspect projects to preserve them as backups, but import the new ones with the same names as prior.. I guess I can export them also and have them available.

4

If the projects have gateway events, a duplicate will run extra copies. Not recommended.