Dave Wilkins wrote:Windows can do it, so why not your NAS? You'd have to ask them.
Thanks for your prompt reply, but 'asking them' is not the answer (as you probably know). While I am willing to buy the software, I would also like an effort from you to solve the problems I have...
I know I am not alone with this problem, and I (think I) know that you don't like NAS devices, since there are many problems with these devices.
Again: I know I am not alone with this and I am unable to find an answer other than "your NAS is not OK".
I just tested the zip-profile again but now I used a folder on another partition as destination. As a breeze...!!
So the problem is the NAS indeed. Maybe it's because this is a Linux filesystem there?
Your statement from the FAQ: SyncBack supports any system that can be accessed like a normal drive. This includes CD-RW/DVD+-RW formatted using UDF (UDF is not required if using SyncBackPro), CompactFlash, external drives, floppy disks, NAS devices, etc
I have to conclude (after several days of testing...) that this statement is not correct when a NAS is concerned.
Would you be 'open' for a solution of the problem???
As I said: I just tested the zip-profile again, but now I used a folder on another HD-partition as destination. As a breeze...!!
So I think (I think I am sure...) that YOU can solve this problem by providing an option to use a file or folder on the SOURCEdrive for the tempfile(s)...
I mean: Don't perform the renaming at the NAS but 'somewhere' on the sourcedrive. My guess is that this would fully solve the issue.
I am thinking of possibilities to do something similar myself in the meantime... First a 'safe' copy/backup to another partition, and another 'normal' copy/backup from this partition to the NAS.
But this would mean twice the amount of data... <sigh>
Regards, Arno R