asked on

Running Jetstress on SCC nodes

Hi

I am building an Exchange 2007 SP1 cluster, A/A/P, using SCC.

The CMS's are Exch1 and Exch2. The CNO's are ServerA, ServerB, ServerC - All Windows 2008 servers.

I need to run Jetstress to ensure the disk subsystem/SAN can cope with the requirements, however am not sure if I need to run the Jetstress on ServerA and ServerB, or on each physical node?

Secondly, I understand that we'll be using Node Majority for our Quorum, but I still can't get how this works in my head. Does anyone have a simple explanation/link?

Many thanks in advance.

ASKER CERTIFIED SOLUTION

TyBeatty

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

kam_uk

ASKER

Hi

Thanks for answering...

>"Personally when I have done this in the past I run it on the Virtuals EXCH1 and EXCH2 in your case"
But I haven't created the virtuals yet since I haven't installed Exchange on the servers yet?

TyBeatty

Glad to help. I just don't like leaving a server untested just in case.

MNS is a little harder. I will see if I can find you a good doc that breaks it down. Seems like most either get how ti works or it is cloudy to say the least so you are certainly not alone!!

SOLUTION

Jamie McKillop

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

TyBeatty

JJ brings a good point except I still like to test the passive node simply because all nodes identical does not mean identical hardware. I have had servers fail JetStress due to the servers Storage Controller.

Jamie McKillop

When you build a cluster all your nodes should be completely identical. That is the assumption I'm going off. Using mixed hardware is not recommended, but if you are, you should certainly run jetstress against each unique configuration.

JJ

TyBeatty

Agreed. But even identical hardware means a controller in each machine. Bascially if you have QLogic Fiber Channel cards for instance you are going to have 3 of them (possibly 6 for redundancy and such of course) But if you only test 2 of the 3 you are not testing that third card, even though they are all the same Type of card. Doe that make more sense?

To JJ's point though they should all be the same for sure!! You don't want 3 different type of controllers.

Thanks,
Tyson

Jamie McKillop

So, you are talking about identical brand/model of controller in each node? If so, you are referring to testing for manufacturer's defect. I see what you are doing but jetstress is a tool intended to lest the performance limits of a systems. It isn't realy intended to diagnose hardware faults. The hardware manufacturer should have tools that are better suited for system burn in and testing for hardware defects that you should run prior to jetstress.

JJ

TyBeatty

Indeed I agree. However to test the performance limits of the system still relys on that controller in the box. I would agree manufacturers should have tools.

I just don't personally like leaving a machine worth of variables not tested. Server BUS, Controllers, cables... I have seen boxes test at X and then you failover and test the other it is only performing at 1/2 X... I figure it is very easy to test why risk it and just test everything.