Increasing volume size for snapmirrored volume in destination filer

Steps to increase size for snapmirroed volume on the destination filer
Primary filer name : PRI
Primary Volume name : vol1
Destination filer name : DST
Destination volume name : vol1



Step 1 —  Break the snapmirror to make the DST volume read/writeable

DST> snapmirror break vol1

Step 2 — We need to change the volume option “vol1″ volume fs_size_fixed to off, if its ON we can’t increase volume size directly.

DST> vol options vol1 fs_size_fixed off

Step 3 — Next increase the size of the destination volume

DST> vol size vol1 +1g

Step 4 — Change the fs_size_fixed on before we resume the mirror

DST> options vol1 fs_size_fixed on

Step 5 —  Resync the destination side, to get latest updates from primary volume.

DST> snapmirror resync -S PRI:vol1

SnapMirror

Snapmirror:

1. Snapmirror is a license product in Netapp.
2. SnapMirror is for Disaster recovery and its Loss of region.
– Disaster Recovery
– Data migration
– Data replication
– Remote access and load sharing
3. Using snapmirror data transfer one filer to another filer or in same filer.
4. Snapmirror will work at Volume and Qtree level.
5. Snapmirrror needs a source and destination filer.
6. Snapmirror is used primarily for data redundancy
7. Real time replication of data
8. Maximum distance of up to 35km
9. Fibre Channel or DWDM protocol

In snapmirror 3 mode of data replication

Sync                = data transfer continually  

Async              = data transfer in scheduled timing

Semi-sync       =  like Async

Requirements and Limitations for VSM

1. Destination’s Data ONTAP® version must be equal to or more recent than the source
2. Like-to-like transfers only: flex-to-flex
3. Destination volume capacity should be equal or greater than source
4. Quota cannot be enabled on destination volume
5. TCP port range 10565–10569 must be open

Qtree SnapMirror (QSM)

1. Logical replication
2. Independent of the type of volume
3. Source volume and qtree are online/writable
4. Destination volume is online/writable
5. Destination qtree is read-only

Requirements and Limitations for QSM

1. Supports Async mode only
2. Destination volume must have 5% extra space
3. Destination qtree cannot be /etc name
4. Cannot be initialized using a tape device
5. Does not support cascading of mirrors
6. Deep directory structure and large number of small files may impact performance

Snapmirror primary configuration of VSM & QSM

Snapmirror Secondary configuration of VSM & QSM

Snapmirror schedule configuration