Good day all
This one is a bit complicated, so will try keep it as brief as I can.
The customer has a faulty storage device with the backup data on it.
They’ve received a loan VAST unit which uses it’s own deduplication engine in addition to the Commvault dedupe in place.
We would like to turn the Commvault deduplication off as we’re having errors on the DDB which may require us to seal it.
The concerns I have are below, and I’m hoping to get some clarity on it.
The faulty storage and VAST storage are in the same Data Centre (DC1).
We want to turn DDB off in this DC and do a Move Mount Path(s) from the faulty storage to the VAST.
At the same time, new backups are running to the VAST device on different Mount Paths.
When this is all complete and the faulty storage is replaced (it won’t have it’s own DDB capabilities, so Commvault will handle that), we will move the VAST Mount Paths back to this storage.
With Commvault DDB off, does non-deduplicated data get deduplicated during a ‘Move Mount Path’ operation by Commvault if DDB is enabled prior to the operation?
Following on from this, we have backup data in another Data Centre (DC2).
The Aux copies from the VAST will need to make a secondary copy to DC2, and DC2’s backup data makes a secondary copy to DC!1 (VAST).
With no deduplication enabled in DC1 (VAST) does the DASH copy option handle deduplication regardless if it’s enabled on the storage?
I hope this makes sense.
Best answer by Mike StrueningView original