nerdexam
Network_Appliance

NS0-157 · Question #9

You set up a SnapMirror relationship between two clusters and start the SnapMirror initialization. The transfer starts without error and begins replicating data. Before the initialization completes…

The correct answer is A. Change the state of the destination volume to online. When a SnapMirror initialization fails mid-transfer due to a network outage, the destination volume remains in a restricted state that must be cleared before re-initialization can succeed.

Data Protection and High Availability

Question

You set up a SnapMirror relationship between two clusters and start the SnapMirror initialization. The transfer starts without error and begins replicating data. Before the initialization completes, a network failure occurs and the transfer fails to finish. Once the network failure is corrected, you attempt to initialize the transfer again, but receive the following error:

Volume rep_vol01 is restricted Which step should you perform before attempting re-initialization?

Options

  • AChange the state of the destination volume to online.
  • BDelete all Snapshot copies on the destination volume.
  • CChange the state of the destination volume to offline.
  • DDelete all data in the destination volume.

How the community answered

(24 responses)
  • A
    83% (20)
  • B
    4% (1)
  • C
    4% (1)
  • D
    8% (2)

Why each option

When a SnapMirror initialization fails mid-transfer due to a network outage, the destination volume remains in a restricted state that must be cleared before re-initialization can succeed.

AChange the state of the destination volume to online.Correct

During SnapMirror initialization, ONTAP places the destination volume in a restricted state to protect data integrity. When a network failure aborts the transfer, the volume stays restricted, and the error 'Volume rep_vol01 is restricted' reflects this. Changing the destination volume state back to online removes the blocking condition and allows the SnapMirror relationship to be re-initialized successfully.

BDelete all Snapshot copies on the destination volume.

Deleting Snapshot copies on the destination is not a prerequisite for re-initialization; the interrupted transfer does not create a Snapshot conflict that prevents a new initialization attempt.

CChange the state of the destination volume to offline.

The destination is already in a restricted or non-online state due to the failed transfer; changing it to offline does not resolve the error and is not a required step before re-initialization.

DDelete all data in the destination volume.

Manually deleting all data from the destination is unnecessary because SnapMirror re-initialization handles the baseline or incremental transfer automatically without requiring prior manual data removal.

Concept tested: SnapMirror initialization failure recovery and destination volume state

Source: https://docs.netapp.com/us-en/ontap/data-protection/initialize-replication-relationship-task.html

Topics

#SnapMirror initialization#restricted volume#volume state#replication recovery

Community Discussion

No community discussion yet for this question.

Full NS0-157 Practice