FAQ about cascade snapmirror transfer and operation
Applies to
- ONTAP9
- SnapMirror
- Cluster Environment(Cascade snapmirror configuration from A->B->C->D)
- Node A: Current operational file server
- Node B: Backup of current operational file server
- Node C: New operational file server
- Node D: Backup of new operational file server
Answer
This FAQ is focus on snapmirror transfer action of B->C :
Q1: What happens to SnapMirror data during the initial transfer and subsequent updates?
A1:
- Initial Transfer (B->C):
- Creates a baseline using data on Node B at the start of the transfer.
- Updates to Node B during this transfer do not affect the baseline.
- A->B Updates:
- Occur daily as schedule setting, changing data on Node B.
- If the initial B->C transfer takes 50 hours, A->B updates will happen twice.
- Second Transfer (B->C):
- Incremental, including only changes made to Node B after the initial transfer.
Q2: Is it possible to pause snapmirror B->C to configure CIFS related setting on C and then resume the snapmirror, and what's the procedure ?
A2: Yes, the procedure is below:
- Check the snapmirror relationship on C
::>snapmirror show
- Pause the snapmirror relationship on C
::> snapmirror quiesce -destination-path vs2.example.com:dept_eng_mirror2
- Resume the snapmirror relationship on C
::> snapmirror resume -destination-path vs2.example.com:dept_eng_dp_mirror2
