Small backups of Flame working files

and did it work?

so is it enough to back it up or do i need to backup my whole project server VM

Point /opt/Autodesk to ZFS and snapshot regularly.

Many times. Archives are preferred, but if the data is there, there is a possibility to get back up.

1 Like

with the INSTALL_PROJECTSERVER script there is now a --dataroot switch which makes it even easier to slice off only your relevant data onto a separate location so the OS drive becomes rather generic instead of “pray something doesn’t go wrong” paradigm of the past.

2 Likes

The only things I have ever used from opt/Autodesk when rebuilding the system is my personal material, such as hotkeys, bookmarks, python scripts and fonts. I keep that all saved off separately and update now and then as I add things. Everything else that is project related is part of the archive.

Step 3 shows you what files are useful to have saved.

2 Likes

so all in all whats really missing is a way to backup working files while everything is running due to the nature of swdb beign a database.

In postgres you can basically export snapshots of the database while everything is running, which is neat.

having the projectserver on a vm like alan is doing will bypass that problem.

I am trying to protect against hardware failure and with multiple flames connected to one projectserver loosing a whole day because i only back up at night because i need to stop sw is not that great.

1 Like

Setup a multi node Proxmox cluster with CEPH and live High Availability migration.

Or buy 1 quality Dell server and LXC live backup to Proxmox Backup Server at interval of your choice. We do every 4 hours.

I’ve never had an issue with a Dell server and in USA, they are plentiful on eBay for cheap price in great condition.

1 Like

Exactly this.
Live migration is fascinating.
Hard on mac hardware. (in my limited experiments)
Quite straightforward elsewhere.
And Ceph ftw.