NAS protection creates logs at the asset and job levels that you can download to analyze when resolving problems.
Log in to the
PowerProtect Data Manager user interface as a user with the
Administrator,
User,
Backup Administrator, or
Restore Administrator role.
On the
Jobs > Protection Jobs page, select the job that corresponds to the problem which requires troubleshooting. The job details provide more information about any potential issues. Also, you can click
Show Skipped Files to view the elements (files and folders) that are skipped during the backup.
NOTE:
Only after indexing the skipped elements are listed in UI. If you want to view the list of skipped elements immediately, you can download the respective log file by clicking
Export Log.
Skipped non-regular files such as socket and FIFO files are not reported in skipped logs.
The files that are skipped during the initial full backup are cumulatively listed under the second full backup. For example, if five files are skipped during the initial full backup and three files are skipped in the following full backup, the total number of skipped files in the second full backup will be eight.
To review the protection and skipped elements logs, click
Export Log. The log export contains three files with consolidated logs from
PowerProtect Data Manager, NAS protection workflow, and skipped elements. The NAS protection log contains the logs from both the NAS agent and
NAS protection engine.
Review
nasdm.log,
Nas_sessionID.log, and
Nas_Skipped_Elems_sessionID.csv to determine the root cause of any issue. Some of the troubleshooting guidance in this appendix uses the additional logs from the consolidated NAS protection log.
Exporting of logs times out
If you have a NAS environment with a very large amount of data, the exporting of logs can time out and you might see the following errors:
SYS0101: Timeout when processing external logs.
An unknown error occurred during the log export operation.
To resolve the issue, perform the following steps:
Log in to the
PowerProtect Data Manager server console using administrator credentials.
Run the command
cd /usr/local/brs/lib/logmgr/config.
Create a file named
application.properties.
Edit the file and add the following line of text:
log.export.dependency.tasks.timeout=7200
Save the file.
Restart the
logmgr service by running the command
logmgr restart, and then wait a few seconds for the service to restart.
Export the logs again.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\