cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

Logfiles on BE-client

Hi,

we have log files in the path c: \ Program Files \ Veritas \ Backup Exec \ RAWS \ logs of our BackupExec clients.
On some servers only a few, on other GB of log files.

Registry key is already set to 0 :
HKEY_LOCAL_MACHINE \ SOFTWARE \ Symantec \ Backup Exec For Windows \ Backup Exec \ Engine \ Logging
CreateDebugLog REG_DWRD 0

what can we do?

10 Replies
Highlighted

Re: Logfiles on BE-client

Firstly I would check to see if they are old logs, or are still being updated on a daily basis. Old logs can generally be deleted, unless you are specifically troubleshooting a problem and support have asked for them.

Also checkout the following technotes, which have details about various debugging options:

https://www.veritas.com/content/support/en_US/article.100016806 - How to enable-disable the Debug logging from Beutility in Backup Exec
https://www.veritas.com/content/support/en_US/article.100028569 - How to Debug Backup Exec - Agent & Options debug log gathering list

Lastly, as is probably mentioned in one of those TNs, as well as :
HKEY_LOCAL_MACHINE \ SOFTWARE \ Symantec \ Backup Exec For Windows \ Backup Exec \ Engine \ Logging
also check the various entries here too:
HKEY_LOCAL_MACHINE \ SOFTWARE \ Symantec \ Backup Exec For Windows \ Backup Exec \ Debug

Highlighted

Re: Logfiles on BE-client

You can use BEutility to change job logs and catalog

 

https://www.veritas.com/support/en_US/article.100017954

Highlighted

Re: Logfiles on BE-client

thanks for your post

we have several be-agents from where we take backups.
most have one beremote log from the last backupjob and single different beremotelogs from diverse dates (eg 1 from 10.07, 18.06. ...)
another be-agent shows 5 up to 20 MB logs from every backup since month, so GB of logs
we cant find differences in registry or SGMon

we cant find entrys in beutility

Highlighted

Re: Logfiles on BE-client

Did the info in the Technote mentioned by @PJ_Backup help ? If you see beremote logs till date then the logging may have been left enabled since a long time or just disabled recently. If SGMON is closed, it stops logging in the SGMON Log file. Having said that you may see some Always On Logs for beremote on remote server and Always on logs for beremote and bengine on BE server, these are enabled by BE by default to log a debug dump when an error occurs during a backup or restore.

We had seen a corner case with some Hyper V Server where the logging used to turn on and that issue was solved in BE 21. I see that you are on BE 20, so just in case these loggings are on Hyper V server you can upgrade to BE 21 , update the remote agent and check the situation.

Highlighted

Re: Logfiles on BE-client

OK, you say the logs are enabled by default? but how to disable them? or is there no change to disable and only update is a possible resolution?
(for organizational reasons we cant update to BE21 at the moment)

Highlighted

Re: Logfiles on BE-client

1) Logging is disabled by default.
You can enable logging when you launch SGMOn or set the createdebuglog to 1

2) If you have logging disabled ( from the registry ) and still logs are getting created please check if the
name starts with AlwaysON*.log. These are very smaller snippet of logs that get saved in BE Logs folder when a job fails.

3) If the above 2 are not the case and you see logging continuously filling the drive, then please check on which server this is the case. By any chance are these Hyper V servers ?

Check this as well if any of the info here helps - https://www.veritas.com/support/en_US/article.100029014

Highlighted

Re: Logfiles on BE-client

we have %servername%-beremote-xx-xx.logs, %servername%-sgmon-xx.logs after starting sgmon, little %servername%-beremote_AlwaysOnLog_%date%.logs
we have no HyperV, but some of the servers are hosted on vmware esxi.
 
Highlighted

Re: Logfiles on BE-client

So you can ignore my comment about the Hyper V.

The logs you talk about should not continue to get created if createdebuglog is 0
If Sgmon.exe is not running, then SGMON log file will not be appended.

Also note that in BE you can right click on the job and run the job with debugging enabled, so ensure by any chance this is not done as it will create log only for the time when the job is running. The debug is disabled when the job completes in this case.

Always on logs are enabled by default in BE and only 10 latest ones are kept ( 5 MB each in size ). They are formed only if a job fails.

If no active ticket is open with support and these logs are not needed, you can delete them to reclaim space.

Highlighted

Re: Logfiles on BE-client

Thank you so much
the many text about sgmon debugging and always on does not help us.
It is not nice to delete the log files when our monitoring reports disk space, but we will apparently have no other choice.

Highlighted

Re: Logfiles on BE-client

SGMON log file will only be appended if SGMON.exe is running. So if you do not run it, the SGMON log file should not increase. For the always on debug if you want to turn it off
HKLM\Software\Symantec\BackupExec For Windows\Backup Exec\debug
Create a Dword as below and set it to 0
Always-On debug logging