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 V300R010C00 Maintenance Guide 07

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).
Backup Policy

Backup Policy

This section describes the eSight backup policy. You can refer to this policy to back up data during onsite implementation.

Backup Scenarios

The eSight backup solution varies depending on the scenario.

  • If eSight uses the MySQL database, the automatic backup mode is used. For details, see Automatic Backup.
    • Backup interval: every day
    • Retention period for backup data: seven days
    • Binlog retention period: three days
    • Default backup time: 02:00 every day
  • In other scenarios, select a backup mode as required by referring to Backup Principle.

Restoration Scenarios

For details about how to restore eSight data, see Manual Restoration.

Table 4-1 Restoration scenarios



Scenario Example

Restoration Procedure

Upon hardware disaster

Hardware faults, such as server faults, in the equipment room

All servers are damaged due to a disaster in the equipment room.

  1. Replace the faulty devices.
  2. Reinstall the eSight system.
  3. If the server or server network adapter has been replaced, update the license. For details, see "Applying for a Commercial License After ESN Change" in the eSight License User Guide.
  4. Use backup files to manually restore eSight service data.

Upon software disaster

Third-party software such as the operating system and database or eSight application software is damaged.

  • A disaster such as power-off occurs, causing data damage to the operating system.
  • Configuration files of the operating system or database are lost, damaged, or incorrectly configured. As a result, basic functions of the operating system are normal, but eSight cannot be started properly.
  • Other third-party basic applications are damaged. For example, if the VCS software is damaged, two-node cluster switchover cannot be performed, and the volume management function cannot be used properly.
  • Service application files are damaged. As a result, eSight cannot be started.
  • Some system files are damaged because the disk space is used up. As a result, the operating system or eSight is faulty.
  1. Reinstall the eSight system.
  2. Use backup files to manually restore eSight service data.

Maintenance scenario

eSight service configuration files are lost or damaged.

eSight services are running properly, but some service data or configuration files are lost.

Manual restoration

Upon database data loss or damage

The database tablespace is damaged or any data table (system table or non-system table) is lost.

Manual restoration

Updated: 2019-06-30

Document ID: EDOC1100044373

Views: 25095

Downloads: 74

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