You can monitor BMR activity by viewing the messages that are generated by BMR.
BMR uses a standardized naming format for log files.
The following is an example log file name:
51216-119-3892578826-050225-0000000000.log
The following are the components of this example log file name:
119 is the originator ID of the process that wrote the log (bmrd or bmrbd, the Bare Metal Restore master or boot server service).
3892578826 is a decimal ID for the host that created this log.
0000000000 is the rotation number indicating the instance of this log file. If the file reaches maximum size and a new log file is created for this originator, the file rotation number increases by 1.
The following types of messages can appear in unified logging files:
Application log messages. These include informational, warning, and error messages.
Diagnostic log messages. The amount of information that is logged depends on the logging level.
Debug log messages. These are primarily for Symantec support and engineering. The amount of debug information that is logged depends on the logging level that is specified for the NetBackup master server.