This is to confirm the power of Scrivener, even during power outs and doing very edgy things with my projects.
We had sporadic blackouts over the weekend, culminating in me saving during a time the computer went into standby mode last night.
This morning when I plugged into power, Scrivener picked up its save and backup of a project from 91% and closed, as per original intent. On restarting, the project was up to date, as expected, and the backup is equally fine.
That’s why I have such a high regard for Scrivener and frown on people complaining about Dropbox synced backups.
I think, mainly, it’s because so many different points-of-failure exist when using cloud services from the user perspective, and it is near impossible for Scrivener Support to determine what happened from a narrative and photo or two.
I just have lots of backups with differing mechanisms. For instance, I use Dropbox (as I want it on my iPhone and Windows machines), but also NextCloud. Also, I have multiple folder locations on external and internal hard drives.
Also, the cloud-specific points of failure are out of Scrivener’s control, but we get the support queries when a problem occurs.
It’s great to hear that the backup was able to complete successfully after standby mode, but that’s definitely not something we would recommend!