Updated Again: disclaimer -- shooting from the hip here. I know how it sucks to have people pissed at you for IT related issues!! I have zero knowledge of this

Updated Again: disclaimer -- shooting from the hip here. I know how it sucks to have people pissed at you for IT related issues!! I have zero knowledge of this company and have only read about them today. Basically, this just boils down to a time issue. No data was lost it just took time for things be to rosy again. Restoring from backups or switching to a DR site takes time too. If you have never fully tested the DR site it might take a long time. It it easy to be Cpt. Obvious; "Well, there's you problem right there" in cases like these but it just sounds like they need better documentation about what to do in the event something like this happens. Forgetting about the DR site for a minute. Why is the NetApp a single point of failure?? Given they are extremely stable and running multiple heads further reduces this but if a single issue with one array causes massive downtime then you might want to think about a snap mirror to a second filer. Switching to a different storage vendor doesn't sound like it will fix the underlining issue here!!