gbland Posted November 26, 2019 Share Posted November 26, 2019 Does anyone have any best practices tips for what to do when a working file crashes? If a normal VW drawing crashes, I just open the backup and save as the original and I'm back in business. When I am using a working file that updates/syncs with a project file, doing this (saving a copy of the backup working file as a new working file) screws up the permissions and it will not work with the project file properly any longer. So I end up creating a new shared project file and creating new working files whenever I crash... Pain in the butt. Maybe there is a webinar on this somewhere that I missed. Thanks, Quote Link to comment
Jeremy Best Posted November 29, 2019 Share Posted November 29, 2019 Hi @gbland, I presume you mean if Vectorworks crashes in such a way that the Working File becomes corrupt. (If not, presumably you can just reopen Vectorworks and the Working File and carry on. Backup files are used when the original is corrupt or if you've made changes that Undo can't reverse). Vectorworks produced a comprehensive publication on Project Sharing referred to as the 'Workflow Document' on this page, which I know covers what to do if your Working File becomes corrupt, but this is also answered in the Project Sharing - FAQ forum. Quote Link to comment
gbland Posted November 29, 2019 Author Share Posted November 29, 2019 Thanks for the reply! I'll check out the links you sent. I am not talking about corrupt files... I'm just looking at retrieving unsaved work. If I have an autosave backup running every 15 minutes but I have not saved the working file for 2 hours and it crashes, I would loose 1.75 hours of work if I just fire up the working file would I not? My thought is how to open the automatically saved backup and use it. Again, this may be addressed in the workflow doc you linked to... I'll check it. Finding holes in my self-education. Quote Link to comment
unearthed Posted November 29, 2019 Share Posted November 29, 2019 15 minutes! I have autosave set to 1min (and keep 3 most recent backups) and run all autosaves to a single separate folder for easy occasional deletion\cleaning. Even with maybe 20 active jobs its only 11Gb Quote Link to comment
KarynT Posted November 30, 2019 Share Posted November 30, 2019 I have mine set to 10 minutes, yet save every few actions. Too many crashes have taught me that large PDFs or reworking plant graphics cause mayhem! You might change the time settings for the autosave to one of number of actions. Quote Link to comment
Jeremy Best Posted December 1, 2019 Share Posted December 1, 2019 Vectorworks strongly recommend users have '5 most recent backups' or more. Autosave interrupts workflow - especially so for users with larger files or slower/older hard drives or when working on files stored on a server, so saving frequently might be an imposition. I would also suggest changing to trigger autosave by 'number of operations' to capture work done instead of time lapsed. This will avoid overwriting backup files when (for example) you've only done one operation since the last backup and then gone to lunch. Quote Link to comment
Jeremy Best Posted December 1, 2019 Share Posted December 1, 2019 @gbland, the answer to your original query can be found on page 38-39 of the aforementioned Project Sharing Workflow Document Quote Link to comment
bcd Posted December 2, 2019 Share Posted December 2, 2019 (edited) I recommend always comparing the timestamp of the backup file with your working file. It would be great if, after a crash, VW would offer the option - together with timestamp information: Reopen the working file or Recreate working file from backup Edited December 2, 2019 by bcd 2 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.