This has been a pain point in my workflow for a long time. I run a primary/backup setup with both machines connected to a shared network drive. When I make changes on the primary, I save the project and load it onto the backup. The problem is that interaction settings, OSC IPs, ports, server configs, are stored in the project file. So every time I load an updated project onto the backup, all of those settings get overwritten with the primary’s values, and I have to manually reconfigure them.

What I’d love to see is the ability to designate a machine as a backup that syncs the project content (boards, timelines, media references, effects, transitions) while preserving its own local interaction and device settings. That way when I make a change on the primary, the backup picks it up automatically without me having to re-enter all the OSC configuration every time. It would save a huge amount of time, especially during rehearsals when changes are constant

As a temporary workaround you can setup a network drive (or google drive) so that both systems are pulling from the same files and you can save a project file in one place. That way to refresh the backup you just reload your file and are back in business.

It would be cool to have a computer designated as “backup” allowing you to auto update in one direction and maybe a push back function if you have to make updates during a show.

Or maybe a “sync” feature.

yes!!! I use the COLLECT consistently - but that is an issue too - as I save this to a Share on the BACKUP machine.
But now my primary is using this file.
So I have to close primary and re-open original file.