Max and Auto backup

[voltron7]

File/Save As /Save Copy As

I like this method as opposed to Save As with increment (+) because it will save the copy, and you can call it whatever you want, and it doesn't change your working file name. THis allows me to save off quick temporary backups with a different naming convention (for safety of overwriting etc) without compromising my file organization and versioning of stages that I want to actually permanently save.

/b

Interesting, perhaps will give it a try...

[simmsimaging]

If interested: here is the workflow I use for saving. This keeps me pretty well covered but avoids having a billion working files accumulating that need to be managed/backed up daily/archived etc.

- Save main file with a version numb like xxxx_01.max

- immediately use the "save copy as" and call it xxxx_A.max

- while working I save safety copies (what the autoback should do) as xxxx_A, xxxx_B, and xxxx_C. Each time I save I overwrite the oldest of those 3 files, so I have a revolving set of 3 safety copies. From time to time I add more backup temp files (xxxx_D, xxxx_E etc) but rarely.

- whenever I am at a stage worth permanently keeping it gets saved and incremented to xxxx_02.max, xxxx_03.max etc. Because there are still occasionally issues with Max corrupting files/crashing on saving, I usually also save a safety copy just before or just after I save a permanent version as well, so most permanent saves are immediately covered - just in case

This way I end up with only 3 "backup" files at any one time and everything else is something worth archiving so it requires no editing on my part when it comes time to archive the whole job or clear some disk space. I do this with Photoshop files as well and have cut down my disk consumption by 100's of GB

/b

[voltron7]

good

If interested: here is the workflow I use for saving. This keeps me pretty well covered but avoids having a billion working files accumulating that need to be managed/backed up daily/archived etc.

- Save main file with a version numb like xxxx_01.max

- immediately use the "save copy as" and call it xxxx_A.max

- while working I save safety copies (what the autoback should do) as xxxx_A, xxxx_B, and xxxx_C. Each time I save I overwrite the oldest of those 3 files, so I have a revolving set of 3 safety copies. From time to time I add more backup temp files (xxxx_D, xxxx_E etc) but rarely.

- whenever I am at a stage worth permanently keeping it gets saved and incremented to xxxx_02.max, xxxx_03.max etc. Because there are still occasionally issues with Max corrupting files/crashing on saving, I usually also save a safety copy just before or just after I save a permanent version as well, so most permanent saves are immediately covered - just in case

This way I end up with only 3 "backup" files at any one time and everything else is something worth archiving so it requires no editing on my part when it comes time to archive the whole job or clear some disk space. I do this with Photoshop files as well and have cut down my disk consumption by 100's of GB

/b

Thanks Brett, This is similar to mine, but better, because of the manageability/less clutter of files. I often end up with waaaaay too many iterations of the scene, just foolish.

[flino2004]

because I'm saving constantly and I turn off all the Autobackups in all my applications( Autocad, Rhino, Sketchup,Max, Revit) since then I didn't have any problems with corrupted files.... I found that every time when i got problem was because of that.
if you work fast and the application is autosaving the file, it's also saving the commands that you are typing/clicking so the chances to get corrupted is higher during that process.