![]() ![]() I do know that sync is not a backup - but pCloud has a timemachine build in - so deleted or changed files can be accessed. It doubles the used space on pCloud - but with 4TB im still very much in the green here. sync DT to a DTCloudStore on pCloud through Webdav as intended by DT.local stored databases sync to pCloud (through pCloud Sync Service).*dtCloud can also include multiple databases - also just understood this. Thanks for your explanation - i did only then see that *.dtCloud and *.dtBade2 are probably not the same even if it seems so at first. I just realised, that these are two different file types … so probably what was originally trying to do is not really working at all … I thought i had this running - but i probably did some thing different So my question, which setup would be best?ĭT saving data locally - pcloud syncing that to the server - DTTG access vie WebDav (if that works my favourite)ĭT saving locally and sync to Webdav - pcloud sync copy on server as backup - DTTG access via WebDav to DT Sync File (DT “Size” doubles on pcloud) but i´d like to access the most up to date database of course. I do not actively create files and notes on the go. so its (at the moment at least) more like DTTG is a reader for my Database. I use DTTG on rare occasions only, where i need a file on the go. i did try this setup, but its not reliable somehow. (this would double the data on the server though) Now i was wondering if i can setup DevonThinkToGo on my iphone to simply hook into that database file on the server through WebDav (as pCloud offers webdav access to every file) or if it is needed, that i setup a WebDav Sync also on my main computer. My Devonthink Databases are also in these document folders to have a constant backed up version. Now I have my local Documents always in sync with the server. (if anyone is interested in a DropBox alternative, i´ve written a bit about it here: ) I use pCloud as sync and backup service for a few years now and I am super happy with them. ![]()
0 Comments
Leave a Reply. |