What I do to guard against file corruption is:
1. Turn on auto save, set for every 5 to 20 minutes, longer intervals as rhe file size grows past 50 mb.
2. Periodically do Save As to a new file iteration
3. Cooy and save some xhiice backups to other media and to new backup names, even if those sre on the same disk.
4. Periodically revisit saved files and backups to assure myself that they can be opened.
Also, part of my workflow is:
1. At a mentally-convenient point, stope working on the file to do a new Save-As
2. Selecting a bunch of splines I know have associativity to something, and going to the Concept Explorer tab named Entities, and right click on one of the splines listed, make sure it has an associative item, then click on "Force Resolve Links"
3. Go to app menu item Edit, then click on "Resolve Links"
4. Do a Save As as yet a new name
5. Click on File, Compact
Note: I can regularly every 30 saves end up running into a spurious/unceremonious app crash. Hence, saving as a new name BEFORE doing a compact.
6. Compact as many times as necessary, unlike in my earlier years of recognition of Compact (~2016 onward) where I did only a SINGLE compact, unawares that in at least Shark V9 (before I upgraded to/bought v12) there can be as many as 15 Compact actions (akin to going home by walking only half the distance of each new leg, then stopping) needed before no more appearances of the dialog listing objects that can be selected and saved from that sub-panel of operations.
7. After Compact is done, yet again do Save As, before moving on with more edits.
As for guarding against spurious loss of tool pallets, I back up those to a differently-named folder.
Yes, as I'm designing naval ships as if a pseudo wannabe naval architect, but doing almost EVERYTHING in a single file, my files grow to 140 mb when saved-as, depending on how many solids and linked curves and surfaces exist. And, currently, Im hitting 1.1 to 1.8 GB during mormal edits. Doing rapid and numerous solids/surfaces related edits via underlying control curves (mostly control point splines) can push actively used RAM to over 2GB. Saves can, too, until the save operation finishes.
Opens can take up to 30 to 60 secinds, and saves/auto saves of a 90mb to 120 mb file can take up to 2 minutes. Closes of a successfully saved file can be nearly instant.
Also, based on some past losses or crashes, I close the files BEFORE closing the Shark app.
Sometimes, I'll immediately reopen the file to ensure nothing awry occured, unless I'm rushed for time.
