Avamar: Could not save console server data to server (Symptom Code 22402) Resolution Path

This event can be logged as a Dial Home Event, an MC event or seen on the command line of the Avamar Utility Node: 

Symptom: 22402, Description: Could not save console server data to server.

The Management Consoler Server (MCS) flush is a backup of the MCS server data.

An MCS flush is performed daily.

If a flush is not successful, a 22402 event is triggered.

There are many factors to consider when troubleshooting MCS flush failures on an Avamar grid. The problem may be intermittent, depending on the network and Avamar Server load. 

This article helps to lead the reader through some of the most common MCS flush problems and how to determine when and why the failure occurred.

Validate that each troubleshooting steps below are true as per the environment.

Each step provides instructions or a link to a document, to eliminate possible causes and take corrective action as necessary.

The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution.

Do not skip any steps.

Step 1: Log in to the Avamar Utility Node as admin and load the admin keys. For instructions on loading keys see Avamar: How to Log in to an Avamar Server and Load Various Keys.

Step 2: Verify if the mcserver.xml file has the correct permissions: Avamar: Could not save console server data to server caused by incorrect file permissions

Step 3: Verify if there are no java utilization issues on the utility node due to port scanners: Avamar: "Could not save console server data to server" due to port scanners causing high Java CPU Utilization

Step 4: Verify if there are no multiple mcserver.xml files in the /prefs directory: Avamar: Symptom 22402 - Could not save console server data to server caused by multiple mcserver.xml files in the prefs directory

Step 5: Verify that the 'Dispatchers' are not suspended on the Avamar server: Avamar: Symptom 22402 - Could not save console server data to server caused by suspended dispatchers

Step 6: Verify if there are no Java Heap Out of Memory issues due to large NVRAM files: Avamar: MCS receives "OutOfMemory" messages

If none of the solutions above corrected the issue, Create a service request.

For a step-by-step flowchart representation of the troubleshooting guide, see the attached document.