LOG Locations in Backup Exec:
VX Gather:
Windows 2k/2k3/XP:
C:\Documents and Settings\<username>\Local settings\Temp\<case_number>_<machine_name>.cab
Windows 2008 and later:
C:\Program Data\Symantec\Backup Exec\<case_number>_<machine_name>.cab
NOTE:The Program Data folder is a hidden folder. If the Program Data folder is not visible, refer to the Microsoft Windows documentation for instructions on how to display hidden folders.
Usage: The Symantec Gather Utility (VxGather.exe) captures the most common diagnostic and historical files necessary for troubleshooting purposes. By default the Symantec Gather Utility will find Windows Event Logs, Backup Exec Installation logs, Backup Exec internal application logs, and when present, the Symantec Gather Utility also executes Bediag.exe. These files can then be used either by Symantec Technical support to resolve the issue more quickly.
When troubleshooting an issue with Backup Exec, it may be necessary to review diagnostic logs from the media server. The Symantec Gather Utility simplifies this process by creating and compiling a compressed file (CAB) that includes various system log files that can be sent to technical support.
____________________________________________________________________________________________________________________
INSTALLATION LOGS:
Version: 10.x and prior - BKUPINST.LOG
• C:\Windows\
Version: 11x to 2010 Rx - BKUPINST.HTM and RAWSINST.HTM
• For Windows 2003 and prior: C:\Documents and Settings\All Users\Application Data\Symantec\Backup Exec\Logs\
• For Windows 2008 and later: C:\ProgramData\Symantec\Backup Exec\Logs\
Version: 2012 - BKUPINST2012.HTM and RAWSINST.HTM
• For Windows 2003 and prior: C:\Documents and Settings\All Users\Application Data\Symantec\Backup Exec\Logs\
• For Windows 2008 and later: C:\ProgramData\Symantec\Backup Exec\Logs
NOTE:The Application Data and Program Data are hidden folders. If the Application Data or Program Data folders are not visible, refer to the Microsoft Windows documentation for instructions on how to display hidden folders.
Usage: Errors during the BE or RAWS installation.
____________________________________________________________________________________________________________________
THIRD PARTY LOGS(Logs created during the installation of Backup Exec):
msrptviewer_install.log
• For Windows Server 2003 and prior: C:\Documents and Settings\All Users\Application Data\Symantec\Backup Exec\Logs\
•For Windows Server 2008 and later: C:\ProgramData\Symantec\Backup Exec\Logs\
Usage: It helps in finding out the reason for the installation failure due to issues related to Microsoft Report Viewer Redistributable (.Net Framework)
MSXML6.log
• For Windows Server 2003 and prior: C:\Documents and Settings\All Users\Application Data\Symantec\Backup Exec\Logs\
• For Windows Server 2008 and later: C:\ProgramData\Symantec\Backup Exec\Logs\
Usage: It helps in finding out the reason for the installation failure due to issues related to MSXML Parser.
Pre-Install_BEDiag.log
• For Windows Server 2003 and prior: C:\Documents and Settings\All Users\Application Data\Symantec\Backup Exec\Logs\
• For Windows Server 2008 and later: C:\ProgramData\Symantec\Backup Exec\Logs\
Usage: Backup Exec runs Bediag.exe and diagnoses the basic configuration of the server on which the media server has to be installed.
EVEInstall.log
• For Windows Server 2003 and prior: C:\Documents and Settings\All Users\Application Data\Symantec\Backup Exec\Logs\
• For Windows Server 2008 and later: C:\ProgramData\Symantec\Backup Exec\Logs\
Usage: The Enterprise Vault installation log. It is created only if Archive Option is installed.
dd_dotnetfx35install.txt
- Directory = C:\WINDOWS\Microsoft.NET\Framework\v3.5\Microsoft .NET Framework 3.5 SP1\Logs\
- Filename = dd_dotnetfx35install.txt
Usage: It is .NET Framework installation error log.
______________________________________________________________________________________________________________
IPLOPS LOG:
• For Windows Server 2003 and prior: C:\Documents and Settings\All Users\Application Data\Symantec\Backup Exec\Logs\
• For Windows Server 2008 and later: C:\ProgramData\Symantec\Backup Exec\Logs\
Filename = IPLOPS.log
Usage: Errors during the BE license installation.
______________________________________________________________________________________________________________
BEPUSHES.LOG:
Windows 2000 Media server
C:\Winnt\System32
Windows 2003 Media server
C:\Windows\Sytem32
Usage: It helps in finding out the reason for the failure of push installation of RAWS or any update to the remote server from the media server.
______________________________________________________________________________________________________________
SG Mon LOG:
Backup Exec Media Server:
C:\Program Files\Symantec\Backup Exec\Logs\ <server name>SGMon.log
Backup Exec Remote Servers:
C:\Program Files\Symantec\Backup Exec\RAWS\Logs\<server name>SGMon.log
Usage: SGMON.EXE is a debug tool used to view active debugging information. SGMON can be used to monitor some parts of the Backup Exec (tm) activity that other logging methods do not monitor.
SGMon, also called Backup Exec Debug Monitor (BEDM), is a standalone diagnostic tool that automatically captures debug output from Backup Exec, Third party application, and saves it in one debug log as <server name>SGMon.log
This log file contains debug statements for the following Backup Exec Services and options:
- Backup Exec Job Engine
- Backup Exec Remote Agent for Windows
- Backup Exec Browser
- Server
- Utility
- Device and Media
- Catalog
- Administration console
- Management
- SDR Disk Wizard and Third party application.
It can help troubleshoot issues and can help Symantec Technical Support to diagnose and repair problems related to Backup Exec and Third party applications.
______________________________________________________________________________________________________________
Services and Registry Debugging Logs:
Backup Exec Media Server:
Backup Exec Job Engine Service:
• Directory = \Program Files\Symantec\Backup Exec\Logs
• Filenames = <ServerName>-BENGINExx.Log
Backup Exec Management Service:
• Directory = \Program Files\Symantec\Backup Exec\Logs
• Filename = Management-<Date>.log
Backup Exec Remote Servers:
Backup Exec for Remote Agent:
• Directory = \Program Files\Symantec\Backup Exec\RAWS\Logs
• Filename = <Server Name>-BEREMOTExx.LOG
______________________________________________________________________________________________________________
ADAMM LOG:
• Directory = \Program Files\Symantec\Backup Exec\Logs
• Filename = ADAMM.LOG
Usage: When Symantec Backup Exec (tm) for Windows Servers sees a tape device attached to a SCSI or to an Integrated Drive Electronics (IDE) controller, it records specific information in a log called ADAMM.LOG. This log file contains very useful information in configuring robotic libraries and tape drives for backup operations within Backup Exec.
When the Backup Exec services start up, a new entry is appended to the ADAMM.LOG file. This way, a history of the devices that have been attached to the server is kept.
______________________________________________________________________________________________________________
TILDBG LOG:
Hardware Related configurations:
• Directory = \Program Files\Symantec\Backup Exec\Logs
• Filename = TILDBG.TXT
Usage: Used to find the hardware related configurations.
______________________________________________________________________________________________________________
DBRECOVER LOG:
• Directory = \Program Files\Symantec\Backup Exec\Logs
• Filename = dbrecover.log
Usage:It is a database recovery log. It keeps a record of all changes made to a database and can be used if the device and media service fails to start.
______________________________________________________________________________________________________________
CRF LOG:
• For Windows Server 2003 and prior: C:\Documents and Settings\All Users\Application Data\Symantec \CRF
• For Windows Server 2008 and later: C:\ProgramData\Symantec\Backup Exec\ Symantec \CRF
Filename: CRF.LOG
Usage:Backup Exec processes show a constant CPU (processor) usage (never idles) and show signs of a memory leak regardless of the Backup Exec for Windows Servers application activity.