For what its worth, I dont seem to have this problem on any other clients, but this user does use Cloud Station more than most. I brought it down to 8 and the problem was almost instantly relieved. The current desktop apps for Cloud Server Backup have been updated recently, and there's a Mac 64-bit version ready for MacOS 10.15 "some desert" dropping 31-bit support in the summer. Synology support directed me to reduce the number of revisions in the Cloud Station package settings on the server. you need to exclude this folder from syncing back on the two-way task. The destination this setup uses it the DSM user's /home/Drive/Backup/ folder, and access privileges are already correctly configured. So, for now, I would rather use Cloud Station Backup on Mac (etc) to backup to DSM Drive. It is do-able but needs testing and many NAS owners will struggle to do this. And this is the reason I keep using Cloud Server Backup: the DSM admin must ensure that Team folder / shared folder privileges are set correctly to limit access from other DSM users whether from Drive apps or other methods. This means that using Syno Drive for doing a backup (one-way) task must use a Team folder as its target. Doesn't matter if the first task is excluding the folders you want to store the backups. If you are already using Syno Drive to do a Dropbox-style service with your /home/Drive folder then you cannot set up a second task to somewhere within /home/Drive. The reason being the destination on DSM for backup data. I have a slightly contrary view about moving from Cloud Station Backup (to DSM Drive) to Synology Drive for backup.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |