Hi Blake,

it is about I/O load at all. One of our branches has an old emc and we want to make them happy with Ontap. But to make them really happy we want to deploy a system which is as strong or even stronger as the old one (not to have complains all the time :D).

Maybe we even get them to use NFS instead of FC :P

Rgds

Jochen

-----Original Message----- From: Blake Golliher [mailto:thelastman@gmail.com] Sent: Tuesday, August 28, 2007 4:55 PM To: Willeke, Jochen; toasters@mathworks.com Subject: Re: clarion cx3-20 vs. netapp

A 3040A is probably the closest match for hardware. What is the competiton about? Iscsi / fc?

-Blake

On 8/28/07, Willeke, Jochen Jochen.Willeke@wincor-nixdorf.com wrote:

Hi toasters,

has anyone a clue to which netapp modell the clarion cx3-20 can be compared??

I have read an older toasters-post where it is put in the ring with a fas270c. Is this really a good competitor?

What do you think?

Best Regards and thanks for your opinion

Jochen

So is the NBU server using DNS? Are you backing up via hostname, or IP address (within NBU application)?

Assuming the filer has its Gbe interface using it's own IP address, have you pointed the NBU server to that IP address (the IP that the filer's Gbe interface is assigned) and not a hostname?

-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of John Foley Sent: Tuesday, August 28, 2007 3:09 PM To: toasters@mathworks.com Subject: filer - windows/netbackup server networking question

Hey toasters....

I have a networking question for you - thought I'd check here first to see if anyone else has this configuration, or if there are any ideas you might have that I could try...

I have a filer (F825) on a small network with a few servers and around 100 client computers. This network is being backed up using Veritas NetBackup v6MP4 running on a Windows 2003 server. It's all connected using 100Mb networking...however, for the filer, the backup server, and a few of the critical servers, I have a Gb 8-port unmanaged switch connecting a second interface on these machines together. This Gb connection is mostly for a particular application, which needs fast access from its servers (Sun Solaris) to the filer. This "private" network has no DNS, no NIS, no services at all - just a fast connection between the filer and some of the servers. I make this work by putting the "private" network addresses of these servers (ie, 192.168.1.x) in their hosts file, and then use "hosts" first in the nsswitch.conf file for the servers and the filer. Seems to work fine for the app - I can confirm that the servers and the filer communicate over the Gb network.

Now, here's where the problem comes in... I decided to try to use this private Gb network for backup, too. NetBackup seems to work fine with the Solaris servers on the private network - I can watch the output of a "netstat -gin 1" on them and verify that the traffic is running over the Gb network, and not the 100 Mb network. However, for the life of me I have not been able to get the filer to do the same thing...using the same command on the filer shows that the backup traffic always runs over the 100Mb network, and not the Gb one. I know the Gb network is up and running on the filer, since ping shows the correct network, and the app mentioned above is using it OK - but I can't seem to get NetBackup and the filer to agree to use the Gb network...

Anyone have any insight or ideas on this (rather strange, admittedly) problem ?

Thanks !

John

--

------------------------------------------------------------------------------ John Foley < johnf@comm.mot.com > sent from Windows using Thunderbird

Note: This message and any attachments is intended solely for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, legally privileged, confidential, and/or exempt from disclosure. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the original sender immediately by telephone or return email and destroy or delete this message along with any attachments immediately.