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

Reminder

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

upgrade

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).
Working Principle

Working Principle

This section describes the basic concepts and working principle of HyperVault.

Backup Principle

HyperVault implements incremental backup of changed data blocks. In the initial phase, full backup is executed. In follow-up phases, only changed data is backed up. In the backup storage system, each copy of backup data is a full backup of service data and all backup data copies are logically independent of each other. Deleting one backup data copy does not affect the validity of other backup data copies. Backup data is saved in its original format and can be immediately accessed. Figure 1-1 shows how file system backup works.

Figure 1-1 Incremental data backup
  1. Full backup in the initial phase: Snapshot 1 is generated in the source storage system. Upon the initial backup, all data of snapshot 1 is backed up to the backup storage system. After the backup is complete, snapshot a is saved in the backup storage system.
  2. First incremental backup: When snapshot 2 in the source storage system is backed up, only the changed data blocks (F, G, and H) are backed up. After the backup is complete, snapshot b is generated in the backup storage system. Logically, snapshot b is a full backup of service data.
  3. Second incremental backup: When snapshot 3 in the source storage system is backed up, only data blocks I and J are backed up. After the backup is complete, snapshot c is generated in the backup storage system. Logically, snapshot c is a full backup of service data.

Local Backup and Recovery

Local backup

Local backup is implemented by creating snapshots of the source file system. The backup can be completed within seconds. The created snapshots are local backup copies. In local backup, HyperVault creates and saves a snapshot for the file system to be backed up in the source storage system based on the specified local backup policy. Each file system keeps a certain number of local backup copies based on the policy. Figure 1-2 shows how local backup is implemented.

Figure 1-2 Local backup

Local recovery

Local recovery is implemented using the snapshot rollback technology. HyperVault specifies a local backup snapshot at a time point for the file system to be recovered and rolls back the local backup snapshot to recover the file system data to that time point. Figure 1-3 shows how local recovery is implemented.

Figure 1-3 Local recovery
  1. Data in the source file system is damaged and needs to be recovered.
  2. A local backup snapshot at a time point is specified for the file system to be recovered.
  3. The local backup snapshot is rolled back to recover the file system data to that time point. After data recovery is complete, snapshots generated after the time point are deleted.

Remote Backup and Recovery

Remote backup

In a remote backup task, file system data is backed up from the source to the backup storage system, which is more secure and reliable than local backup. Figure 1-4 shows how remote backup is implemented.

Figure 1-4 Remote backup
  1. In remote backup, HyperVault creates a new snapshot for the file system to be backed up in the source storage system based on the specified remote backup policy.
  2. The system obtains the data changed from the last remote backup snapshot and replicates the changed data to the backup storage system.
  3. The system creates and saves a new snapshot in the backup storage system.

Remote recovery

Remote recovery is implemented using the remote replication technology. HyperVault specifies a remote snapshot at a time point in the backup storage system for the file system to be recovered and copies the snapshot to the source storage system to recover the file system data to the time point. Figure 1-5 shows how remote recovery is implemented.

Figure 1-5 Remote recovery
  1. Data in the source file system is damaged and cannot be recovered by local backup. In this case, recovery from the backup storage system is required.
  2. A remote snapshot at a time point is specified in the backup storage system for the file system to be recovered.
  3. The snapshot is copied to the source storage system to recover the file system data to the time point. In remote recovery, snapshot copies in the backup storage system are not deleted after the recovery is complete.

Backup and Recovery Mode Selection

Comply with the following rules when using HyperVault to back up and recover data:

  • Backup mode selection
    • Local backup applies to quick backup scenarios. It is advised to set the local backup interval to 5 minutes. In addition, local backup can be used if the connection between the production center and the backup center is down.
    • Remote backup backs up data between storage systems. One-time full backup and permanent incremental backup improve security and reliability. If the file system in the backup storage system does not carry host services, it is advised to set the remote backup interval to a large value (for example, at 0:00 every day).
  • Recovery mode selection
    • If data in the source file system is damaged, a local backup snapshot is preferred for data recovery.
    • If local recovery cannot meet the requirements, remote recovery is used.
Download
Updated: 2019-02-22

Document ID: EDOC1100067325

Views: 2297

Downloads: 13

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