Thus, turn on-demand off and have all the files always on your machine. * IDrive does not work with on-demand synching of e.g., Google Drive or OneDrive. So, you need to solve the issue somehow (by renaming, moving or deleting files). Most likely these files are, anyway, skipped by IDrive. This way you’ll find the files/paths that for some kind of reason are problematic. However, you should also execute the command without the flag. It allows the command to continue in case of errors. More information here: Īn important flag here is /C.
Idrive synology backup stops full#
This gives you full control for all the files under the current path.
Idrive synology backup stops windows#
From Windows standard Command line you can set the permissions correctly with * IDrive does not handle permission problems very well. It is a more powerful command line tool than the standard one. If you do not know Powershell, you should google it a bit. Recurse -Force -ErrorAction Continue | Where-Object You can list these filenames with Windows Powershell script * IDrive is not very good with long filenames (> 250 or so characters). This seemed to work all the time, even when scheduled backups or "Backup Now" failed. * You can force backup of a path by right clicking in File Explorer (you might need to enable this behavior somewhere in the IDrive settings). Some other things I learned during my journey: Thus, allowing multiprocessing, things went forward. I’d guess that the single process somehow got deadlocked. However, according to my Task manager it seems to manage whether the program executes on a single process or multiple processes. The setting does not seem to be mentioned anywhere in the official documentation. I still do not know the background reason, but the solution MOST LIKELY was to enable the setting “Optimize CPU resources”. After half a dozen contacts to support, two data dumps to their development team and months of debugging, I got it working. It just looped over “Preparing file list” in the beginning. Unfortunately, two of my machines constantly froze right when backup was starting. I bought IDrive for three of my Windows machines as a cheaper replacement of CrashPlan. The solution for me was to enable “Optimize CPU resources” under “Settings” In short: My IDrive got stuck with “Preparing file list” looping forever when I tried to execute backup. Hopefully, this will slightly reduce the overall suffering in the World
0 kommentar(er)
