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.


eSight V300R010C00SPC200, 300, and 500 Operation Guide 09

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).
Setting Data Overflow Dump

Setting Data Overflow Dump

Normally, sufficient database space has been allocated based on the network scale to ensure proper eSight service running. Even so, it is still possible that network monitoring will be compromised as new data cannot be written to the database when the data in it accumulates with time. eSight data overflow dump provides a mechanism to cope with the problem. It is advisable to plan and set this function based on the network scale and hardware configuration of the eSight server after eSight is installed. The eSight supports overflow dump of log, alarm, and performance databases.


You have the operation rights for Database Overflow Dump.


  • The dump function is available only to the databases for whom automatic expansion is enabled (the default state). Do not disable automatic expansion manually.
  • Figure 23-1 shows the working mechanism of eSight data overflow dump.
    Figure 23-1 Working Mechanism of Data Overflow Dump
    • eSight checks whether the database tablespace usage or the number of data retention days exceeds the threshold. If the usage exceeds the threshold, the eSight dumps the earliest data to the files in a specified path and deletes the data from the database until the database tablespace usage is below the threshold.
    • Dump path can be a relative path.

      The relative path is relative to the eSight installation path eSight installation directory/AppBase/var/iemp/data/dump (on Linux). If you specify Dump path to AAA, the file is saved to eSight installation directory/AppBase/var/iemp/data/dump/AAA.

    • Before saving dump files to a specified directory, the eSight checks whether the file size or the retention period exceeds the preset thresholds. If so, it will delete the earliest file until they are below the threshold. File size and Save period settings can help you manage file directory size based on available space of hard disks.

Because the eSight deletes the dumped data from the database, the dumped data cannot be queried from the GUI. You can view it in the dump file during the storage period.


  1. Choose System > System Settings > Common Parameters from the main menu.
  2. In the navigation tree in the left pane, choose Log Database Dump, Alarm Database Dump or Performance Database Dump.
  3. In the right pane, set dump parameters.
  4. Click Apply.


When data is dumped, the eSight automatically generates a folder named in the format of the current date, save the data to the folder, and place the folder in the directories whose names are the months in which the data is generated.

Updated: 2019-09-12

Document ID: EDOC1100044378

Views: 69397

Downloads: 371

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