Hmmm... Looks like part of your message got garbled. I'll have to put on my Postmaster hat later and look into that...
ac220 is the 220, nac330 is the 330 and nac330-bak is the private 100mb network connection between the two.
Here is my command:
ndmpcopy nac220:/vol/vol0/testdir nac330:/vol/vol0/testdir -sa root:pass -da root:pass -d nac330-bak
I'd guess that the NetApp's aren't routing over the private connection. Try specifying the interfaces in the ndmpcopy command, like this:
ndmpcopy nac220-bak:/vol/vol0/testdir nac330-bak:/vol/vol0/testdir -sa root:pass -da root:pass
I'm not sure what the -d you're using is for, but I've used ndmpcopy to move ~6GB/hr over a 100mb-full connection from an F330 to an F740.
One other piece of info--the 220 is used to store Netnews data. When I am testing I have not turned news off, so the data is continually changing. When I do the actual transfer news will be turned off. But
No it's not. The ndmpcopy is doing a dump on the source filer, so the data is comming out of a snapshot.
I can't turn it off for my testing.
- Is my ndmpcopy command correct?
Looks good to me, just explicitly state the interfaces you wish to use.
- Is it abysmally slow because the news is still up?
Don't know. How loaded is the filer?
jason
One other piece of info--the 220 is used to store Netnews data. When I am testing I have not turned news off, so the data is continually changing. When I do the actual transfer news will be turned off. But
No it's not. The ndmpcopy is doing a dump on the source filer, so the data is comming out of a snapshot.
Technically you're right, the data being copied is static thanks to Snapshots, but with a (full?) news feed on an F220 both the file system and the filer's memory are being aggitated quite vigorously. This is sure to have a deleterious effect on the performance of ndmpcopy.
-- Karl Swartz - Technical Marketing Engineer Network Appliance Work: kls@netapp.com http://www.netapp.com/ Home: kls@chicago.com http://www.chicago.com/~kls/