Hi there,
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,
Jared
Understanding the Synchronize Feature
In the current version APBackup set archive bit to be able to do incremental and differencial backups. I think such feature (don't clear archive bit) will be implemented in the next version.
When you set [Full backup mode + Sync] APBackup uploads only new files or if file already exists but size or file modification date is different.
When you set [Full backup mode + Sync] APBackup uploads only new files or if file already exists but size or file modification date is different.
-
jared4surf
- Posts: 3
- Joined: 25 Mar 2009, 22:48
thank you!
[quote="support"]New version 3.5 support FULL backup (don not clear archive attribute) mode.[/quote]
thank you very much. will download! program is very excellent. you folks are very very thoughtful for coming back and telling me!
i will open another thread for a delete issue (on the ftp server) I am having. it may not even be your program tho, still testing the FTP server.
thank you very much. will download! program is very excellent. you folks are very very thoughtful for coming back and telling me!
i will open another thread for a delete issue (on the ftp server) I am having. it may not even be your program tho, still testing the FTP server.
-
jared4surf
- Posts: 3
- Joined: 25 Mar 2009, 22:48
Re: Understanding the Synchronize Feature
Hello,
I may need to come back and open another thread, but I thought I would post this here as it has our whole conversation...
I got around to installing 3.5 just now. The site I was working on just went live, so I am no longer in testing...
However, above, when you say "When you set [Full backup mode + Sync] APBackup uploads only new files or if file already exists but size or file modification date is different." I thought you fixed it completely for me by NOT setting the archive bit. The program would go through the "source" comparing "size" and "modification date" esssentially "synchronizing" the two stores, without copying everything over each time AND without modifying the archive bit on the source files. That sounded great. Exactly what I was after in minimizing bandwidth and eliminating the alteration of the source files.
You may imagine my frustration when I installed version 3.5 and "Synconize" is unavailable in the main options when I choose "Full Backup (do not clear source archive attribute)"...
Can you read what I originally requested and explain to me how I can do this in version 3.5?
Thank,
Jared
I may need to come back and open another thread, but I thought I would post this here as it has our whole conversation...
I got around to installing 3.5 just now. The site I was working on just went live, so I am no longer in testing...
However, above, when you say "When you set [Full backup mode + Sync] APBackup uploads only new files or if file already exists but size or file modification date is different." I thought you fixed it completely for me by NOT setting the archive bit. The program would go through the "source" comparing "size" and "modification date" esssentially "synchronizing" the two stores, without copying everything over each time AND without modifying the archive bit on the source files. That sounded great. Exactly what I was after in minimizing bandwidth and eliminating the alteration of the source files.
You may imagine my frustration when I installed version 3.5 and "Synconize" is unavailable in the main options when I choose "Full Backup (do not clear source archive attribute)"...
Can you read what I originally requested and explain to me how I can do this in version 3.5?
Thank,
Jared
Re: Understanding the Synchronize Feature
Hello
Please download the latest APBackup bild: 3.5.5531
http://avpsoft.com/download/apbackup.exe
This bug was fixed. (Sync feature works now for FTP FULL backup (Without archive bit))
Please download the latest APBackup bild: 3.5.5531
http://avpsoft.com/download/apbackup.exe
This bug was fixed. (Sync feature works now for FTP FULL backup (Without archive bit))
