Skip to main content
Answer

Intermittent Check Readiness Issue on Clients (Requires Multiple Attempts)

  • September 1, 2025
  • 2 replies
  • 36 views

Forum|alt.badge.img+5

Hi Community,

I’m experiencing a strange behavior from my CommServe.
When running Check Readiness on some clients, the first attempt (and sometimes the second) shows the status as Disconnected. However, after trying 3 or more times, it finally changes to Ready.

  • Network connectivity is stable with no significant latency.

  • The issue occurs with multiple clients, not just one.

  • Once the client is marked as Ready, backups run without issues.

Has anyone encountered this behavior before?

I appreciate any guidance or similar experiences.

Best answer by Michael Woodward

Hi Community,

I’m experiencing a strange behavior from my CommServe.
When running Check Readiness on some clients, the first attempt (and sometimes the second) shows the status as Disconnected. However, after trying 3 or more times, it finally changes to Ready.

  • Network connectivity is stable with no significant latency.

  • The issue occurs with multiple clients, not just one.

  • Once the client is marked as Ready, backups run without issues.

Has anyone encountered this behavior before?

I appreciate any guidance or similar experiences.

 

To try and confirm what’s going on you can create a one-way firewall group under Manage > Network > Network Topologies.

Add a Server Group for the servers that are having connectivity issues (or just start with one server) and in the Backup Infrastructure put in “My CommServe Computer”   

Then if you navigate to the server and click the ...and go Advanced >  View Network Configuration you should see the contents of a file called FWConfig.txt (it’s in the base directory on the client if you want to go looking).  In the outgoing section you should see an entry like:

<CLIENT> <COMMSERVE>-cs remote_guid=<GUID> type=persistent proto=https cvfwd=COMMSERVE:8403

This will establish a persistent connection between the client and commserve. you can troubleshoot the connections in a log file called cvfwd.log on the client.

2 replies

Erase4ndReuseMedia
Byte
Forum|alt.badge.img+14

What does the log file (CVNetChk.log) on the CommServe, MediaAgent and Client show? 

When there are issues, have you tested communication between the CommServe, MediaAgent and Client via other means (CVPing.exe / Test-NetConnection)?


Michael Woodward
Commvault Certified Expert
Forum|alt.badge.img+12
  • Commvault Certified Expert
  • Answer
  • September 2, 2025

Hi Community,

I’m experiencing a strange behavior from my CommServe.
When running Check Readiness on some clients, the first attempt (and sometimes the second) shows the status as Disconnected. However, after trying 3 or more times, it finally changes to Ready.

  • Network connectivity is stable with no significant latency.

  • The issue occurs with multiple clients, not just one.

  • Once the client is marked as Ready, backups run without issues.

Has anyone encountered this behavior before?

I appreciate any guidance or similar experiences.

 

To try and confirm what’s going on you can create a one-way firewall group under Manage > Network > Network Topologies.

Add a Server Group for the servers that are having connectivity issues (or just start with one server) and in the Backup Infrastructure put in “My CommServe Computer”   

Then if you navigate to the server and click the ...and go Advanced >  View Network Configuration you should see the contents of a file called FWConfig.txt (it’s in the base directory on the client if you want to go looking).  In the outgoing section you should see an entry like:

<CLIENT> <COMMSERVE>-cs remote_guid=<GUID> type=persistent proto=https cvfwd=COMMSERVE:8403

This will establish a persistent connection between the client and commserve. you can troubleshoot the connections in a log file called cvfwd.log on the client.