Testing Windows Home Server
On our search for a good file server and centralized backup solution, I stumbled across Windows Home Server. The description sounds very good and seemed to be the perfect solution for our office: this server system automatically backs up Windows clients over night and has a unique data-storage system, which makes it possible to add and remove different harddrives to the storage, making it larger without the hassle of moving files from one drive to the other. It’s a kind of software raid (stripe).
It also comes with a handy administration console, which can be accessed from every client machine. This console can be extended easily with addins by third party software developers. As some TapiRex customers already asked about a Windows Home Server console addin for TapiRex, it was a good point to get started trying this new Windows Server operating system.
So I tried to find it in the MSDN Subscriber downloads, as we have several subscriptions to MSDN Universal, which theoretically includes all Microsoft operating systems and all other software. As I was unable to find a download there, I googled the web and found out that Microsoft decided not to make Windows Home Server available in MSDN Subscriber downloads. Urgh. So we pay lots of money to not be able to get access to a Windows operating system to develop new addons for it. What a decision…
So I just ordered a Windows Home Server license from eBay, which was delivered quickly and did only cost around 90 Euros.
Installation
When installing the Windows Home Server incl. Power Pack 1 (which is based on Windows 2003 Server) on one of our servers in our server rack, it stumbled upon our 3Ware RAID controller, which is installed with 2 x 160GB harddrives as system drives in a mirrored array to speed up the operating system. I was able to load additional drivers for that controller from an USB stick, but when the system rebooted after the first installation step, it has forgotten about the driver.
Googling for this issue, I had to find out that this is a bug in the Windows Home Server installation 
. As the text-based setup does not have access to a USB stick to reload the drivers, I had to go out to buy an external 3.5″ USB disk drive, as the setup only accepts additional drivers from the A: drive. Do you remember 3.5″ disks? It was not that easy to find a disk to store the driver to get past this installation step. These disks have gone so rare here in the office 
. Previous installations of Windows 2003 did not have this problem…
But after that, setup was pretty easy. I was able to install all hardware components and to setup the Drive Extender. After setup, you have to install a small client connector software on every client machine that should backup to that Windows Home Server, which was pretty easy as well.
In-day-usage
The good thing is that the backups worked pretty well. Also, some of the available plugins from third-party developers are very useful.
But there also were some problems:
Delays in accessing shared folders: we experienced some delays in accessing shared folders on the server. Every employee in the office has some drives mapped to shared folders on the file server. This includes a personal folder and some general folders for everyone. While browsing in these subfolders on these drives, there was sometimes a lag of several seconds that makes it impossible to work with it fluently. For example, we store our downloads company-wide in a folder on the file-server. But the “save file” dialog in the webbrowser sometimes hung up for up to 20 seconds before it was able to show the folder and save the file. Once the data transfer starts, it’s fast and reliable.
Bug in drive’s size-calculation: When you map shared folders on the Windows Home Server as local drives, Windows XP and Vista are unable to show the correct drive size. After searching the web and asking some experts in Windows Home Server forums, I found out that this a known bug in Windows Home Server and that you can’t do anything about it:
Popups on all client machines: when you have the client connector software installed, all warnings from the Windows Home Server or one of it’s clients is shown on every client machine. So every user gets popup messages like “Computer X does not have virus protection installed”, “Backup on machine Y was not sucessful”, and many more. I was not able to find a way to customize these popups so that there are not shown to our apprentices for example.
So, after nearly 2 weeks in production, I am currently installing Windows 2008 Datacenter on that server machine, as the problems shown above disturbed our daily workflow that much that it was not worth it. We will install Windows Home Server as a VMWare virtual machine instead to do some software development on it. A PamFax addon is also an idea for it. What do you think?
I will report back how this all worked with Windows 2008. Does anyone have a different suggestion for a solid and fast file server operating system + client backup possibilities?
