Symptoms

IDPA Appliances running version 2.0(includes Avamar version 7.4), 2.1(includes Avamar version 7.5.0), and 2.2(includes Avamar version 7.5.1) have the Java Heap Size on the respective Avamar server set to 2 GB by default. In case of Avamar versions 18.2 and above the Java Heap Size is set to 3 GB by defaultWhen Avamar Server is Upgraded as part of the IDPA upgrade from versions 2.1,2.2 --> 2.3 and above, the Java Heap value on Avamar stays at 2GB and is not changed to 3GB. In general there is no impact with the 2G heap size. But if the system is targeting to do heavy operations, e.g. many backup jobs running in the same time, or backup + replication in the same time, or anything similar, 2G heap size would slow down the Avamar system.Therefore it is recommended to Update the Avamar Java Heap Size to 3GB post IDPA upgrade to versions 2.3 and above.Note: If IDPA was freshly deployed on versions 2.3.x/2.4.x/2.5, then the Avamar Java Heap Size value will be set to 3GB already. The following Symptoms or issues may be seen if the Java on Avamar Server running out of memory due to incorrect Heap Size set:1. All backups stay in waiting client or waiting queued status.2. Some/All backups may not kick off as scheduled. 3. Replication jobs may stay in waiting queued state.

Cause

The Java Heap Size is 3 GB by default in Avamar 18.2 and above so fresh deployments of 2.3 and above would not run into this issue.However, in Avamar 7.5 the default is 2 GB and Avamar upgrade from 7.5 -> 18.2, etc. does not update this value. So 2.1 -> 2.3.x upgrades will still retain the old default and therefore can potentially run into this issue with mass backups in waiting queued state or waiting client state.

Resolution

Verify the current Java Heap Size set on the IDPA-Avamar:1. Login to the Avamar as 'admin' user.2. Run the following command to verify the current value of Java Heap Size set: grep -i "maxJavaHeap" /usr/local/avamar/var/mc/server_data/prefs/mcserver.xml 3. Verify the Avamar Version using the following command and refer the table. mcserver.sh --version IDPA VersionAvamar VersionJava Heap Size (Default)2.07.42 GB2.17.5.02 GB2.27.5.12 GB2.318.23 GB2.418.23 GB2.519.13 GB Please contact IDPA Support and refer this article, If an incorrect value for Java Heap Size was observed in Step 2.

Support Cases