We have 2 databases running on the filer on the SQL (ver. 6.5) end. Both of them are 500MB. Relatively small but effective. We have encountered no problem with the filer. I haven't used the filer yet in a disaster recovery plan, but I'm sure I would have no issue. Best practice is to use SnapShots or Snap Mirror for added protection. I would consider running your SQL backups (log files) just a few minutes before a snap shot occurs, then in case of disaster, you have to most up to date information and can get your database back on line within minutes.

Create a separate ID for the filer and give it Admin privileges. Have it log on as a service. Do not use your Administrator account as if you change your password you will get suspect databases. -- This is from the trenches, things where you go, Ooops! when you are learning for the first time... Make sure it is on a different volume than your data storage. I have never experienced any down time with the filer. We have had it for over a year so far. It's a F740. We have two of them. The other serves UNIX and Oracle. Oracle embraces NetApp. Still wondering why Microsoft is so far behind the ball on this one??? It is as reliable as the hard disk you are using, with snap shot it becomes more reliable and faster than SCSI.

As for service from NetApp. It is A1. I have never seen any other company with such dedicated people. You've have already experienced this, I'm sure... They were here late in the evening, early in the morning. Their telephone support is top notch. They will not let you go until your problem is solved, and their expertise is number one.

Steven Gagnon	Visteon Canada Inc.	Tel: (905) 475 8510 Ext. 4207
NT / SQL System Administrator		Pager: (416) 753 3132
Markham, Ontario, Canada	FordNet: 854-4207	Fax: (905) 470 3296

"Man's mind, once stretched by a new idea, never regains its original dimensions." -Oliver Wendell Holmes