Make sure the aux copy to the “to be new primary” copy finishes before promoting (so that both the copies are in sync). Once promoted, the dash copy will source its data from the new primary copy. So, yes the to-be-copied jobs in the dash copy will be copied from the new primary. 

Hello @Ajal 

You cannot change the source copy while the job is still running. Changing the source copy before the aux copy is finished, say if you killed it, would not copy the jobs that were “to be copied” prior to changing the source copy.

Thank you,
Collin

Hello @Collin Harper @Satya Narayan Mohanty  let me give some more clarity on this 

we had a hyperscal 1.5 library and associated storage policy - for ex - Database_SP

in that we have a primary copy to hyperscal 1.5

dash copy - to secondary location

and now we created a new copy to new hyperscale x - primary_HSX ,

now syncing between primary and primary_HSX is completed , 

but between primary and dash copy is still not finished , 

now my questing if i promote primary_hsx to new primary will my pending copies from old primary to dash copy will be taken from primary_hsx.

what is the recommended way , to wait until it finish completely and switch ?

Hello @Ajal 

We will copy data from whatever is defined as the “Source Copy”. If you change the source before all jobs are copied, the remaining jobs will not be copied.

Thank you,
Collin

Yes, if primary_HSX is completely in sync with primary, then you can kill any running auxcopy job to dash_copy and promote primary_HSX. Once promoted, you can kick off auxcopy for dash_copy, which will then copy the jobs in “partial or to be copied” state from primary_HSX. Just make sure all the “partially copied” or “to be copied” jobs in dash_copy are available in primary_HSX before triggering the promotion.

Which one is the actual asnwer

@Collin Harper - by default the source copy of any secondary copy is primary copy unless explicitly another copy is selected. When a copy is promoted, the new primary automatically becomes the source copy of all the secondary copies in the policy (except for those copies where a source copy is explicitly selected to a different copy).

@Ajal - I synced up with @Collin Harper. The behaviour will be as I mentioned in the previous reply. 
 

Yes, if primary_HSX is completely in sync with primary, then you can kill any running auxcopy job to dash_copy and promote primary_HSX. Once promoted, you can kick off auxcopy for dash_copy, which will then copy the jobs in “partial or to be copied” state from primary_HSX. Just make sure all the “partially copied” or “to be copied” jobs in dash_copy are available in primary_HSX before triggering the promotion.