Anchoring side effects

Hi,

I have a question about anchoring in the following situation : say I have a folder in "C:\Folder_A\", and I am running an active snapshot #1
I anchor it (C:\Folder_A\) and create a snapshot #2 with #1 as source.

I then decide to unanchor "A" and to anchor another folder "B" instead, "C:\Folder_B\".

When I update snapshot #2 with #1 as source, are files in "C:\Folder_A\" supposed to be copied in snapshot #2 ? And files from "C:\Folder_B\" removed from snapshot #2 ?

Thanks !

 

Hmm. I never was good at logic problems. I believe that the anchoring is program related and not snapshot related. What ever is anchored last will be available to all snapshots. A and/or B depending on your choice.

This is just a guess. I still get stumped on "all bulldogs are dogs, are all dogs bulldogs?"

SourMilk out

 

Yes it is normal.
The anchored files/folders are excluded from the creation/restoration/update of the snapshots.

Panagiotis

 

Thanks. I got burned once but still need anchoring. The trick is to be very careful because anchoring causes no loss of data, but unanchoring has some side effects. Next time I can experiment, I will and report here.

 

A implies B is not the same as B implies A, but is logically equivalent as
(Not B) implies (Not A).
Or A=>B is equivalent to (Not A or B) [if A is not True, Not A is True, so Not A or B also, and if A is true, then B is also true].

Hope this will clear this up ? Maybe not...