We have a very large, Infinite retention Storage Policy, associated to Storage Pool “Pool1”.
It has grown to the point, that we will soon be creating another Storage Pool and Storage Policy. Let’s call these Pool2.
All clients from Pool1 will be migrated to Pool2, so Pool1 will stop receiving any fresh data, since Pool2 will start receiving it all.
The question I have is around the massive, leftover DDB’s from Pool 1. They are 2 x 1.8 TB and are hosted on the two Media Agents associated with Pool1.
Since Pool1 will stop receiving data, I am keen to decommission the Pool1 Media Agents - noting that the Secondary-copy Cloud-based backup data can be accessed from a number of Media Agents and so it does not necessarily have to be the Pool1 Media Agents. It can be any Media Agents, provided they are mapped to the relevant Cloud Library Mount Points.
So the questions I have are :-
1 - What do we do with these large, legacy DDB’s?
I understand we need to keep for Commvault Sync operations. Any other reason?
2 - What activity will continue against these DDB’s once I migrate all clients away from them?
I’m aware a DDB BAckup will likely run. Anything else?
3 - Should I seal them, once all clients have migrated across?
This is an Infinite retention SP, but I wonder if sealing will further reduce potential CPU or memory overhead.
4 - Would anyone know the likely CPU overhead of leaving these DDB’s lying around?
This would factor in to which Media Agent I could move them to.