NetWorker: How to Enable Debug Logging for the vRealize Data Protection Extension

Prerequisites and Important Notes

• Understand the logging hierarchy — The edp_4_vcac.log file uses the same log level as the level configured in the vRealize Orchestrator Control Center under configure logs. The default log level is INFO. Setting the log level directly in the log4j.xml file takes precedence over the Control Center setting.
• Configure the Control Center first — If log parameter changes are needed in the Control Center, make those changes before editing log4j.xml. Saving log parameters in the Control Center overwrites any manual changes made to log4j.xml.

Enable Debug Logging

1. Open the log4j.xml file on the vRealize Orchestrator (vRO) application server:

   vi /var/lib/vco/app-server/conf/log4j.xml

2. Find the com.emc.edp4vcac category block in the file.
3. Change the priority value to DEBUG:

   <category additivity="false" name="com.emc.edp4vcac">
       <priority value="DEBUG"/>
   </category>

4. Save the file and close the editor.

Apply the Changes

1. Restart the vco-server service to apply the updated log level:

   systemctl restart vco-server

2. If the environment has multiple vRO nodes, repeat Steps 3–7 on every node to enable debug logging consistently across the cluster.

Verify Debug Logging

1. Perform a backup or restore operation through the vRealize Data Protection Extension to generate log entries.
2. Open the edp_4_vcac.log file and confirm that DEBUG-level entries now appear:

   tail -f /var/lib/vco/app-server/logs/edp_4_vcac.log

Disable Debug Logging (After Troubleshooting)

1. After troubleshooting is complete, change the priority value back to the default level of INFO to reduce log volume and disk usage:

   <category additivity="false" name="com.emc.edp4vcac">
       <priority value="INFO"/>
   </category>

2. Restart the vco-server service on all nodes to apply the change:

   systemctl restart vco-server