Increase HDD for Server 2008

[SlowLane]

I have just bought the VPS Starter subscription with 15GB disk space, which I believed to be more than enough for my needs. Imagine my shock and horror, coming from Server 2003 environment, to find 14GB of my 15GB package eaten up by the basic Server 2008 installation!
Now, to get 10GB more, I have to upgrade to the VPS Business at an additionalr 10GBP per month. That's a bit stiff just for a bit of extra disk space and 128MB of extra RAM (which I don't need anyway. Both are relatively cheap nowadays.

Therefore, I would suggest that the packages with Windows Server 2008 VPS are restructured to have AT LEAST 20GB allocated. As it stands now the VPS Starter is actually quite useless for any practical purpose.

On the upside, your service so far has been excellent, thanks!

[WH-Garry9]

Hello,

to the forums and we hope that you will enjoy your stay here.

The operating system of the VPS does consume some disk space of the VPS, however, it is not possible that the operating system will utilize 14 GB of disk space. It might be possible that there are some other applications installed on the VPS which must have utilized the disk space of the VPS or the logs must have utilized the disk space of your VPS.

In order to check the disk space utilization and get this sorted, I would request you to initiate a Live Chat session in our Windows VPS Support dept or send an email to our Windows VPS support dept at vps[@]webhosting.uk.com and our Windows VPS support dept will assist you with this

Please feel free to post if you have any further questions.

[SlowLane]

Server 2008 Disk space

Hi Garry, thanks for the welcome and your response.

The problem as I see it, is the way Server2008 stores multiple dlls etc for the side-by-side support. The winsxs folder on my VPS is using up 6GB of the 11GB being used by C:\windows.
There is actually very little installed, only the standard stuff like Plesk, SmarterTools, SQL 2005 and so on, that one needs to run a functional server. Fact remains 2008 eats up a stack more hdd than 2003 ever did, and what I am griping about is that your VPS bundle does not seen realistic where Server 2008 is the OS. Just a few more gigs on the Starter VPS would make it very nice.
On my 2003 server with 10GB disk and with everything installed, and a bunch of users and sites running, and I still have about 3GB free.
Anyway, it looks like an upgrade is in the only way out!
T.

[WH-Garry9]

Hello,

Actually, C:\windows consists of all the files of Windows operating system and therefore it is not possible to delete those files in order to get more disk space.

Applications like Plesk, SmarterTools and SQL 2005 also consume disk space of the VPS and therefore these applications also contribute in eating up the disk space of the VPS.

When it comes to Windows 2003 operating system, we used to offer Windows VPS's with Windows 2003 operating system, however, as Windows has stopped providing support for it, we had no option but to discontinue Windows VPS's with Windows 2003 operating system.

If you would like to have more disk space for your VPS, you can upgrade your VPS. You can send an email to our Billing dept at billing[@]webhosting.uk.com and our Billing dept will assist you with the upgrade

[sysadmin]

Hi Garry, thanks for the welcome and your response.

The problem as I see it, is the way Server2008 stores multiple dlls etc for the side-by-side support. The winsxs folder on my VPS is using up 6GB of the 11GB being used by C:\windows.
There is actually very little installed, only the standard stuff like Plesk, SmarterTools, SQL 2005 and so on, that one needs to run a functional server. Fact remains 2008 eats up a stack more hdd than 2003 ever did, and what I am griping about is that your VPS bundle does not seen realistic where Server 2008 is the OS. Just a few more gigs on the Starter VPS would make it very nice.
On my 2003 server with 10GB disk and with everything installed, and a bunch of users and sites running, and I still have about 3GB free.
Anyway, it looks like an upgrade is in the only way out!
T.

The Winsxs folder it the component store in the operating system. All of the components are found here. In practice, nearly every file in the WinSxS directory is a "hard link" to the physical files elsewhere on the system-meaning that the files are not actually in this directory. The WinSxS folder is supposed or designed to have duplicates of system and other components files. This is one of the main reasons for it being created in the first place. Earlier, you would have software installation programs that would overwrite system dll files with their own versions and cause other programs to break in the process. This was a huge problem and the WinSxS folder was created to solve this problem. WinSxS contains multiple versions of many files so that a program can use whatever version that it was created for, without bothering other installed software programs on the system. Deleting duplicates in this folder will have only one result. A complete reinstallation of the operating system and other programs.

In order to reduce the size of Winsxs folder, please try the methods below.

• Uninstall unnecessary applications if possible
• If your computer is running Windows Server 2008 SP1, please use Vsp1cln.exe tool to clean up the space or if your computer is running Windows Server 2008 SP2, please use Cmpcln.exe tool to clean up the space. (They are located under \%windir%\system32\)

To do this, please follow these steps:

1. Open an elevated command window
2. Type vsp1cln or cmpcln.exe
3. Type Y to start the cleanup process.

*Note: After you use this cleanup tool, you will no longer be able to remove the Service Pack, should any problems occur. Make sure that the system is stable before using. This tool is a one-time use tool. Once it's used it will no longer work on the same installation.

• Delete blobs.bin file & reboot the system.

The blobs.bin file which is located at \Windows\winsxs\ManifestCache\blobs.bin is used as a caching mechanism for servicing operations that are set to happen against the system. The file will naturally grow & shrink in size as various servicing actions take place against the machine & are satisfied. It the file grows out of control, let’s say it occupies several GBs space. You can safely delete this file without any fear of it damaging anything on the server as this file is just for caching. The file will be recreated when you reboot the system.

If deleting the file does not resolve the growth issue, set the permission of the file to deny everyone from writing to it. The stack will see a failure to write to this as a signal that it doesn’t need caching & it will move on servicing files..

NOTE: I'd recommend a complete system backup before trying anything..