Follow

arcserve-KB : Arcserve UDP 6.5 - Windows Event Log integration

Last Update: 2017-11-15 10:49:12 UTC
Description:
Customers using either the Windows Event log direct, or using a 3rd party monitoring & event management tools would like for Arcserve UDP to integrate with the Windows Event Log.


Solution:
Arcserve UPD 6.5 contains an experimental feature that allows for integration with the Windows Event Log.
This feature is not enabled by default.
It can be enabled with the CmdUtil.exe and the /evtlog parameter – as shown below.

 
Text version of this screenshot:
 

D:\Program Files\Arcserve\Unified Data Protection\Engine\BIN>cmdutil /evtlog /?
Usage: evtlog

Remarks:
Register or remove event log source of Arcserve UDP.

/reg - Register event log source of Arcserve UDP.
/e[w,i] - Options of event log.
/rm - Remove event log source of Arcserve UDP.

Examples:
cmdutil.exe /evtlog /reg /e
Register to write error messages to system event log.

cmdutil.exe /evtlog /reg /ew
Register to write error and warning messages to system event log.

cmdutil.exe /evtlog /reg /ewi
Register to write error, warning and information messages to system event log.

cmdutil.exe /evtlog /rm
Remove event log source of Arcserve UDP. 

 
The source of the event log entries will say “Arcserve UDP”.

  • Windows Agent-based backup jobs will integrate with the Event Log on the Agent node itself.
  • Agentless backup jobs will integrate with the Event Log on the Proxy node.
  • Tasks that are initiated on the RPS will integrate with the Event Log on the RPS node.
  • Linux Agent-based nodes don’t have any Event Log integration.

It is recommended to use this feature with UDP 6.5 Update 2 or later, because before that version all Event ID's had the value 100 (information), 101 (warning) and 102 (error). After upgrading to UDP 6.5 Update 2 the Event ID's will show unique values, with Errors between 10000 and 19999, Warnings between 20000 and 29999 and Informational entries over 30000:


Known issue:
If the Windows Event Viewer is open during an upgrade of the UDP software, then some DLLs remain locked and cannot be upgraded before Event Viewer is closed. The Windows Installer framework will automatically capture this condition – but given that it has no interactive prompt, it will instead require a reboot at the end of the installation procedures. Without the Event Log registration there should not be a requirement for reboots of UDP Agent and RPS nodes. Customers are advised to close the Event Viewer before any update / upgrade, to avoid being prompted for a reboot.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments