topic Re: Great difference in space allocation between EMC and Netapp in Network and Storage Protocols

Great difference in space allocation between EMC and Netapp

baszom — Thu, 05 Jun 2025 05:24:46 GMT

Hi,

we copied by rsync a volume containing MANY MANY files (28,819,704) from an old EMC Celerra array to a Netapp FA8060.

On source, I have about 2 TB of data that, with deduplication on, become 1.4 TB.

On destination, I'm already at 1.9 TB and rsync still doesnt' end, in spite of deduplication and compression saving of about same percentual of EMC.

How is it possible? Is there some basic difference of block size?

Thanks

Re: Great difference in space allocation between EMC and Netapp

georgevj — Wed, 12 Nov 2014 10:59:11 GMT

File based copying programs are not necessarily deduplication-aware. You may have to run dedupe once after the copying is complete, unless you have enabled automatic schedules.

from TR-3958: (http://www.netapp.com/us/media/tr-3958.pdf)

Compression and deduplication share the same scheduler and can be scheduled to run in one of five
different ways:
 Inline (compression only)
 Scheduled on specific days and at specific times
 Manually, by using the command line
 Automatically, when 20% new data has been written to the volume
 SnapVault software based, when used on a SnapVault destination

Re: Great difference in space allocation between EMC and Netapp

mimmus — Wed, 12 Nov 2014 13:32:14 GMT

Solved: there was +800 GB of snapshot copies forgotten after disabling snapshot reserve 😞