Backup Exec beremote log file exists on every remote server

Problem

Backup Exec creates on every remote system a beremote log file in the following directory:
C:\Program Files\Veritas\Backup Exec\RAWS\logs

The beremote log file has the following naming convention:
<server name>-beremote<number>.log
Example: Server1-beremote01.log

 

Error Message

No error message
 

Cause

With Backup Exec 20.4 the following feature was introduced:
"Run with debugging enabled"

For more information about the usage of this feature see (as example BE 22 Admin Guide):
https://www.veritas.com/support/en_US/doc/59226269-152612234-0/v135206755-152612234

 

Solution

The existence of the beremote log file on any remote server is by design.
It is required to exist for the above described feature to work correctly.

The increase of the beremote log file is in most situation a few 100 KB when a backup or restore job of this server runs, depending on different job features and options like the target device or applications involved.

There is an additional small increase when the server is "browsed", when Backup Exec identifies what resources are on this server.

Neither of the above should have any negative impact on disk size usage as long as all the debugging is disabled.


In the unlikely event that the beremote log file on a remote server is increasing too much even though all the debug logging has been disabled, the following registry key got introduced with BE 22.1, which can be adjusted to disable this functionality.

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.


HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\Backup Exec For Windows\Backup Exec\Engine\Logging\CreateDefaultDebugLog
Default value is 1 (functionality enabled)
Set the value to 0 (functionality disabled)



WORKAROUND:

For earlier versions, please delete the log file on a regular basis.