You can refer to daemon.raw for most of the networker logging. Apart from that, you may alos look at the follwoing under ../nsr/logs on UNIX or \nsr\logs on Windows
messages: Contains all the NetWoker logged information
networker.raw :manual backup and recover
summary: media alert logs
license-conformance: All the license informaation
rap.log : All the changes made to the datazone configuration( rap logging should be enabled for this)
For any application backup, you need to look at /nsr/applogs and then the specific log file depending on th application being backed up.
Apart from this, if detailed debugging is required, then you may need to change the debug level of a process using dbgcommand or during startup, or run the program in verbose mode.
To render the log, please follow the method provided by Arun, however there are a lot more switches available for customized rendering using nsr_render_log
mridul_singh
57 Posts
21638
2
Posted August 12th, 2012 03:00
You can refer to daemon.raw for most of the networker logging. Apart from that, you may alos look at the follwoing under ../nsr/logs on UNIX or \nsr\logs on Windows
messages: Contains all the NetWoker logged information
networker.raw :manual backup and recover
summary: media alert logs
license-conformance: All the license informaation
rap.log : All the changes made to the datazone configuration( rap logging should be enabled for this)
For any application backup, you need to look at /nsr/applogs and then the specific log file depending on th application being backed up.
Apart from this, if detailed debugging is required, then you may need to change the debug level of a process using dbgcommand or during startup, or run the program in verbose mode.
To render the log, please follow the method provided by Arun, however there are a lot more switches available for customized rendering using nsr_render_log