No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


OceanStor BCManager 6.5.0 eReplication User Guide 02

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Introduction to Log Management

Introduction to Log Management

Log management means the management of system operation logs, system debug logs, host Agent logs, and GaussDB database logs.

System Operation Logs

All user operations performed on eReplication are logged. Operations that do not affect eReplication such as viewing and searching are not logged. eReplication provides the function of browsing operation logs and filtering logs by log level, administrator, log category, operation results, as well as log start time and end time. Logs also help you understand user operations. For example, you can view the operations that are performed by a user on the NMS.

eReplication has restrictions on log permission of different users as follows:
  • Super administrators have all permissions.
  • Common administrators granted the viewing permission can view their own operation logs only.
  • Administrators without permission cannot view any operation log.

Periodically dumping system operation logs deletes database records, ensuring sufficient available space of the database. Dumped operation log files are saved in the eReplication Sever installation directory//Runtime/LegoRuntime/datastorage/sysoptlog path. A user can download the dumped system operation files on the client and delete unnecessary log files under the directory.

Operation log levels indicate the severity of the log. eReplication classifies system operation logs into three levels: Warning, Minor, and Info from the most critical to the least critical. Table 7-8 defines different levels of system operation logs.
Table 7-8  Log levels




Operations that may cause data inconsistency of the entire system or a function module, for example, Delete Recovery Plan.


Normal operations on a system or function module, for example, Deliver refreshing resource command.


Operations, which impact no service running, on a system or function module, for example, Deliver a protected group creation command.

System Debug Logs

Debug logs record the software running status that cannot be detected by the system, such as the object status change and record of an abnormal message. Debug logs help system maintenance personnel locate faults and analyze the system running efficiency.

System debug log levels indicate the severity and importance of logs. eReplication classifies system debug logs into four levels: Error, Warning, Info, and Debug from the most critical to the least critical. Table 7-9 defines different levels of system debug logs.
Table 7-9  Levels of system debug logs




Errors occurred during system running, such as file damage, which may lead to abnormalities of some functions and recovers only after manual intervention.


Information about foreseeable and processable local abnormalities, such as processing timeout.


Software running tracks. Such logs records the information about function invocation.


Debugging information that is provided to the R&D personnel.

GaussDB Database Logs

The GaussDB database is installed during the installation of eReplication. Run logs and debug logs generated during the running process of the GaussDB database are called system logs. Run logs are generated during the normal running of the database. Debug logs are generated when a database application is being developed and commissioned. During the running of the GaussDB database, a large volume of run logs are generated, consuming large disk space. You are advised to retain run logs generated only in the latest one month.

The aussDB database logs are saved the following path:
  • Windows: GaussDB database installation file path\gs\app\data\pg_log
  • Linux: /opt/gs/app/data/pg_log
Updated: 2019-05-21

Document ID: EDOC1100075861

Views: 14196

Downloads: 70

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Previous Next