Files not in list, not removed from sync destination

Use this forum for help with AISBackup
Post Reply
DnlPbl
Posts: 32
Joined: Mon Oct 24, 2005 9:57 pm

Files not in list, not removed from sync destination

Post by DnlPbl »

In both types of one-way sync jobs...
Copy new and changed files (Older or newer)
Copy new and newer files only
...the following scenario seems to produce unexpected results.

1) Run a one-way sync job that is supposed to delete files from destination, which are not in the source location.
2) Modify that sync job's files and folders list by removing some folders/files
3) Run the sync job again. When run interactively, AISBackup does not prompt to delete those folders/files that were removed from the job's list. When run by shortcut with the paramaters "CFZ", the folders/files also remain.

If this is a bug, can it be fixed?
On the other hand, if this is the expected behavior, is it necessary to make a formal feature request to have this accommodated?

Windows XP SP3
aisBackup 2.8.0.378
Barry
Site Admin
Posts: 1529
Joined: Tue Aug 20, 2002 3:16 pm

One way sync

Post by Barry »

Hi

This behaviour is by design

AISBackup will only remove files from the destination from the folders (and sub folders) selected for copy. If this is not the case please supply a simple example.

Additionally for two way synchronisation:

AISBackup maintains a list of folders that exist on 'both sides' to determine whether a folder has been deleted or added to one of the 'sides'. When the both way synchronize job is first run AISBackup assumes that no folders have been deleted (which is true). When the list of files selected for synchronize if modified AISBackup resets the job to the first time run state as removing a folder from one of the 'sides' would cause it to be deleted from the 'other side'; it was decided that this could be disastrous if for example you removed your video folder purely because it was too big to synchronize.

Barry
DnlPbl
Posts: 32
Joined: Mon Oct 24, 2005 9:57 pm

Post by DnlPbl »

Ok, so it is intended behavior. Your explanation of potential disaster in a two-way sync makes plenty of sense - such default behavior in a two-way sync would be disastrous, since the deletion would be two-way, just like all job activity.

However, in a one-way sync, there is no such risk, as the deletion will only be one-way. Further, it does not have to be default behavior - a check box option would do fine.

Doesn't it make sense to have an option to delete files from destination, which have been removed from the files and folders list? This way you can have the destination exactly mirror the files and folders list - very useful.

Before seeing otherwise, it seemed a matter of course that it would work this way. Naturally, a subfolder within a folder to be synced, that goes unselected at time of sync job creation, will not be copied to the sync destination. Yet once that job is run, and a subfolder is deselected from the files and folders list, why should it persist in the sync destination?

What are your thoughts?
DnlPbl
Posts: 32
Joined: Mon Oct 24, 2005 9:57 pm

Post by DnlPbl »

Hey Barry,

Any news on this?
Post Reply