We have created a new library. we were trying to associate it to an existing deduplication engine (new data path) but its not avaiable.
Can anyone help understand why?
Best answer by Mike Struening
Quick question of my own:
Is this Storage Policy using a Global Deduplication Policy set somewhere else? You SHOULD be able to add another library to a Dedupe copy, though iof that copy is subscribed to a Global DDB, then you need to add it to the Global DDB copy, not the child.