Unsolved
2 Posts
0
651
January 26th, 2022 10:00
Networker - Policy action for Clone - Not seeing new clone pool
Hello,
We are migrating off 2 Data Domain (primary + DR) to 2 new Data Domains (Primary + DR). Due to the differences between the old/new Data Domains, we cannot use MTree replication for Networker as we had originally planned.
I have a pool pointing to a destination pool on the new Data Domain device. When I run the workflow it writes to the new primary Data Domain. Now I need to get the clone to the new DR Data Domain destination
So I have defined the new DR Data Domain device, Media Pool and disk volume. When I try to add a "clone" action to the policy, the destination pool I created is not available(visible) for selection. Any ideas on what I may be missing?
Networker 18.2
No Events found!
syprog
2 Posts
0
January 26th, 2022 10:00
I forgot to mention, the Media Disk Volume for the clone pool is "appendable"
bingo.1
2.4K Posts
0
January 26th, 2022 13:00
Before you adjust your configuration (which only YOU see) and you define a new clone workflow (which you probably will only use once) ... why would you not use nsrclone to migrate the volume:
nsrclone -b new_dd_clone_pool source_volume
JChan2020
18 Posts
0
January 26th, 2022 18:00
I think you may have created the new destination pool as a "Backup" pool, not "Backup Clone" pool.
You can go to Media > Media Pools > double-click the new destination pool, then check the Pool type value. If it is "Backup", delete the pool and re-create it as "Backup Clone" pool.
barry_beckers
393 Posts
0
January 27th, 2022 15:00
What are the "differences" between old DDs and new DDs that would not allow for mtree replication? This as the supported range from goes from ddos6.2 all thecwat to ddos 7.7 if memory serves me well? Or are the old dds running an unsupported ddos version?
If mtree replication would have worked, would you then have wanted to use scanner to scan in the data?
As mtree replication is not used, what do you want do with the data on the old dds? Let it run out of retention or is it to be cloned/staged to the new dds as well?
clex_granados
1 Rookie
•
35 Posts
0
February 1st, 2022 14:00
Hello,
the NW 18.2 version is currently end of life, I would recommend you to upgrade to a supported version.
can you check that your DD licensing has replication enabled?
In the data domains, do you have the replication paths configured in the DD Boost section?
CCR is what should be configured in your data zone.
NetWorker does not natively support recovery from a Data Domain appliance where native Data Domain replication technologies have been used to create the NetWorker file tree and data. Only file systems containing NetWorker managed volumes, created by NetWorker backup or cloning methodologies, are supported for any type of data operation.
Only NetWorker Clone Controlled Replication (CCR) is supported for creating data clones, as NetWorker is aware of each copy made and manages the data separately, including retention times per clone instance.