Resized of C: drive
I was just at a customer site which was complaining of slow response from the server, this would occur everytime anyone attempted to get to a file within the shared drive of the server.
The client has a physical raid disks, that has a 12 gig partition for OS and the rest partioned for data. I'm considering resizing the OS partition on their server, the total space was about 200 Gbs. It seems as though all the programs were being installed onto the C: drive (on the OS side). The total amount that is free is about 128 Gb's left over.
My questions is if anyone can suggest a solution for this? As mentioned earlier, I'm considering resizing the drive, but like to hear what everyone has to offer and also what software, if any, was used to accomplish this solution, without corrupting the data?
In addition, there are about 15-20 users and two shared drives. They currently do not have a decent AV solution at the moment. Only some of the workstations are running standalone Symantec clients for AV.
The client has a physical raid disks, that has a 12 gig partition for OS and the rest partioned for data. I'm considering resizing the OS partition on their server, the total space was about 200 Gbs. It seems as though all the programs were being installed onto the C: drive (on the OS side). The total amount that is free is about 128 Gb's left over.
My questions is if anyone can suggest a solution for this? As mentioned earlier, I'm considering resizing the drive, but like to hear what everyone has to offer and also what software, if any, was used to accomplish this solution, without corrupting the data?
In addition, there are about 15-20 users and two shared drives. They currently do not have a decent AV solution at the moment. Only some of the workstations are running standalone Symantec clients for AV.
It's risky and unneccesary.
If only the OS were on the C: drive, you wouldn't have a problem.
Where is the page file? It can be several gigabytes and can be moved. (Click Start, right click on Properties, go to Advanced, under performance click settings, click advanced, under "Virtual Memory" click change.
If you have a large paging file on C:, create a second on on your data partition and change the one on c to be small, like 50 Megs.
Run treesize free to determine what folders are taking up to much room.
http://www.jam-software.com/freeware/index.shtml
Things like log files, backup catalogs, etc. can easily be moved.
If only the OS were on the C: drive, you wouldn't have a problem.
Where is the page file? It can be several gigabytes and can be moved. (Click Start, right click on Properties, go to Advanced, under performance click settings, click advanced, under "Virtual Memory" click change.
If you have a large paging file on C:, create a second on on your data partition and change the one on c to be small, like 50 Megs.
Run treesize free to determine what folders are taking up to much room.
http://www.jam-software.com/freeware/index.shtml
Things like log files, backup catalogs, etc. can easily be moved.
Actually since it is AV, then this is large to huge block I/O. Your C:\ drive needs little piddly 4K I/Os at a time (depending on NTFS) that has to compete with 64KB and much higher I/O requests. So you have even a worse config then I originally mentioned due to the RAID controller and disk drives having to deal with large sequential I/O requests simultaneously with small block somewhat random I/O. Your A/V requirements will chew up the controllers read/write cache which will pretty much take read cache out of the equation on C:\.
Reformatting won't fix that either. Only separating C: into a different RAID1 set will fix this. Also when you build NTFS, on 2nd partition of the new RAID1, then consider increasing NTFS chunk size.
Reformatting won't fix that either. Only separating C: into a different RAID1 set will fix this. Also when you build NTFS, on 2nd partition of the new RAID1, then consider increasing NTFS chunk size.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You need to add 2 disks and mirror them, and make the C:\ drive be on the mirror. Then with leftover space on the new RAID1 partition, create a 2nd partition for use with write-intensive I/O, like journals, scratch table space, etc.
You will see a major performance improvement, it may even more than double I/O performance on system as a whole, assuming you have a single partitioned RAID5 set.