We would like to use some form of replication to mirror our NetApp 230 to another NetApp in a remote location. Has anyone on the list tried to do this before? Any suggestions on how to tackle this problem?
Thanks in advance for any help you can provide-
Vance
BTW - If it matters at all, we are looking to replicate ~2M files totaling about 50GB. The WAN link would be fairly fast (> 45Mb).
......................... ........... Vance Huntley .. Director of Technology ............ TheGlobe.com . vance@corp.theglobe.com . http://www.theglobe.com .........................
+--- In a previous state of mind, vance@corp.theglobe.com (Vance Huntley) wrote: | | We would like to use some form of replication to mirror our NetApp 230 to | another NetApp in a remote location. Has anyone on the list tried to do | this before? Any suggestions on how to tackle this problem?
This is a hairy issue. We have a similar need (East coast replication of our West coast filers) but I am waiting to see if something else comes along that will make this a simple issue...
Depending on how frequently your data changes, how closely you need the filers to be in sync, you might get away with something like rsync running once every so often (although, a 230 with 2M files and lots of deltas may make this a slower process) or you can try the ndmpcopy (using incrementals). Neither solution is optimal.
Alexei
At 10:08 AM 5/29/98 -0400, Alexei Rodriguez wrote:
+--- In a previous state of mind, vance@corp.theglobe.com (Vance Huntley)
wrote:
| | We would like to use some form of replication to mirror our NetApp 230 to | another NetApp in a remote location. Has anyone on the list tried to do | this before? Any suggestions on how to tackle this problem?
This is a hairy issue.
Ugh. Tell me about it. :-(
We have a similar need (East coast replication of
our West coast filers) but I am waiting to see if something else comes along that will make this a simple issue...
Depending on how frequently your data changes, how closely you need the filers to be in sync, you might get away with something like rsync running once every so often (although, a 230 with 2M files and lots of deltas may make this a slower process) or you can try the ndmpcopy (using incrementals). Neither solution is optimal.
About 5k new files and 2k deleted files per day. Because of the nature of the data stored, files are never modified and filenames are unique across all time (that is, if a file is deleted there wil never be another file with that name). New files need to be mirrored in near-real-time, no more than a 5 minute delay. File deletions are not very significant, and could be much less than real time.
Vance ......................... ........... vance huntley .. director of technology ............ theglobe.com . vance@corp.theglobe.com .........................
In an upcoming release in the summer, NetApp will provide functionality that allows you to copy volumes to another filer (or to the same filer). It will use technology that is fast. The target volume will not be online, however. Still, this initial function will provide some disaster resiliency. This function will be a charged, price-listed option.
David
Vance Huntley wrote:
At 10:08 AM 5/29/98 -0400, Alexei Rodriguez wrote:
+--- In a previous state of mind, vance@corp.theglobe.com (Vance Huntley)
wrote:
| | We would like to use some form of replication to mirror our NetApp 230 to | another NetApp in a remote location. Has anyone on the list tried to do | this before? Any suggestions on how to tackle this problem?
This is a hairy issue.
Ugh. Tell me about it. :-(
We have a similar need (East coast replication of
our West coast filers) but I am waiting to see if something else comes along that will make this a simple issue...
Depending on how frequently your data changes, how closely you need the filers to be in sync, you might get away with something like rsync running once every so often (although, a 230 with 2M files and lots of deltas may make this a slower process) or you can try the ndmpcopy (using incrementals). Neither solution is optimal.
About 5k new files and 2k deleted files per day. Because of the nature of the data stored, files are never modified and filenames are unique across all time (that is, if a file is deleted there wil never be another file with that name). New files need to be mirrored in near-real-time, no more than a 5 minute delay. File deletions are not very significant, and could be much less than real time.
Vance ......................... ........... vance huntley .. director of technology ............ theglobe.com . vance@corp.theglobe.com .........................
I want to follow up with a clarification. I am talking about a volume copy function which has to be kicked off each time, not a synchronized, remote, online mirror.
In our delivery this summer, the resulting copy of the volume will not be online. It can be brought online as needed if the source filer or volume is no longer available.
Over time, we will extend our functionality, but we won't have synchronized, online, remote mirrors this summer.
David
David Yu wrote:
In an upcoming release in the summer, NetApp will provide functionality that allows you to copy volumes to another filer (or to the same filer). It will use technology that is fast. The target volume will not be online, however. Still, this initial function will provide some disaster resiliency. This function will be a charged, price-listed option.
David
Vance Huntley wrote:
At 10:08 AM 5/29/98 -0400, Alexei Rodriguez wrote:
+--- In a previous state of mind, vance@corp.theglobe.com (Vance Huntley)
wrote:
| | We would like to use some form of replication to mirror our NetApp 230 to | another NetApp in a remote location. Has anyone on the list tried to do | this before? Any suggestions on how to tackle this problem?
This is a hairy issue.
Ugh. Tell me about it. :-(
We have a similar need (East coast replication of
our West coast filers) but I am waiting to see if something else comes along that will make this a simple issue...
Depending on how frequently your data changes, how closely you need the filers to be in sync, you might get away with something like rsync running once every so often (although, a 230 with 2M files and lots of deltas may make this a slower process) or you can try the ndmpcopy (using incrementals). Neither solution is optimal.
About 5k new files and 2k deleted files per day. Because of the nature of the data stored, files are never modified and filenames are unique across all time (that is, if a file is deleted there wil never be another file with that name). New files need to be mirrored in near-real-time, no more than a 5 minute delay. File deletions are not very significant, and could be much less than real time.
Vance ......................... ........... vance huntley .. director of technology ............ theglobe.com . vance@corp.theglobe.com .........................
-
Alexei Rodriguez -
David Yu -
vance＠corp.theglobe.com