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.


HyperClone Feature Guide for Block

OceanStor V5 Series V500R007

This document is applicable to OceanStor 5110 V5, 5110F V5, 5300 V5, 5300F V5, 5500 V5, 5500F V5, 5600 V5, 5600F V5, 5800 V5, 5800F V5, 6800 V5, 6800F V5, 18500 V5, 18500F V5, 18800 V5, and 18800F V5. This document describes the implementation principles and application scenarios of the clone feature. Also, it explains how to configure and manage clones.

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).
How Do I Plan Reserved Space for Immediately Available Clones?

How Do I Plan Reserved Space for Immediately Available Clones?


What is the purpose of reserving space in the storage pool for immediately available clones? How do I plan the reserved space size?


The reserved space is used to store snapshots generated during the synchronization implemented by an immediately available clone. Storage space is reserved because:

  • During the synchronization implemented by an immediately available clone, COW is performed on the I/Os newly written by the host. As a result, the space of the primary storage pool is occupied.
  • If the storage pool space is insufficient, COW of host I/Os will fail due to the failure to request space. In this case, the immediately available clone will enter the stopped state.

When configuring an immediately available clone, consider the reserved space of the primary storage pool. Ensure that the space is sufficient for COW of new host I/Os during the synchronization implemented by the immediately available clone. The space that needs to be reserved in the primary storage pool varies greatly depending on service scenarios and configurations. The maximum reserved space does not exceed the capacity of the primary LUN in the immediately available clone. In project planning, you are advised to plan the reserved space size based on the actual scenario and configuration to prevent resource waste or insufficiency.

The factors that affect the reserved space include the synchronization duration, host write bandwidth, and host I/O size. The following example describes how to plan reserved space:

An immediately available clone synchronizes data once a day. The duration of each synchronization is 1 hour, and the peak write bandwidth of the host is 5 MB/s. The amount of data written by the host in the one-hour synchronization period N = 1 x 60 x 60 x 5 = 18000 MB.

So, the reserved space at the primary end is at least 18000 MB.

  • When planning the reserved space, also consider the size of data blocks written by the host. The host I/O COW granularity used by the storage system is 64 KB. If the data block size written by the host is smaller than 64 KB, the reserved space occupied by COW is larger than the amount of data delivered by the host in the synchronization period.
  • Assume that a manual split or an external fault causes an immediately available clone to be disconnected. When incremental synchronization is performed again, the COW space required by the primary end is the size of service data delivered to the primary LUN during this period. The maximum COW space may be the same as the capacity of the primary LUN.
Updated: 2020-01-17

Document ID: EDOC1000181501

Views: 25012

Downloads: 252

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next