kblackwel
asked on
Slow win2k3 file server
We used to have a windows 2003 server that acted as a file server. The file server handles folder redirection for 200+ users. Their dfs root is on the qx100. Term servers pull user profiles from the San via smb. It had a 2gig hba connected to a ax100.
That server was also a domain controller.
So I had another machine with the same hba (qla200) installed win2k3 and attached the ax100 to it.
If a couple people log in, it's fine, but when the day gets going that 200+ people start to log in, it get to the point where
1 can't rdp to server, but can ping and access wmi controls
2 file serving is speratic at best. Some can access their pst file, some can't.
Seems like datas corrupt, but after hours all data seems fine.
Machines running out of resources. Lookng for ideas while I'm on my way to datacenter to look at machine.
Thanks
That server was also a domain controller.
So I had another machine with the same hba (qla200) installed win2k3 and attached the ax100 to it.
If a couple people log in, it's fine, but when the day gets going that 200+ people start to log in, it get to the point where
1 can't rdp to server, but can ping and access wmi controls
2 file serving is speratic at best. Some can access their pst file, some can't.
Seems like datas corrupt, but after hours all data seems fine.
Machines running out of resources. Lookng for ideas while I'm on my way to datacenter to look at machine.
Thanks
Ooops just re-read my post. It should read "Stopping snapshots made things a million times better."
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I turned out to be 2 things. The first was the snapshots that we were running every couple of hours would kill the server for 20mins (ish). That made things a million times better. then there were the .pst files.....
MS dont recommend putting pst files on a server as they use up a lot of connections and them open.
Have a read of the following....
http://blogs.technet.com/askperf/archive/2007/01/21/network-stored-pst-files-don-t-do-it.aspx
We ended up moving all of the PSTs back into exchange (and created a GPO that stopped new psts being created) where we could benefit from single instance storage and the problem NEVER reoccured.
Not really a solution but definately something to consider.