Skip to main content
Question

Media agent impacting GDP_xx

  • February 25, 2026
  • 2 replies
  • 14 views

Forum|alt.badge.img

Hey all,

We had two media agents on site A and site B. 
Site A’s media agent died and was replaced by the media agent from site B. 
Site B was consolidated. 

I have a Storage Policy GDP_xx that points to the dead media agent.
I tried to replace the  MediaAgent in the Data Paths of the Properties windows, on the primary copy of the policy (the only copy, there is no other copy) 

We have a Dedup DB reconstruction job for this policy GDP_xx.

How to stop this auto job from running? 
How can I disable the Storage policy?

2 replies

I think the easiest thing to do it associate the clients from the A media agent to B it they have different policies. The GDP is the dedupe policy which in my case is different than my actual storage policy. If that is the case with yours then that may be triggering your DDB reconstruction job if you’r making changes to that.

I would have to know more about your environment to help more. You might want to make a call to support as well.


Scott Moseman
Vaulter
Forum|alt.badge.img+23

If you’re replacing MA-A with MA-B, it’s going to need to recover the DDBs and Indexes which were originally being managed by MA-A.  These processes will happen automatically, but they will need to run if you want to continue using the associated SPs.  Hopefully MA-B has the HW resources available for the additional space since it sounds like it’s running double duty now.

Thanks,
Scott