Skip to main content
Question

Issue backing up client through a media agent without a DDB

  • May 6, 2026
  • 4 replies
  • 19 views

Forum|alt.badge.img+1

We have a client sitting in a DMZ that can successfully connect to media agent 01. However, media agent 01 does not have a DDB. In the job logs we can see the scan phase for the job complete on MA01 but then it fails on the backup phase. We noticed in the logs an attempt to connect to the CVD service on media agent 02 which houses the DDB. The client does not have a path to MA02. In this situation, does commvault require the client to have comms to the DDB media agent MA02? I thought that MA01 would handle connecting to MA02 not the client. How does Commvault handle the data flow in this setup?  Thanks!

4 replies

Forum|alt.badge.img+2

If not properly trained, a client must reach any component as needed.
I recommend following the guide https://documentation.commvault.com/11.40/software/setting_up_network_gateway_connection_using_predefined_network_topology_client_type_is_servers.html to configure an application gateway that allows the client in the DMZ to communicate with the comcell components when needed.


Forum|alt.badge.img+19
  • Vaulter
  • May 6, 2026

Yes the client will reach and open connection with the MA to send the backup stream and connect to its DDB engine, in you case they are not the same backup server that is quite unusual.

You have some options:

  • Move the DDB to your Media Agent 01.
  • Disable dedupe on the client and enable it on the Media Agent 01 (Not 100% sure this work but worth trying)
  • Allow conection from client to MA 02.
  • Convert the MA01 in network proxy to allow the client to reach MA 02 using a Network topopoly.

 


Forum|alt.badge.img+1
  • Author
  • Apprentice
  • May 6, 2026

Ok thanks for the reply’s. I always assumed the initial media agent would do the transfer to the MA with the ddb. Guess not.


Forum|alt.badge.img+19
  • Vaulter
  • May 6, 2026

Well, that is part of the learning path. Most of the time Data Mover and DDB Manager role are located in the same backup server or servers, matching the default or best practice.

I think you can see in the cvd.log of the client how it opens connection to each partition of a ddb that will be hosted in a particular backup server or servers when running a backup operation in the initial phase of it.