If anomalies occur on a protected object (such as a database) during DR protection or recovery, you can export the logs of the eReplication Agent on the host where the protected object resides to a local path. You can analyze the logs to locate and handle the anomalies.
Context
You can export the logs of the eReplication Agent on the eReplication CLI. All the logs, including the Nginx logs, run logs, and debug logs, of the current eReplication Agent are collected.
Procedure
- On the menu bar, select Resources.
- In the navigation tree, choose LocalServer > xxSite > Host.
xxSite indicates the site where the host whose Agent's logs to be collected resides.
- Export and download the logs of the eReplication Agent on the host.
- In the row of the host, click in the operation area.
In the Warning dialog box that is displayed, read the content of the dialog box carefully and select I have read and understood the consequences associated with performing this operation.
- Click OK.
- In the row of the host, click Export Log in the operation area to download the collected logs to a local path.
- In the row of the host, click in the operation area.
- View the collected logs.
In Linux, the name of the exported log package is in the format of xxx.xxx.xxx.xxx (host IP address).tar.gz. In Windows, the name of the exported log package is in the format of xxx.xxx.xxx.xxx (host IP address).zip. After decompression, there is a folder named sysinfodate. The folder contains a file named date, which provides information about the log collection date and time. Figure 1 describes the structure and function of the log package directory.
agent_log: records the run logs and debug logs of the eReplication Agent.
nginx_log: records logs of communication between the eReplication Server and Agent and error logs.
