Here is a pre-released tech note that solved my problem and will help others with the same issue...
Bug:
When a drive or path that doesn't exist on a DLO agent is specified for backup, DLO processes take up as much as 80% or more of CPU usage. The DLOChangeLogSVCu.exe and DLOClientu.exe processes specifically will be seen consuming CPU.
Bug ID: 319077
Symptom(s):
Master Log Files: N/A
Media Server Log Files: N/A
Client Log Files: N/A
Workaround:
Examine the backup selection information within the profiles for the affected machines. Identify the use of static drive letters that may not exist on some DLO Agents. For example, suppose that "d:\data" is specified as a backup selection. If this folder doesn't exist for one of the DLO Agents that use that profile, that DLO Agent will experience the CPU usage issue mentioned above.
Instead of specifying an exact drive, use the %LOCALFIXEDDRIVES% macro. For example, if there is a folder called "data" at the root level, add the following entry as a backup selection:
%LOCALFIXEDDRIVES%data
This macro will back up paths such as c:\data, d:\data, e:\data, etc. This applies only to local fixed disk drives.
ETA of Fix:
This issue is scheduled to be addressed in a forthcoming release of DLO.
Another TechNote of interest is here: http://seer.support.veritas.com/docs/275960.htm
and here: http://seer.support.veritas.com/docs/277986.htm
Hope this helps all.
Thanks to Symantec for the note!
Regards,
Robert