Whether data is synchronized between the primary and secondary LUNs if the HyperClone feature of the OceanStor V3 Series is in the non-split state

1

Data is synchronized between the primary and secondary LUNs if the HyperClone feature is in the non-split state.

Other related questions:
Whether the primary and secondary LUNs must have the same owning controller in the clone feature
The primary and secondary LUNs must have the same owning controller in the clone feature.

Whether the HyperClone feature of the OceanStor V3 Series supports cross-engine or cross–storage system clone
The HyperClone feature does not support cross-engine clone of LUNs. The primary and secondary LUNs used for cloning must reside on the same engine.

Whether services are stopped upon the initial synchronization of the HyperMirror feature in the OceanStor V3 Series
You do not need to stop services upon the initial synchronization. The HyperMirror feature supports dual-write, round-robin read, and online synchronization.

Feature of the LUN non-prefetch policy
1. Data is directly read from disks based on the read length specified in the I/O request without a prefetch process. 2. LUN non-prefetch is suitable for small-block random read applications, for example, databases.

Whether the SmartTier feature of the OceanStor V3 Series supports cross-engine data migration
The SmartTier feature does not support cross-engine data migration.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top