Hello team
We’re going to replace the on-premises disk library that use for 2nd copies with a new immutable container that created in Azure Blob
if it’s possible to migrate old data(dash copies) that currently store on the on-premises disk to this new immutable container by creating a new copy that takes the old 2nd copy as source and destination points to this new immu container for two scenarios :
- 2nd copy with mixed retentions
- 2nd copies have the same retention
#1 If yes, once migration complete, can we run CV workflow to convert it to CV Worm storage lib or we should config the new cv lib to worm before migrate data?
#2 More concern about the dash copies with mixed retention and data will not get aged until all jobs meet retention, should group copies with same retention into a dedicated immutable containers first?
#3 Once all set (data migrate to this new immu storage and convert to worm mode in CV), does subsequence 2nd copies will continue running into this new immu storage or we have to wait until DDB sealed and new one get created ?
