VWX backup File Strategies in General Discussion Posted November 4, 2019 Every workflow is a bit different and my situation certainly doesn't match yours exactly, but I thought I'd share the auto save procedure I've developed over the years that works very well for me at the moment. I make heavy use of layers to organize multiple versions and various parts of a drawing, and all my symbols remain in the file for the duration of the project. I do mainly trade show design, so most of my jobs are based on show cycles that repeat on a yearly or bi-annual basis. Each cycle is based on the previous unless we're doing a complete redesign, so the 2020 file is a copy of the 2019 file, which was a copy of the 2018 file, etc. I will generally purge the new file of unused resources from the last year, but those resources remain in the old plan, so those act as a backup. For the duration of the project I keep one backup every 15 minutes in the same location as the original. I used to keep more, but because I never delete resources from a file until purging before the next show, there is really nothing to lose. That means if I do experience a crash (which is rare, as I will explain in a moment), I never need to go back more than one backup, therefore is no reason to keep more than one. There is nothing in a 30 minute old backup that's not in the 15 minute version, and if I accidentally purged something I need it's in last years file. So my total backup file size is just that one file. As for crashes, I used to experience them so frequently that I once wrote a haiku about them, but no longer. There are often crashes that accompany upgrades, or anomalous behaviors that Vectorworks is famous for (some time ago my rig crashed every time I selected a blue fill from the menu, though it worked fine if I typed in the RGB number), but those are eventually fixed through a service pack (usually), and we can put those aside. I find that the crashes in our office mainly occur due to the user asking too much of the computer in one shocking moment. That's not to let VW off the hook. They should be able to let you know that you're overloading the system and stop your process without crashing the entire program. But I did find that crashing practically disappeared when I began diligently organizing my file into manageable visibility chunks, used Saved Views to navigate them, and kept my geometry as simple and streamlined as possible. If you ask the computer to manipulate too much geometry all at once, it will likely crash. Ultimately, I find that exquisite organization is the key to a happy Vectorworks experience. I described the details of that in an other thread that I participated in some time ago in relation to keeping file sizes manageable (see link below). Another thing I noticed is that auto saving itself can cause crashes, I think when it tries to save while in the middle of some process. So, auto saving too frequently can be a problem because it creates more opportunities for a crash.