Avamar: How to Enable Debug Level Logging on the Avamar Data Domain logs (ddrmaint.log)

Caution: IMPORTANT NOTE: Debug must be disabled after the relevant information has been collected. Failure to disable debug may result in Avamar or Data Domain maintenance performance issues.

1. Log in to the Avamar Utility Node as admin.

2. Elevate to root privilege.

3. Load the root keys. See Avamar: How to Log in to an Avamar Server and Load Various Keys for information about loading keys as required.

Note: The rest of this article assumes that the admin keys are loaded.

4. Run the following ddrmaint command to ensure connectivity between the Avamar and the Data Domain (DD):

ddrmaint read-ddr-info 

See APPENDIX A for an example of how the output appears in the ddrmaint.log.

Note: If this command does not return output as expected, contact Dell Technologies Avamar support.

5. Create or edit the ddrmaint.cmd file using vi (or equivalent):

vi /usr/local/avamar/var/ddrmaint.cmd

6. Add the following line to the file:

--debug

7. Save the file.

8. Run a ddrmaint command to force an update to the logs with debug messages:

ddrmaint read-ddr-info 

9. To confirm debug was enabled, review the ddrmaint.log for debug messages:

grep "Debug:" /usr/local/avamar/var/ddrmaintlogs/ddrmaint.log

See APPENDIX B for an example of how the debug output appears in the ddrmaint.log.

10. Once troubleshooting has been completed, remove the debug flag in the ddrmaint.log file.

Failure to disable debug may result in Avamar or Data Domain maintenance performance issues.

APPENDIX A:
Example of the ddrmaint.log before debug is enabled:
(Command run to trigger this output in the log 'ddrmaint read-ddr-info')

Mar 18 12:33:07 avamar1 ddrmaint.bin[13517]: Info: ============================= read-ddr-info cmd start v6.1.0-402 =============================
Mar 18 12:33:07 avamar1 ddrmaint.bin[13517]: Info: read-ddr-info cmdline: '/usr/local/avamar/bin/ddrmaint.bin --flagfile=/usr/local/avamar/etc/usersettings.cfg --password=**************** --server=avamar1 --vardir=/usr/local/avamar/var --bindir=/usr/local/avamar/bin --id=root --vardir=/usr/local/avamar/var --bindir=/usr/local/avamar/bin --sysdir=/usr/local/avamar/etc read-ddr-info'
Mar 18 12:33:07 avamar1 ddrmaint.bin[13517]: Info: read-ddr-info::checkflags read-local: 0
Mar 18 12:33:07 avamar1 ddrmaint.bin[13517]: Info: ============================= read-ddr-info cmd finished

APPENDIX B:
Example of the ddrmaint.log after debug is enabled:
(Command run to trigger this output in the log 'ddrmaint read-ddr-info')

Mar 18 12:33:56 avamar1 ddrmaint.bin[13542]: Info: ============================= read-ddr-info cmd start v6.1.0-402 =============================
Mar 18 12:33:56 avamar1 ddrmaint.bin[13542]: Info: read-ddr-info cmdline: '/usr/local/avamar/bin/ddrmaint.bin --flagfile=/usr/local/avamar/etc/usersettings.cfg --password=**************** --server=avamar1 --vardir=/usr/local/avamar/var --bindir=/usr/local/avamar/bin --id=root --debug --vardir=/usr/local/avamar/var --bindir=/usr/local/avamar/bin --sysdir=/usr/local/avamar/etc read-ddr-info'
Mar 18 12:33:56 avamar1 ddrmaint.bin[13542]: Debug: read-ddr-info::connect addr=10.20.30.40:27000 expert=false
Mar 18 12:33:56 avamar1 ddrmaint.bin[13542]: Debug: read-ddr-info::connect socket=tcp servaddr=10.20.30.40:27000 fd=4 bufsize=60000 isclosed=0
Mar 18 12:33:56 avamar1 ddrmaint.bin[13542]: Debug: read-ddr-info::login - Command type requires login
Mar 18 12:33:56 avamar1 ddrmaint.bin[13542]: Debug: read-ddr-info::connect hasstatusexts=1
Mar 18 12:33:56 avamar1 ddrmaint.bin[13542]: Debug: read-ddr-info::execute setting DB to not flush streams
Mar 18 12:33:56 avamar1 ddrmaint.bin[13542]: Info: read-ddr-info::checkflags read-local: 0
Mar 18 12:33:56 avamar1 ddrmaint.bin[13542]: Debug: read-ddr-info::is_command_successful fault_count: 0
Mar 18 12:33:56 avamar1 ddrmaint.bin[13542]: Info: ============================= read-ddr-info cmd finished =============================