Skip to main content
Solved

Could not reach Media Agent [] with hostname


Forum|alt.badge.img+8

Hello Team,

I have issue on my media agent. Services are running and check raidness succesfully. I am unable to browse and restore my backup data  it  failes as Could not reach Media Agent [GAR-PND-PRD-FPS-MA03] with hostname [PGARAPPCVM13] 

I have rebooted media agent twice.I have checked the Index cache there is about 900GB free sapce.

 

Best answer by ETO

Hello I ahve rebooted the media agent again. I guess the index rebuilded it self. It is working fine now

THanks

View original
Did this answer your question?

Forum|alt.badge.img+7
  • Vaulter
  • March 9, 2025

Hi ​@ETO,

 Could you please confirm if the Media agent is ready for operation? 

Additionally, I would like to know what you are seeing in the CS\Browse log while starting the browse process. 

Regards,

Wasim


Forum|alt.badge.img+8
  • Byte
  • March 9, 2025

Hi ​@Wasim 

Yes Media agent is ready, We are able to take incremental and Full backup. I noticed that Shyntetic Full backup also fails.I have checked CVD logs in the media agent logs. It see some time out about index server. I have rebooted the media agnet again. I could browse the jobs. But Shyntetic backup still fails due to index issue


Emils
Vaulter
Forum|alt.badge.img+13
  • Vaulter
  • March 10, 2025

Hi ​@ETO 

Can you please confirm the Indexing server used for the client?

You can check this by following:

  1. Navigate to the client properties in the CommCell Console.
  2. Within the client properties, find the 'Index' tab to view the index server details

Confirm the MediaAgent shown in the Index Tab, and ensure the client (PGFKFTPSTA01) is able to reach the MediaAgent shown as the Index server?

Use the cvping command from the client to the MediaAgent on ports 8400 and 8403 to ensure network connectivity using both IP and hostname seen in the commcell and in both direction.

Thanks

 


Forum|alt.badge.img+8
  • Byte
  • March 10, 2025

Hello I ahve rebooted the media agent again. I guess the index rebuilded it self. It is working fine now

THanks


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings