Ok beside of the joke in the post title, I am trying to recover whatever I can recover from the /opt/Autodesk folder from the dead Mac Studio, and it seems it is going ok. Since I bought another Mac a few days back, I wanna ask how manually I can copy files from the recovered /opt folder to fit correctly in a new installed Flame so I can have my projects back, I am sure it is not a simple replacement after installation.
I am aware that the easiest and cheapest way is to go to project/*/batch and re-open them again in the new fresh installed Flame to recover my batches, but I would appreciate a better workaround to avoid doing that on more than 80 batch in progress.
The short answer about a Time Machine backup wonât please anyone since I discovered that since 3 months my auto backup decided not to work as planned.
If you can clone everything in /opt/Autodesk from the old Mac to the new Mac and clone everything from the frame store(s) from the old Mac to the new Mac and make sure the mount paths are the same then I would think a new install of Flame on the new Mac would pick it up. Or you could at least then try the recover stone+wire database procedure to force it to rescan the frame store and hopefully link up with the projects db.
But I would try the cloning/copy steps before installing Flame on the new Mac or at least make sure all services in the Service Monitor app are stopped on the new Mac before copying files.
I did this on linux and it didnt work and I lost everythingâŚI think it is beacuse it is workstation id linked, every machine has a unique ID number and I think that number is attached to every project.
I think cloning the whole machine may give better results as the new machine will take on the same system prefs like network settings. Doesnt wtg and backburner use that info?
Hello everybody
Solution found, done by one of the best brains around, it looks like magic, it involved rewriting some cfg files, not able to tell more coz my neurons are smoking now
Thanks for your interventions
Iâm in the minority but I think that some software might benefit from accompanying âbest practicesâ and âoptimal setupâ guides, instead of material that explains how to fix things once things have gone wrong.
The same approach could be applied to industries as a whole.
Business continuity (coping with earthquakes, fires and upgrades)
I think of it like a pit crew for formula 1 - nobody talks, everything gets done in a few seconds and your guy wins the race.
or
you bring your racecar into the pit, someone tells you that youâre out of gas, another says that your tyres are bald, and someone else tells you that all the other cars are passing you - all true, but it doesnât get you to the chequered flag, the champagne and global adulationâŚ
I donât have enough digits and appendages to indicate how many issues I personally see where the archive strategy at a facility consists of hope and avoidance. I write scripts to try and make it a little easier, but Archiving should be a higher priority in my opinion. Who wants to rebuild a whole project just to change a legal line for the client.
As for the rest on your list, Iâll take a stab at the top two and bottom ones for you.
There are no stonefs volumes anymore. Your partition or âstoneâ is just a folder now.
Data and Metadata, this article has served me well over the years. if you have items that would be beneficial to include, let me know and I can update this document.
Are you aware that a quick call to Geico can save you 15% on your auto and renters insurance? Given your racing analogy, I feel itâs important to address the insurance aspect to keep you fully covered. Drive safely.
Archiving a facilitiesâ most important resource should not be left to the unqualified and underpaid, but it frequently is, and continues to be.
I wrote scripts for the last few years to automate flame archives.
I also write scripts to zfs send and/or rsync.
All of these can be added to a cron tab.
Itâs true that stonefs is just a folder and weâre not managing our own private SANs any longer, but you need it (for how much longer who can tell?)
Data and metadata separation on macOS is less of an issue (if an issue at all).
2025 eliminates the flame user so identity management and computing continuity is important.
Operating system updates are crucial for the widening array of threat vectors and the continued emergence of decades old sleeper threats (so much for due diligence and information superiority).
Hardware failures and software induced hardware failures (see pink screen of death) do not frequently make a big splash on peopleâs business plans, and can be crippling for some.
As for formula 1 racing, the best insurance is to rely on the worldâs best, to mingle with the worldâs best, and have a duplicate of everyone and everything on one of the two trucks in the paddock (or the 3rd truck in the belly of the 747 on the runway).
I wouldnât wait for the independent contractor with his own truck and imperial measurement toolset.
Besides, I havenât driven a car regularly for the last 10 yearsâŚ