H13-629_V3.0 Exam Dumps : HCIE-Storage V3.0

Huawei divides DR into data-level, application-level, and service-level protection according to recovery requirements and investment.

For data-level DR, the remote site primarily protects copies of production data. Huawei explicitly states that a data-level DR center cannot prevent service interruption when a disaster occurs; it operates essentially as a backup center from which data can later be restored. Therefore, C is correct and D is false.

For application-level DR, the backup site contains the same application system as the production site and data is synchronized between the sites using synchronous or asynchronous mechanisms. This allows applications to be restarted at the DR site within the defined RTO, making B correct.

Service-level DR is the most comprehensive level. Huawei defines it as a complete DR environment covering IT technologies and infrastructure as well as non-IT resources such as offices and telecommunications. A redundant workplace may therefore be required if the normal business site becomes unavailable.

Hence, A, B, and C are correct.

Study Guide Topics: Data Protection Solution → DR Basics → DR Levels → Data-Level → Application-Level → Service-Level DR.

Huawei explains that a file-system snapshot is a point-in-time copy. When source data changes, ROW writes the new data to another location while the snapshot continues to reference the original data, thereby preserving the source file system ' s state at snapshot creation time.

The statement is TRUE. Snapshot rollback changes the active file-system data state back to the selected protection point. Active NAS clients must therefore not continue issuing file operations against the source file system while that authoritative state is being replaced. The host share is unmounted before rollback so that active client I/O cannot conflict with restoration of snapshot metadata and data mappings.

The HCIE materials also show the same operational consistency principle in rollback workflows: upper-layer service access is stopped before storage state is reverted. In the Lab Guide ' s rollback procedure, the first action is to stop upper-layer service access and unmount the relevant file system before storage mappings are changed.

This ensures that the post-rollback file system presents one internally consistent point-in-time image when service access resumes.

Study Guide Topics: Data Storage Technology Presentation → HyperSnap → File System Snapshot → ROW → Snapshot Rollback → NAS Data Consistency.

Huawei explicitly states under Working Principle of the Mirroring Function of Volume Management Software:

“Add the target storage to a VG before the mirroring.”

“Run the lvconvert command to mirror LVs.”

“After the mirroring, remove the source storage and the data migration is complete.”

Therefore, the correct answer is B. lvconvert.

In an LVM-based migration, both the source and target physical volumes are made available within the appropriate volume group. lvconvert converts the existing logical-volume layout into a mirrored configuration so that LVM creates and synchronizes another copy of the logical volume on the target storage.

The HCIE Lab Guide also demonstrates lvconvert during the migration workflow. Once synchronization is complete, the mirror can later be split, allowing the target-side image to become the active migrated copy while the original source-side image can be preserved temporarily for rollback.

lvmigrate, hrmirror, and lvexport are not the command used by Huawei ' s documented Linux LVM migration workflow for creating the mirror.

Study Guide Topics: Data Migration Solution → Host Volume Management Software → Linux LVM → Volume Mirroring → lvconvert.