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.


HyperVault Feature Guide

OceanStor Dorado V3 Series V300R002

This document is applicable to OceanStor Dorado5000 V3, Dorado6000 V3, and Dorado18000 V3. It describes the implementation principles and application scenarios of the HyperVault feature, and explains how to configure and manage HyperVault.
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).


This section describes the background, definition, and benefits of HyperVault.


In the new digital era, data is key for an enterprise to survive and succeed. Protecting service data that grows explosively is one of the most pressing challenges. Currently, basic data backup and recovery policies have the following problems:

  • Massive service data cannot be backed up and recovered quickly. The backup process affects service continuity.
  • More devices and management tools are required as the backup environment is increasingly complex, raising data protection costs.

Therefore, enterprises are seeking for a solution that backs up and recover data quickly without affecting services or raising costs. To meet the customer requirements, Huawei has developed HyperVault.


Based on file systems, HyperVault enables data backup and recovery within a storage system and between different storage systems.

  • Data backup involves local backup and remote backup. With file systems' snapshot or remote replication technology, HyperVault backs up the data at a specific point in time to the source storage system or backup storage system based on a specified backup policy.
  • Data recovery involves local recovery and remote recovery. With file systems' snapshot rollback or remote replication technology, HyperVault specifies a local backup snapshot of a file system to roll back it or specifies a remote snapshot of the backup storage system for recovery.

HyperVault has the following characteristics:

  • Time-saving local backup and recovery: A storage system can generate a local snapshot within several seconds to obtain a consistent copy of the source file system, and roll back the snapshot to quickly recover data to that at the desired point in time.
  • Incremental backup for changed data: In remote backup mode, full backup at an initial time and permanent incremental backup save bandwidth.
  • Flexible and reliable data backup strategy: HyperVault supports self-defined backup policies and threshold for the number of copies. A copy of invalid backup data will not affect follow-up backup tasks.


Table 1-1 describes the benefits provided by HyperVault.

Table 1-1 Benefits



High efficiency

HyperVault uses redirect-on-write (ROW) technology to achieve real-time backup without degrading service performance. In addition, HyperVault completes data rollback and achieves quick data recovery by adopting the snapshot rollback technology to enable the root node of source data to quickly point to the root node of snapshot data.

High data security

HyperVault enables you to set four local backup policies and four remote backup policies as well as configure the number of copies to between 3 and 256. The minimum interval of backup tasks is 5 minutes, implementing continuous data protection.

Cost effectiveness

HyperVault integrates backup and recovery technologies. You do not need to purchase them separately.

Easy management

HyperVault supports centralized backup, not requiring independent backup servers. HyperVault configuration and management can be performed in DeviceManager.

Updated: 2019-02-22

Document ID: EDOC1100067325

Views: 2360

Downloads: 13

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