Ok, we we’ve finally migrated from Rocky Linux 8.5 to 9.5,
In the past copying the projects and clips folders was enough to get a system up and running, but with this postgres stuff i’m having troubles, how on earth do you do an easy mass move, i can see all the 2025.2.3 projects fine, but none of the 2026.1 projects.
not sure what to do, also i did move the /var/opt/Autodesk/projects folder as well
Any help on how to move the DB, or even if i have top would help.
sorry I’ll not be much help to you. I am an artist not IT.
I would say though that I have ALWAYS been told to archive a project and use that to migrate it to another machine. I am amazed to hear that you can move the Projects and Clips around and still have them function but as I mentioned I am not IT
Given the changes in 2026 I don’t think a migration can be accomplished at the file system level alone.
They need to run through the conversion. Not only because of the DB but also the OCIO transition.
There may be a path where on 2026.1 you make the old projects visible in the project management window and on open it will create a copy for you. Not in bulk, but faster than archive/restore.
In 2026 there is now stuff in /var/opt/Autodesk/ like (by default) your projects in flame/projects/ which you already found, and the database and its configs in pgsql/ – If you shut down PostgreSQL from the Service Monitor and then sync that whole directory across from your old system/HD to the new, you might have better luck.
Unfortuniatly i tried the full folder copy including the pgsql directory, but unlike before where copying clips, projects and the stone+wire db would get you up and running, this new postgres db is another beast altogether, it seems to need signing certs, and once placed on a new system just comes up corrupted, I’m guessing its encrypted?
But have just had no luck on getting it working.
Seeming its only been installed for a week or so i’m going to archive it all and recover on the new HDD.
The only thing that worries me is how do we take nightly archives of the system if the database recovers broken?
Going to spend the next few days trying to figure it out, unless some on has some insight.
Just a little background, we were on Rocky linux 8.5, tried the 8.10 upgrade and it failed on one system, so ended up deciding to do a full reinstall and recover to 9.5 worked flawlessly for all of the 2024.2.3 suites failed hard on the 2026.1
Well you can dump the database with pg_dump to an sql file and then pg_restore but I have personally not tried demolishing my own database and restoring it. As an aside, were you running 2026 prior in ‘trust’ mode or in ‘certificate’ mode for strict access control?
I think at one point the Flame team was going to be working on some docs for backup strategy/disaster recovery and/or maybe a friendly database backup/restore utility but I don’t know the status of any of that. For now I dump a copy of the database prior to making my system snapshots using
which dumps to the ramdisk file /dev/shm/flamedb.sql and then I compress it into a place that gets picked up by my snapshot backup.
If you have the ability to get the old working system back up ‘live’ so you can dump the database in order to experiment with importing it back into the new one…. have at it
I’m on Discord if you want moral support or other crazy ideas
I’m not 100% sure what option was chosen when starting flame for the first time, but would have assumed trusted, but could be wrong on that.
But the db archive seems like the way to go and will probably incorporate that into our current archive workflow. (really recovery workflow)
Fortunately when doing a full OS upgrade like this i shelf the disk and install on a new one, so this morning I just swapped the old disk back and we archived the projects and re-imported to flame.
I have a workbench Z8G4 i can run some tests on so will probably be doing that to try and find the best way to automate recovery if a system goes down.
On another note, with the old versions if something went wrong you could just pop in to clips and unarchive the older version, what’s the process now to recover earlier versions? its infrequent but it dose happen.
hey Andrew,
