NetApp Community Update
This site will enter Read Only mode on July 23 as we prepare to move to a new platform.
You will still be able to view content, but posting and replying will be temporarily disabled.
To learn more, please review the information in this blog post.

ONTAP Discussions

Snapmirror - destination qtree bigger than source qtree

semionkras
4,380 Views

I am replicating 100 GB to remote site over slow wan connection , during first initialization snapmirror stopped due to network problems(lost connection) .

I resumed it and seems replicating going well, but i notieced that destination gtree replicated more than 110G already and keep going , since i need couple days to do first initialization of  volume i cant stop it and redu this again , anyone got any idea why i keep replicating more data than source qtree?

4 REPLIES 4

radek_kubka
4,380 Views

I bet your source volume has been de-duped, hasn't it?

QSM inflates de-duped data unfortunately - you have either live with this or consider using VSM instead.

Have a look at this:

http://communities.netapp.com/message/5334#5334

Regards,

Radek

semionkras
4,380 Views

No , no duplication here on both source and destination , anyway it finnaly ended with 15 gb difference

rkaramchedu1
4,380 Views

What type of disks are on source and on destination? can you do a vol status -b on both and share the output?

semionkras
4,380 Views

DESTINATION

Volume              Block Size (bytes)  Vol Size (blocks)   FS Size (blocks)
------              ------------------  ------------------  ----------------
web01               4096                78643200            78643200

SOURCE

Volume              Block Size (bytes)  Vol Size (blocks)   FS Size (blocks)
------              ------------------  ------------------  ----------------
web01               4096                104857600           104857600

I am transferring qtree and not entire volume , so difference you see is becouse of missing qtree on destination ,

The difference in size i was during snapmirror , but i think now it ok

Public