Hello there.
I’d like to suggest an enhancement to Scrivener, namely, the ability to set up backup folders per project. At the moment, unless I missed something, there is a single backup folder for everything. Personally, I would much prefer to keep my projects and their backups together so it would be great to have the ability to set up a backup folder on a project basis, with its own backup settings.
Many thanks.
You can do this via → Project → Project Settings… → Backup
Ah, awesome! Many thanks!
If you keep your project and your backups in the same master folder, and you inadvertently delete the master folder, how would you recover?
Be sure you have an answer to this question. 
Best,
Jim
You can set up a project-specific backup folder. But you’ll get an error message if you make it the same as the folder containing the active project.
https://scrivener.tenderapp.com/help/kb/macos-troubleshooting/project-not-in-a-recommended-save-location-error
I keep separate backups of my entire laptop on other devices, in a multi-tiered backup strategy. I think I’m ok on that front. 
I keep the backups in a folder of their own, inside the project’s parent folder, so I don’t get that error.
– DANGER – DANGER –
If something unfortunate happens to your project, it’ll happen to your backups too.
Plus: Every time you backup, you include the previous backups. The file uselessly growing in size.
Plus: You can’t move the project without messing up the backup dir.
This is not good.
Backups and the project they are intended to secure, they should be kept apart.
If something unfortunate happens to your project, it’ll happen to your backups too.
No, because I keep several backups, as I mentioned before.
Plus: Every time you backup, you include the previous backups. The file uselessly growing in size.
No, because the project and the backups folder are siblings. The backups folder is not a child of the project.
Plus: You can’t move the project without messing up the backup dir.
Again, no, for the same reason.
Backups and the project they are intended to secure, they should be kept apart.
They are apart, just not as far from one another as the default setting makes them.
Then I suppose that by
you mean a layer of folder-structure you added yourself, manually. (?)
. . . . . .
Too close for comfort, still, in my opinion.
Say that I have a project called Foo. It has its own directory, Foo, inside of which lives the actual Scrivener project Foo.scriv and a directory called backups. The latter houses the backups for the Foo project.
Yes, if I accidentally delete the Foo directory, then I lose the Foo project and its backups.
However, that’s not a likely scenario for me given the way I work and, in any case, I keep automated full backups of my laptop in various external drives, staggered in time. Should an accident happen, I can recover from it without losing more than a few minutes of work.
It’s a setup that I am happy with.
Yes that’s fine, and it make sense to me to organise backups into the master folder for an overarching real-world project. With the way I work, when I am done with a large effort that deserves a folder and subfolders with files like that, then I zip up the whole master folder and put that in an archival area, deleting the working folder once I’m done doing that and testing the zip. If I scattered important components of the project elsewhere, like backups, then this would complicate the archival process.
The warning message Scrivener gives should only trigger if the backup copies are being opened directly—and really it’s more a warning about doing that, but it does overlap into not storing the working copy in the same folder, too, which indeed would be mayhem.