This past week - I have been updating a number of jobs from being simple "Backup" profiles to a Mirror Right profile.
Since we am now moving specific filesets out to Crashplan - I want to ensure that when I delete/change or alter ANYTHING from the Source side - the destination gets 100% identical changes.
Now - as an example - I have a source folder on a local PC with my active documents. Inside the main root folder are 20 or so sub folders. Since this "source" has been subjected to a normal SyncBack "backup" profile for a long while - the destination on my server - has these 20 subfolders - jammed with stuff placed over the last year.
Now - yesterday - I did some severe clipping to this local folder structure on local PC and changed my SyncBack profile to be a Mirror Right - hoping that after my pruning session on Source - the next run of this profile would create the Mirror image on the destination.
Turns out - it creates the mirror - but does nothing with the other crap that is out on the destination. Instead of one root and now 8 main subfolders (after my prune session on Source) - I see a root folder and about 28 subs out in destination.
Seems Syncback ignores everything on Dest that has been changed on Source - creating a hell of a mess to clean up on Dest now.
Why is it down this way? Is it a safety hatch to ensure some user (not paying attention) does not torch a pile of things in Dest? Even if (in my case) - I want them torched?
I then saw the Folders area under the Decisions area - and realized that Syncback will ignore/skip all folders that are on Dest but not on Source - unless Prompt Me is selected via a manual run.
Well - I tried that too - switched the behavior to "Prompt Me" and started a manual run. One by one - each folder on Dest (that was not on Source) was placed on screen - with 4 choices - for each one - I clicked Delete...
This went on for 15 mins - but when it was all done - none of the folders that I specifically said Delete - were deleted on Dest.
Is this a rights issue? Or a "cannot delete folder with files in it" issue or what?
What do I have to do - to make Mirror Right - actually be a true Mirror? I need this profile to be a totally destructive force that deletes EVERYTHING from Dest that is not on Source at every run and be 100% certain that Dest ONLY contains a Mirror image of Source?
Especially when I am very clear that I am fine with burning data that I do not care about.
Cheers,
VP
Since we am now moving specific filesets out to Crashplan - I want to ensure that when I delete/change or alter ANYTHING from the Source side - the destination gets 100% identical changes.
Now - as an example - I have a source folder on a local PC with my active documents. Inside the main root folder are 20 or so sub folders. Since this "source" has been subjected to a normal SyncBack "backup" profile for a long while - the destination on my server - has these 20 subfolders - jammed with stuff placed over the last year.
Now - yesterday - I did some severe clipping to this local folder structure on local PC and changed my SyncBack profile to be a Mirror Right - hoping that after my pruning session on Source - the next run of this profile would create the Mirror image on the destination.
Turns out - it creates the mirror - but does nothing with the other crap that is out on the destination. Instead of one root and now 8 main subfolders (after my prune session on Source) - I see a root folder and about 28 subs out in destination.
Seems Syncback ignores everything on Dest that has been changed on Source - creating a hell of a mess to clean up on Dest now.
Why is it down this way? Is it a safety hatch to ensure some user (not paying attention) does not torch a pile of things in Dest? Even if (in my case) - I want them torched?
I then saw the Folders area under the Decisions area - and realized that Syncback will ignore/skip all folders that are on Dest but not on Source - unless Prompt Me is selected via a manual run.
Well - I tried that too - switched the behavior to "Prompt Me" and started a manual run. One by one - each folder on Dest (that was not on Source) was placed on screen - with 4 choices - for each one - I clicked Delete...
This went on for 15 mins - but when it was all done - none of the folders that I specifically said Delete - were deleted on Dest.
Is this a rights issue? Or a "cannot delete folder with files in it" issue or what?
What do I have to do - to make Mirror Right - actually be a true Mirror? I need this profile to be a totally destructive force that deletes EVERYTHING from Dest that is not on Source at every run and be 100% certain that Dest ONLY contains a Mirror image of Source?
Especially when I am very clear that I am fine with burning data that I do not care about.
Cheers,
VP