Good evening! I want to use pCloud to store my archive with a lot of Scrivener files. Did anyone here experience problems like data loss?
I will not sync it! I will use pCloud as backup storage only.
Really it’s pCloud, not iCloud 
BTW I’m on Mac and Win … (Catalina, Big Sur an Win 10).
TIA
Walter
Hope and assume you are putting the backup zip files created by Scrivener on this service.
1 Like
Um… no… just the files that I have in the folder of my archive… never thought about the backup files … does this create a problem?
For uploading copies of the project, it depends on what you mean by this:
@waco: I will not sync it! I will use pCloud as backup storage only.
If you’re directing pCloud to sync the areas where there are Scrivener projects, or moving those projects into areas it syncs, then opening and editing them will involving syncing them, naturally. In theory that should work fine, though it’s always something that should be tested very carefully with lesser-used services (I use Tresorit, a very similar service, and it has never once messed up a project sync, though I rarely use it for that purpose). But of course that isn’t a backup by any definition, in that case…
So I presume you mean making copies of the project into those areas, and then never editing them directly. In that case you should be fine. Scrivener projects are just a folder hierarchy with a bunch of files in them (this is kind of hidden from you on a Mac, but it makes no difference to sync engines what a folder looks and acts like on a Mac).
What works easiest for most people by the way, is to go into the Backup preference pane on each computer and point the automatic backup folder at the synced area on the drive, or configuring sync to keep that folder updated (depending on how the tool works). If you do that, tweaking the settings is a good idea—in particular I like to use at least 25 saved copies and date stamps, as this works better with how most servers work. The default creates x number of backup copies and then rotates through the same file names over and over, which can get confusing with versioning. As noted above, .zip compression is good for anything going over a network, though if your cloud server is on the LAN, it really doesn’t matter too much.
If you’d prefer to keep each machine’s automatic backups separate, and manage a shared repository manually, then the File ▸ Back Up ▸ Back Up To... menu command is the easiest—particularly since you can safely fire that off while in the middle of working. You don’t have close out and then do a bunch of file management stuff to copy the project and “upload” it. You’ll note that feature as a zip compression option as well. There are advantages to this approach, as you effectively end up with 50 instead of 25 (or whatever), and thus a much greater safety net for resolving cases where you forgot to sync machine X and did a bunch of work on Y for a while.
2 Likes
Hi AmberV, this is exactly what I tried to say… 
Thanx much, that really helps! 
I always think for archiving something like a Scriv project it is good to archive the zip of it. This prevents accidentally changing anything and so on.
3 Likes