Yes, Task Scheduler is what I would recommend if you need more advanced features. Because of this I don't see a reason to upgrade the Acrosync scheduler.
As for the command line mode, I don't like the idea of having too many command line arguments.…
Not sure if I would do this. The command line mode is supposed to be run from a script so it was kept to a minimalist level. For instance, the command line execution prints the logs to stdout and doesn't honor the 'log to a file' option. It is ex…
That is because you used the same remote directory for backing up photos on both iPhones. That is dangerous because photos on different iPhones may have the same file names.
'N' and 'I' both mean 'not indexed' -- this is so confusing!
What matters here is not whether or not they have 'N' or 'I'. If the file has 'A' then Acrosync will treat it as a regular file. So if you can add 'A' to all the files using a command li…
That is because those .MOV files do not have FILE_ATTRIBUTE_NORMAL or FILE_ATTRIBUTE_ARCHIVE set, so Acrosync didn't pass the regular file mode to rsync.
Can you run the 'attrib' command to see what attributes those files have?
I found this post on synology's forum (possibly by you):
http://forum.synology.com/enu/viewtopic.php?f=260&t=106168
So the solution is to enable the admin account for anyone else having the same issue with DSM 6.0.
I'll look at the memory issue, but for the blocking one, can you try the latest build here:
32 bit: https://acrosync.com/win32/acrosync_installer_win32_1.5_519.exe
64 bit: https://acrosync.com/win32/acrosync_installer_win64_1.5…
The new version 1.4 with a fix is now available in the App Store.
For others reading this thread, the root cause of the issue is that one method of the Apple PhotoKit API used for requesting photo and video content, requestImageDataForAsset, may re…
I can get you a special build that would help track down the issue, but that would require you sign up for our beta besting program via Apple. Would you like to do that? If so, send an email to [email protected] and I'll add you to our beta…
Normally device logs can be found in Xcode. If you don't have Xcode I believe the best method is to install idevicesyslog from https://github.com/benvium/libimobiledevice-macosx/blob/master/README.md.
Can you check your device log to see if you got any log messages like:
"Skipped an asset with irregular url"
"No PHImageFileURLKey found in asset"
These are two possible cases where a file may be skipped.
Was that the first time you ran PhotoBackup on that phone? Auto sync by default skips photo/video files previously uploaded, so what you encountered could happen if you delete some files after the first upload. If this is the case, then you can tu…
'Local Directory' should accept any directories with spaces.
To specify files/directories with spaces in the include/exclude patterns, replace space with '*'; for example, 'My*Documents' (without quotes).
That was more than a year ago but even then it wasn't a beta version. We have many bug fixes and improvements from the first version 1.0 to the current version 1.7.
Can you try this build for which the timeout has been increased to 600 seconds: https://acrosync.com/osx/acrosync_1.8_build_488.dmg
Note that this is the non-App Store version so if you have an App Store version, email me and I'll send you a free ac…
The remote directory '/root/Pictures' is likely on your system partition which is at most a few Gigabytes. You should create that directory on your storage partition.
A new version is available in which the timeout value is increased to 600 seconds. The reason for this change is that it may be possible for the network traffic to stall for a while before it gets going again under certain conditions, but I haven't…
This is an error reported by rsync running on your server. Looks like you're out of disk space, or something is wrong with the disk (check disk might fix it).
I just replied your email. For those who have encountered the same error, please make sure you're running the latest version. If you're already, email me a screenshot of the error as well as the ssh and rsync version on your server.
The maximum file name length in Linux is 255, so if your file name is 128 character long then after encoding to UTF8, the length may exceed the linux limit. For example, when I create a file with this name:
РјРЅРѕРіРјРЅРѕРіРјРЅРѕРіРјРЅРѕРіРјРЅРѕРіР…
Internally, Windows should always use UTF16, unless your file system is FAT, not NTFS.
I still wonder if that error was actually caused by the file name too long for Linux. What if you exclude that particular file by using the 'Don't sync' setting?…
Can you post here the file name that caused the error?
Acrosync for Windows uses the equivalent of '--iconv=utf16,utf8', i.e., all file names are converted into UTF8 before they are sending to the remote server.