Troubleshooting Jetstress failure

Hi Experts,

We have the following environment:

Servers: Windows Server 2008 SP2 Enterprise x64
Jetstress version: 08.02.0060.000
SAN: EMC Clarrion CX4

I am in the process of building our Exchange 2007 SP1 SCC cluster for about 5000 users. There are three physical nodes, and there will be two virtual nodes.

We ran Jetstress for 24 hours, but it has failed :(

Test issues are that the Database LUN's have "x maximum database read latency errors"

Does anyone know how I can go about troubleshooting this? I assume this means that we can't install Exchange until these problems with the backend have been resolved?

Any help appreciated!
Who is Participating?
Jamie McKillopIT ManagerCommented:

How do you have your SAN configured? What are the total number of drives, what type of RAID, how many LUNs, do you have separate LUNs for the databases and transactions logs, how many databases do you plan on having?

Basically, the way you currently have your SAN configured, Exchange won't be able to read data fast enough given the expected parameters you entered into the jetstress tool. You may be able to fix this with a better configuration of your current SAN or you may need to expand your SAN to include more disks.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.