Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

PowerProtect Data Manager 19.11 Cyber Recovery User Guide

PDF

Reviewing Cyber Recovery logs

The Cyber Recovery software generates both a JSON and a text logfile for each service.

The log files are stored in the <installation directory>/var/log/<component> directory, where component is one of the following Cyber Recovery components:

Table 1. Cyber Recovery component log directoriesThe following table lists and describes the log directories for the Cyber Recovery components:
Cyber Recovery component Log directories
cradmin Anything that is related to lockbox activity.
crcli Anything that is related to the CRCLI.
crsetup Anything that is related to the crsetup.sh script.
edge service The routing for all calls from REST clients, the Cyber Recovery CLI, and the Cyber Recovery UI, as well as the logic for setting system log levels, licensing, and dashboard.
NOTE This service is the entry point for all REST API calls.
apps service Anything that is related to applications that are associated with Cyber Recovery, including CyberSense feature used for copy analysis, PowerProtect Data Manager instances, and file system hosts.
mgmtdds service All communication with the Cyber Recovery vault DD.
notifications service All the system notifications (alerts and events) and SMTP email messages.
policies service Anything that is related to policies, jobs, copies, and sandboxes.
schedules service All the system schedules, cleaning schedules, and action endpoints.
users service Anything that is associated with users, including addition, modification, and authentication operations.
vault service Anything that is related to the status of the vault, and opening and closing managed interfaces.
nginx service Anything that is related to the web server that runs the Cyber Recovery UI.
swagger service Anything that is related to the Cyber Recovery REST API container.
system service Anything that is related to DR backups and log bundle creation.
vcenter service Anything that is associated with vCenter objects.
clouds service Anything that is related to the Cyber Recovery vault on Amazon Web Services (AWS).

All Cyber Recovery logfiles use the following log message format: 

[<date/time>] [<error type>] <microservice name> [<source file name>: <line number>] : message

For example: 

[2018-08-23 06:31:31] [INFO] [users] [restauth.go:63 func1()] : GET /irapi/users Start GetUsers

Log Levels

The following table describes the log levels by order from low to high. Each log level automatically includes all lower levels. For example, when you set the log level to INFO, the log captures all INFO, WARNING, and ERROR events.

The default log level is INFO.

Table 2. Log levelsThe following table lists and describes the log levels for the Cyber Recovery components:
Log Level Purpose Example
ERROR Reports failures in the execution of some operation or task that usually requires manual intervention.
  • Replication failure due to an incorrect password
  • Sandbox creation failure due to the mount point already in use
WARNING Reports unexpected technical or business events that might indicate a potentially harmful situation, but do not require immediate attention.
  • Corrupted or truncated file
  • Policy 1 hour over the sync timeout period of 6 hours
INFO Reports information about the progress of an operation or task.
  • Synchronization started
  • Creating a point-in-time copy
  • Scanning for malware
DEBUG Captures highly granular information for debugging or diagnosis. This level is typically useful to administrators, developers, and other users.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  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: <>()\