| Component | Location on NetWorker Server | Description |
| daemon.raw |
|
The unrendered daemons (services) log file - This file contains messages about NetWorker service operations. |
| rap.log |
|
This log details changes to the NetWorker server's resource database including which NetWorker user account made the change. |
| nsrim.raw |
|
Nsrim performs aging of control data and consistency check of the media database. This log details when a save set is marked as eligible for deletion as per its retention settings. |
| Client fix |
|
Contains status information that is related to the use of the nsr_client_fix command |
| NetWorker Server generated syslog messages and daemon.notice |
|
Contains general NetWorker error messages |
| Disaster recovery command-line wizard, nsrdr program |
|
Contains detailed information about the internal operations that are performed by the nsrdr program - NetWorker overwrites this file each time that you run the nsrdr program. |
| Index log |
|
Contains warnings about the size of the client file index and low disk space on the file system that contains the index files - By default, the Index size notification on the NetWorker Server sends information to the log file. |
| Hyper-V FLR |
|
Contains status information about the Hyper-V FLR interface |
| Snapshot Management |
|
Contains messages that are related to snapshot management operations - For example, snapshot creation, mounting, deletion, and rollover operations. Use the nsr_render_log program to view the contents of the log file. |
| Media management |
|
Contains device-related messages - By default, the device notifications on the NetWorker Server send device-related messages to the media.log file on the NetWorker Server and each Storage Node. |
| Recovery Wizard |
|
Contains information that can assist you in troubleshooting recovery failures - NetWorker creates a log file on the NetWorker Server for each recover job. |
| Package Manager log |
|
Contains information that is related to the Package Manager and the nsrpush command Use the nsr_render_log program to view the contents of the log file. |
| Security Audit Logs |
|
Contains security audit-related messages |
| Policy and Workflow Logs |
|
The policy/workflow logs are retained as per the jobsdb retention window (default 72 hours). |
| RabbitMQ | RabbitMQ logs are detailed in KB: NetWorker: How to enable RabbitMQ Debugging. | Message Bus server which handles communication between the NetWorker server and NetWorker Management Console (NMC) or NetWorker Web User Interface (NWUI) |
| Component | File name and default location | Description |
| NMC server log files |
|
Contains information that is related to NMC server operations and management - Use the nsr_render_log program to view the contents of the log file |
| NMC server database conversion |
|
Contains the results of the NMC server database conversion that is performed during an upgrade operation |
| NMC web server |
|
Contains messages for the embedded Apache httpd web server on the NMC server |
| NMC server database log files |
|
Contains messages for the embedded PostgreSQL database server on the NMC server |
| Component | File name and default location | Description |
| Installation Log |
|
Contains information about the installation of the NetWorker Authentication Service. |
| authc_mgmt and authc_config |
$HOME/authc-cli.log
Where $HOME is the home folder for the logged in user. For example, when the root user runs the command, the file location is /root/authc-cli.log.
|
Contains a list of error messages that appeared when a user ran the authc_mgmt and authc_config tools |
| Authentication server log |
|
Contains security audit messages for the NetWorker Authentication Service. |
| Audit log |
|
Contains security audit messages for the NetWorker Authentication Service. |
| Tomcat Access logger |
|
Contains access information for the embedded Apache httpd web server |
| Apache Catalina log |
|
Contain messages for the Apache Tomcat core component. |
| Component | File name and default location | Description |
| NetWorker Client daemons |
|
Main NetWorker log file Use the nsr_render_log program to view the contents of the log file. |
| User log | C:\Program Files\EMC NetWorker \logs\networkr.raw |
For Windows, contains a record of every file that was part of an attempted manual backup or recovery operation that is started by NetWorker User program. Subsequent manual backup or recover operations overwrite the file. Use the nsr_render_log program to view the contents of the log file. |
| Windows Bare Metal Recovery (BMR) | The following files in the X:\Program Files\EMC NetWorker\nsr\logs\ directory: ossr_director.raw |
Contains the recovery workflow of the DISASTER_RECOVERY:\ and any errors that are related to recovering the save set files or Windows ASR writer errors. Use the nsr_render_log program to view the contents of the log file. |
| ... | recover.log | Contains the output that is generated by the NetWorker recover.exe program and error messages that are related to critical volume data recovery |
| ... | winPE_wizard.log | Contains workflow information that is related to the NetWorker BMR wizard user interface |
| ... | winpe_nw_support.raw | Contains output from the winpe_nw_support.dll library - The output provides information about communications between the NetWorker BMR wizard and the NetWorker Server. Use the nsr_render_log program to view the contents of the log file. |
| ... | winpe_os_support.log | Contains output information that is related to Microsoft native API calls |
| CloudBoost - NetWorker Client | The following log files in the /nsr/logs/cloudboost directory: MagFS.log.ERROR.date-timestamp.pid.txt MagFS.log.FATAL.date-timestamp.pid.txt MagFS.log.INFO.date-timestamp.pid.tx |
These files appear on a client direct-enabled NetWorker Client and contain information about data stored on a CloudBoost device. The severity of the message determines which log file that error message is written to. The maximum size of the log files is 100 MB. Before a client direct backup, the save process checks the size of the file. When the maximum size is reached, save starts an automatic trimming mechanism, which renames and compresses the log file. The maximum number of versions for a file is 10. When the number of renamed log files reaches the maximum version value, NetWorker removes the oldest log when a new version of the log file is created.
NOTE: The Troubleshooting manual backups section of the NetWorker Administration Guide describes how to use the CB_LOG_DIR_LOCATION environment variable to change the default log file location.
|
| CloudBoost - CloudBoost Appliance | The following log files in the /nsr/logs/cloudboost directory: MagFS.log.ERROR.date-timestamp.pid.txt MagFS.log.FATAL.date-timestamp.pid.txt MagFS.log.INFO.date-timestamp.pid.txt |
These files appear on the CloudBoost appliance and contain information about operations that are performed on a CloudBoost device. The severity of the message determines which log file that error message is written to. The maximum size of the log files is 100 MB. When the maximum size is reached, the nsrmmd process starts an automatic trimming mechanism, which renames and compresses the log file. The maximum number of versions for a file is 10. When the number of renamed log files reaches the maximum version value, NetWorker removes the oldest log when a new version of the log file is created. |
| Log file | Default log location | Description |
| <job-uuid>.log |
|
vProxy management job log file is created during the redeployment of the associated vProxy. |
| vproxy_upgrade_sessio n__< jobuuid> |
|
Associated nsrvisd log file is created during redeployment of the vProxy. |
| nsrvisd-daemon.log |
|
Associated nsrvisd detailed log file is created. |
| ProxySessions- .log |
|
Associated ProxySessions log file is created during redeployment of the vProxy. |
| Nsrvisd logs |
|
Associated inventory sessions log file is created. |
| VM backup logs |
|
The VM backup session logs are retained as per the jobsdb retention window (default 72 hours).
NOTE: The VM session logs can also be found on the vProxy appliance.
|