We have 2 commcell running V9 SP11a.
In the first infrastructure, we have 12 media agent with local deduplicated copy. (One Storage Policy per site)
Those local magnetic Library are synchronized every night with a central media agent in our datacenter using DASH. (a synchronous copy in SP pointing to a global dedup)
We would like to :
- Migrate those media agent in our second infrastructure, with ensure that we don't have to reseed the global ddbstore (reuse of block of backup perform by the 1rst CommCell)
- Change the media agent hosting the Global DDB in datacenter.
The media agent actually hosting the global database must stay in the first infrastructure.
According the reading to the BOL CommCell Migration :
I understand that on all office media agent migrated from 1rst infra to the 2nd infra, DDB Store will be sealed so future job will seed a new store. So we must ensure we have sufficient space on office MagLib. The central DDB will be also sealed in the new infra and cannot be used to reference block, we must re-seed the central DDB.
I also understand that I must manually copy the maglib and the sidb store to a new media agent according to the IMPORT METADATA ON THE DESTINATION COMMCELL section in the migration process.
So according to our previous question, my answers should be :
Yes, we must re-seed the global DDB.
Yes, we can change the media agent hosting the ddb when migrating from one commserve to another.
Does anyone have already perform this operation and can confirm/infirm ?