Dell - Defect ID: 26581
Avamar: Replication verification testing fails due to suspended dispatchers on the target grid.

Symptoms

If adding, or editing a replication destination, the verification appears to get stuck: MC UI: AUI:

Cause

The dispatchers on the Avamar target grid are in a suspended state so the connection cannot be established.If suspended, the Avamar grid prevents new dispatchers being activated for use for backups, restores, and replications. This can be verified by running the status.dpn command on the target grid Avamar Utility Node. For Example: status.dpn Thu Mar 13 02:15:23 GMT 2025 [AVANAR-UTIL] Thu Mar 13 02:15:33 2025 UTC (Initialized Tue Dec 7 16:14:04 2021 UTC) Node IP Address Version State Runlevel Srvr+Root+User Dis Suspend Load UsedMB Errlen %Full Percent Full and Stripe Status by Disk 0.0 192.168.255.2 19.12.0-186 ONLINE fullaccess mhpu+0hpu+0hpu 0 true 0.07 27024 25487149 3.6% 3%(onl:513) 3%(onl:494) 3%(onl:497) 0.1 192.168.255.3 19.12.0-186 ONLINE fullaccess mhpu+0hpu+0hpu 1 true 0.11 28164 16880311 3.6% 3%(onl:486) 3%(onl:474) 3%(onl:521) 0.2 192.168.255.4 19.12.0-186 ONLINE fullaccess mhpu+0hpu+0hpu 0 true 0.03 26688 18351447 3.6% 3%(onl:501) 3%(onl:501) 3%(onl:502) 0.3 192.168.255.5 19.12.0-186 ONLINE fullaccess mhpu+0hpu+0hpu 0 true 0.03 26355 17138335 3.6% 3%(onl:509) 3%(onl:492) 3%(onl:490) Srvr+Root+User Modes = migrate + hfswriteable + persistwriteable + useraccntwriteable System ID: 12345667890@00:60:16:B5:D8:44 All reported states=(ONLINE), runlevels=(fullaccess), modes=(mhpu+0hpu+0hpu) System-Status: ok Access-Status: full Last checkpoint: cp.20250312080741 finished Wed Mar 12 08:08:18 2025 after 00m 37s (OK) Last GC: finished Wed Mar 12 08:00:37 2025 after 00m 13s >> recovered 2.22 MB (OK) Last hfscheck: finished Wed Mar 12 08:06:59 2025 after 05m 34s >> checked 2012 of 2012 stripes (OK) Maintenance windows scheduler capacity profile is active. The backup window is currently running. Next backup window start time: Thu Mar 13 20:00:00 2025 GMT Next maintenance window start time: Thu Mar 13 08:00:00 2025 GMT This output confirms that the dispatchers are suspended (The entries for each node is "true" in the "Suspend" column)

Resolution

On to the target Avamar Utility Node: 1. Run the avmaint resume command: avmaint resume Note: No output is returned from the avmaint resume command. 2. Verify that the dispatchers are now not suspended by rerunning the status.dpn command: status.dpn Thu Mar 13 02:24:04 GMT 2025 [AVAMAR-UTIL] Thu Mar 13 02:24:14 2025 UTC (Initialized Tue Dec 7 16:14:04 2021 UTC) Node IP Address Version State Runlevel Srvr+Root+User Dis Suspend Load UsedMB Errlen %Full Percent Full and Stripe Status by Disk 0.0 192.168.255.2 19.12.0-186 ONLINE fullaccess mhpu+0hpu+0hpu 0 false 0.07 27024 25487149 3.6% 3%(onl:513) 3%(onl:494) 3%(onl:497) 0.1 192.168.255.3 19.12.0-186 ONLINE fullaccess mhpu+0hpu+0hpu 1 false 0.11 28164 16880311 3.6% 3%(onl:486) 3%(onl:474) 3%(onl:521) 0.2 192.168.255.4 19.12.0-186 ONLINE fullaccess mhpu+0hpu+0hpu 0 false 0.03 26688 18351447 3.6% 3%(onl:501) 3%(onl:501) 3%(onl:502) 0.3 192.168.255.5 19.12.0-186 ONLINE fullaccess mhpu+0hpu+0hpu 0 false 0.03 26355 17138335 3.6% 3%(onl:509) 3%(onl:492) 3%(onl:490)) Srvr+Root+User Modes = migrate + hfswriteable + persistwriteable + useraccntwriteable System ID: 123456789@00:60:16:B5:D8:44 All reported states=(ONLINE), runlevels=(fullaccess), modes=(mhpu+0hpu+0hpu) System-Status: ok Access-Status: full Last checkpoint: cp.20250312080741 finished Wed Mar 12 08:08:18 2025 after 00m 37s (OK) Last GC: finished Wed Mar 12 08:00:37 2025 after 00m 13s >> recovered 2.22 MB (OK) Last hfscheck: finished Wed Mar 12 08:06:59 2025 after 05m 34s >> checked 2012 of 2012 stripes (OK) Maintenance windows scheduler capacity profile is active. The backup window is currently running. Next backup window start time: Thu Mar 13 20:00:00 2025 GMT Next maintenance window start time: Thu Mar 13 08:00:00 2025 GMT 3. Retry the verification test again. A Successful test shows the following: MC UI: AUI: If the issue remains unresolved, further investigation is required. Return to the knowledge base for additional troubleshooting resources.

Support Cases