New subject: volcopy and snapmirror performance

31 Dec 1999


      We did this transfer on a site to migrate around 150GB data between F630 to F760
- it went though at around 14-15MB/s (50+GB/hour) on a direct cross-over GbE
connection.
Although it's not a requirement, I would sugggest using the same versions of
ONTAP - we hit a hardware problem on one filer which aborted the transfer, &
there was a problem with aborted transfers when the filers were on 5.2.1 and
5.2.3 resp. - we upped them both to 5.2.3 & all was well ;-)
Cheers
Mike
...
-----Original Message-----
From: owner-dl-toasters@netapp.com
[mailto:owner-dl-toasters@netapp.com]On Behalf Of kevin graham
Sent: 30 December 1999 11:54
To: toasters@mathworks.com
Subject: volcopy and snapmirror performance
We're looking at moving 287gb (~10.7m inodes) worth of data 
from a 630 to
a clean volume on a 760.
To schedule the downtime, I need to know if anyone has 
ballpark figures
for calculating the tiem for a volcopy. The filers are well 
connected
(gbit ether on both of them), and I can sacrafice big chunks of
performance to make this go in a timely manner. (the 
100mbit interfaces
are inactive as well, if those should just be strapped together)
Later on, we're looking at trying to snapmirror 536gb 
(~17.2m inodes)
spread pretty evenly across two volumes between two 
locations. Are there
numbers available on the approximate overhead of the 
snapmirror protocol
(delta bytes * overhead), and how often it would be 
feasible to run it
(I'd prefer something in the neighborhood of 5-10 minutes).
The best numbers I could find on NOW were "36GB/hr will 
drive the cpu to
100%" without any reference to the filer model, cache sizes 
(the filer
does do read-aheads, right?), inode density, etc...
thanks.
..kg..

RE: volcopy and snapmirror performance