kpltechgroup
asked on
Server 2003, Exchange, Blackberry-BES Server,
When I copy something from D:\ (sata disk 1,1)
to C:\ (system IDE disk 0,0)
The computer will stop responding remotely, drop exchange connectivity, and even locally...
Heres the odd part when the copy is done, the computer just 'wakes up' again. I have my page file as a partition as part of C (similiar to a swap file on linux-easier to manage).
Is there a way of limiting resources on the server so it keep enough to stay active for basic use?
2GB of ram is really really bad considering everything Im running its only got a Pentium D processor @ 3.6ghz but still windows should be smart enough to leave enough ram to do stuff no?
to C:\ (system IDE disk 0,0)
The computer will stop responding remotely, drop exchange connectivity, and even locally...
Heres the odd part when the copy is done, the computer just 'wakes up' again. I have my page file as a partition as part of C (similiar to a swap file on linux-easier to manage).
Is there a way of limiting resources on the server so it keep enough to stay active for basic use?
2GB of ram is really really bad considering everything Im running its only got a Pentium D processor @ 3.6ghz but still windows should be smart enough to leave enough ram to do stuff no?
rsoly777
Exchange tends to use up a a lot of Ram but releases it when it is needed but 2 GB of Ram seems low to be running all those services... Server 2003 Exchange and BES Server. Is this an actual Server box or a desktop made into a server. This can also b an issue.
ASKER
nah desktop, I know 2gb is slow but even before the BES server it was doing this, I only have 2 users on my exchange. it only happens when copying large files
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Both slots are fully I work in IT and work in a Server 2003/08 environment.
I was looking for more of a direct responce with what could be done if you were in my situation not what i should buy or get or do to the machine.
Everything is running at max. Thanks,
I was looking for more of a direct responce with what could be done if you were in my situation not what i should buy or get or do to the machine.
Everything is running at max. Thanks,
There are only a couple things I know you can do:
1) Add Ram, maybe 2x2GB sticks
2) Migrate to a real server
3) navigate to System Properties> Advanced>Performance>and Advanced and set the memory usage for performance of the system cache
4) There is also a product from Microsoft called Windows System Resource Manager. You can use Windows System Resource Manager to allocate processor and memory resources to applications, users, Remote Desktop Services sessions, and Internet Information Services (IIS) application pools. But there can be real complications if you really do not know what you are doing
kpltechgroup,
I know you were looking for more of an answer but the hard reality is that this is pretty much it.. Since you work in an IT environment you should know about desktops running server apps is not really very reliable due to the makeup of the hardware, just not built robust enough to handle all of this.
Sincerely RSOLY777
1) Add Ram, maybe 2x2GB sticks
2) Migrate to a real server
3) navigate to System Properties> Advanced>Performance>and Advanced and set the memory usage for performance of the system cache
4) There is also a product from Microsoft called Windows System Resource Manager. You can use Windows System Resource Manager to allocate processor and memory resources to applications, users, Remote Desktop Services sessions, and Internet Information Services (IIS) application pools. But there can be real complications if you really do not know what you are doing
kpltechgroup,
I know you were looking for more of an answer but the hard reality is that this is pretty much it.. Since you work in an IT environment you should know about desktops running server apps is not really very reliable due to the makeup of the hardware, just not built robust enough to handle all of this.
Sincerely RSOLY777
ASKER
I understand but at the same time I think there should be some sort of limit to where I can set the page file for instance or yes use WSRM to manage. Only problem is explorer.exe does the copying and explorer does the windows gui.
ASKER
I think it even might be the drive dying now that i think about it. Server or not its running 2003 which is an XP kernel. with 2 users and BES, its pretty much running XP with some background apps. Server 2003 should be smart enough to say this is what I have, and this is what I need to do. Leave this much open for...
Im going to swap the drives tonight so we'll see
Im going to swap the drives tonight so we'll see
ASKER
Drive tested okay, the answer to the question was the following:
Total Commander, then set the options to resource friendly transfer. It only copies at about 15MB/S but doesn't swallow up my full 20MB/s not allowing the disk to even read for basic usage.
Thanks for you help though rsloy
Total Commander, then set the options to resource friendly transfer. It only copies at about 15MB/S but doesn't swallow up my full 20MB/s not allowing the disk to even read for basic usage.
Thanks for you help though rsloy
Try using Robocopy in the command line I have found this to be useful in these situations where explorer just can't seem to hack it
ASKER
Yes I was also going to post that next using the /IPG switch.
The kernel is not the same as XP, but a further evolution the the kernel. XP is build 2600 and Win2k3 RC2 is build 3718 and Win2k3Ent SP-2 is 3790
ASKER
yes but my logic was xp was on it before, I copied 8GB files over with 2 Server VM's running and antivirus software... and it didn't freeze. my server is freezing me out of remote desktop and exchange. there has to be a way to allocate proper ram to the mere operation of the server...
Also what are ideal paging file conditions, same physical disk?
Also what are ideal paging file conditions, same physical disk?
For Size and Logic to what Page file should be set to take a look at this Microsoft KB Article http://support.microsoft.com/kb/2267427. Also a standard practice is that if you want the machine to write s dump file if the server crashes is to set the page file on the C drive. You should also set up auditing for system events. GPEDIT.msc from the run window. Expand Computer Configuration >Windows Settings> Security Settings> Local Policies and Audit Policy set audit system events for failure and possibly process tracking. Hopefully you will et some errors in your system event logs that will help point to where the failure is.