![]() ![]() 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. 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. Please enter security code that you see on the above box.I have a slightly contrary view about moving from Cloud Station Backup (to DSM Drive) to Synology Drive for backup. Send me an email when anyone response to this However, if you wish to receive a response, please include your email and name. Sharing your feedback about this process or ask for help Here is the list of instances that we see for the process: cloud-backup-daemon.exeĬ:\Users\username\AppData\Local\CloudStationBackup\CloudStation.app\bin\cloud-backup-daemon.exeĬ:\Documents and Settings\username\Local Settings\Application Data\CloudStationBackup\CloudStation.app\bin\cloud-backup-daemon.exeĭ:\Users\username\AppData\Local\CloudStationBackup\CloudStation.app\bin\cloud-backup-daemon.exe If you think this is a driver issue, please try Where do we see cloud-backup-daemon.exe ? Let try to run a system scan with Speed Up My PC to see any error, then you can do some other troubleshooting steps. What can you do to fix cloud-backup-daemon.exe ? If you encounter difficulties with cloud-backup-daemon.exe, you can uninstall the associated program (Start > Control Panel > Add/Remove programs Let try the program named DriverIdentifier to see if it helps. ![]() Then simply restart Cloud Station on the client and it will start working. The solution is to generate a new UUID on one of your devices (I use uuidgen for this) and then save it to the file mentioned. Synology appears to use this to determine unique devices connecting. Is cloud-backup-daemon.exe using too much CPU or memory ? It's probably your file has been infected with a virus. It turns out the problem is the this file: /.uuid. ![]() Do the following to configure the Synology product you want to back up to, and then click Next : Enter the name of your computer, the IP address, the QuickConnect ID, username and password of your Synology. Synology appears to use this to determine unique devices connecting. On your Linux computer, go to Dash > Applications > Internet > Synology Cloud Station Backup to launch the wizard. Something wrong with cloud-backup-daemon.exe ? It turns out the problem is the this file: /.uuid. ![]()
0 Comments
Leave a Reply. |