I am a brand new user. Just found your program and it is great! It worked out of the chute... wonderfully!
I just have a couple of weird issues, and for my purposes, I want to make sure I understand what is going on. (so that, ultimately, I can fix it.)
I am using the program to "Upload to FTP" with a "Full backup" and I use the option to "Synchronize".
The source files in question are on a Network Attached Storage (NAS) that I am accessing via network name (e.g., \\NAS1\share). The user I have put into the "Advanced" tab has Read-only rights to this resource (the NAS). I have read-only rights on this resource, on purpose. These are live media files that can/may be downloaded. I DO NOT want the archive bit set.
So, I set up the job, set the parameters I thought would do exactly what I wanted... (Full/Synchronize) and then ran it (on a test directory, I haven't messed with my live files yet). To my shock, I found that:
a) Everything was coped over perfectly. I love it. It was so simple!
b) Somehow (and this is really really weird) the archive bit was set on all of the source files!
Now, I love that it worked, but I hate that the Full backup with synchronize even tried to set the bit. AND, I have no idea how it did! I log in as the user that I specify in the job and I can neither clear NOR set the bit.
So, what I am asking is this...
Is there a setting somewhere in APBackUP v.3.3 to:
1. Backup/send only the source files that don't match the modified date on the FTP server.
2. Leave the files in the source directory alone (now, if during the processing, you need to set and clear the archive bit, that is okay, I just want them to end up the same!)
If I can't get 1, I gotta have 2. I have live media files (photos, movies, etc.) being downloaded and viewed on the web, I can't have the archive bit set as they might be sent BACK to me like that.
Your attention is appreciated,