Exact Extract — Huawei Training Material, Pages 76–77:
HyperSnap/HyperCDP/HyperClone (SAN)
The SAN snapshot workflow identifies:
Cascading snapshot
The NAS copy-creation workflow identifies:
Cascading clones (up to 8 levels)
Technical Deep Dive:
Huawei OceanStor Dorado supports sophisticated snapshot and clone operations through HyperSnap, HyperCDP, and HyperClone.
However, the relationship between snapshots and their source objects differs between SAN and NAS.
For SAN environments, HyperSnap supports cascading snapshot relationships in which a snapshot can serve as the basis for another snapshot.
This enables multiple generations of point-in-time data copies to be created and managed in a hierarchical structure.
It is particularly valuable for database testing, application development, recovery validation, and environments requiring multiple recovery points.
For NAS environments, the supported copy relationships include creating a clone file system from an existing file-system snapshot or HyperCDP object.
The system also supports creating new snapshots or HyperCDP objects on a clone file system.
Furthermore, NAS supports cascading clones, allowing a clone to serve as the parent for another clone.
Cascading clones and cascading snapshots are not interchangeable concepts.
A cascading snapshot creates another snapshot within a snapshot relationship, while a cascading clone introduces a new clone object that can subsequently support additional protection operations.
The NAS workflow does not establish the same direct snapshot-of-snapshot capability shown for SAN.
Therefore, the statement is false because it incorrectly claims identical cascading snapshot support for both SAN and NAS.