HOWTO: How to use the vomgather utility to gather logs for Veritas Operations Manager (VOM).


Requirement to collect VOM specific logs from VOM Central Server (CS) and/or Managed Host (MH).


During troubleshooting, running the vomgather tool will create an archive of VOM specific configuration files and logs.  This is automatically included when collecting an enhanced SORT vxexplorer and it is seldom necessary to run it standalone.  See Related Articles below on using the SORT vxexplorer.

Error Message

Various troubleshooting scenarios.




Vomgather is a utility that can be executed from the command line interface that is included with Veritas Operations Manager (VOM) Central Management Server (CS) and Managed Host (MH) versions 4.0 and above. It gathers configuration files and log files that are specific to VOM and can be used to gather data from both the CS and an MH.


As mentioned above, this utility is automatically invoked by default when collecting a SORT vxexplorer (Unix only at the time of this writing).  This is highly recommended as typically a vxexplorer and vomgather troubleshooting archive are required when resolving VOM-related issues.  Since the function of displaying information in the VOM GUI is the result of mechanisms at the MH and CS, it is recommended that the SORT vxexplorer (vomgather) be run at both hosts (sometimes including a working MH environment).


When running VOM at a Windows CS and/or MH, it is recommended that vomgather be run on both the CS and the MH along with the Windows VxExplorer. For more information about the Unix vxexplorer and Windows VxExplorer utilities, please see the Related Articles section below.

The perl script is included with Unix and Windows and is located in the following directories:
Unix Directory:
# /opt/VRTSsfmh/adm/

Windows Directory:
C:\Program Files\Veritas\VRTSsfmh\adm\


To execute the vomgather script on UNIX, perform the following command:

# cd /opt/VRTSsfmh/adm
# ./ --dir <output_directory>
Note: The above command assumes perl is in the PATH statement for execution.

To execute the vomgather script on Windows, open a command prompt perform the following command:

cd C:\Program Files\Veritas\VRTSsfmh\adm\
perl --dir <output_directory>
Note: The above command assumes perl.exe is in the PATH statement for execution.

Example for Unix:

# ./ --dir /var/tmp/vomgather,d

Example for Windows:

C:\Program Files\Veritas\VRTSsfmh\adm> "c:\Program Files\Veritas\VRTSsfmh\bin"\perl.exe --dir C:\vomgather.d

The output file, vom_backup_sol_4.0.1097.0.tar.gz for UNIX and vom_backup_win_4.0.1097.0.tar.gz for Windows, will be generated in the directory specified on the command line ( --dir <output_directory> ). In the examples above the output directory is specified as /var/tmp/vomgather for UNIX and C:\vomgather for Windows.

If a case has already been opened with Symantec Technical Services, the vomgather output file should be renamed to include the existing eight (8) digit case number and if it is the CS or MH such as:


or ...



Once the file is renamed, it can be provided to the Symantec Technical Support Engineer.  Typically this will be less than the 10 meg email attachment limitation and can be attached to an email to the technical support case otherwise it may be ftp'ed to the Symantec ftp site or fileshare (see Related Articles below).


In versions 4.x, the VOM database is automatically collected from the CS.  This may sometimes inflate the size of the vomgather archive.  In version 5.0, a HotFix is available to replace vomgather with a new version that will not collect the database by default (HF050001960-05).  Subsequent versions will include this fix.


This HotFix is available at the SORT website at:

(direct link: )

(this is a Unix and Windows patch)


After applying this patch, it will be necessary to use the parameter "--full" if it is desired to collect the VOM database from the CS.




# ./ --dir /var/tmp/vomgather.d --full

Applies To

Any supported VOM version on any supported platform.

Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)