Typing lag when working on NAS

Scrivener Scrivener for Windows
23

Glad to hear you the got the lag issue sorted. :nerd_face:

Here are some (unrequested) suggestions about backups and your backup settings. All backup options are found under File > Options > Backup.

You may have mentioned this already, but you might want to ensure that Back up on project close is enabled, as well as Compress automatic backups as zip files. As others have mentioned, choose a backup location that’s on local storage (not your NAS). Then when you close Scriv, you’ll always get a local zipped backup.

I strongly recommend that you enable Backup with each manual save, and then get in the habit of doing a manual save via Ctrl-S every hour or two. This way you’ll have zipped backups of your work throughout your writing day.

I’m suggesting this because Scriv’s auto-save is not a perfect, fail-safe solution. There are occasional posts (like this one) where there was a system-level crash that corrupted Scriv files, most notably the binder and whatever documents happened to be open at the time of the crash. This happens despite auto-save, because it seems the open Scriv project files are actually damaged on the disk in this scenario.

You use of the NAS may make you more susceptible to this scenario. Not trying to scare you, just pointing out a possible risk.

But even if you weren’t on the NAS, this scenario can occur to anyone, and the simplest, most foolproof way to recover from it is to have a recent zipped backup. Hence my recommendation to get in the habit of Ctril-S with that option enabled.

There are two downsides to this approach:

  1. The time necessary to make the zipped backup may interrupt your writing flow, particularly with a very large project. I’d still do it, say when you get up for a bio break. :innocent:

  2. You’ll have a lot more zipped backups to deal with. I handle this at the end of the day by culling backups manually.

Best,
Jim

1 Like