WHS As A Backup Suite

Although Microsoft is offering many features with WHS, it's WHS as a backup suite that is the single biggest feature of the OS. For Microsoft, this is more or less breaking new ground on an industry that is underdeveloped. At the corporate level there are numerous competting backup suites, but at the consumer level that WHS is targeting there's a handful of packages and Windows' own built-in backup system.

What does exist in the consumer space right now either does backups to the local disk, or if it's designed to do remote backups it does so via making whole copies of a disk, neither of which come close to what corporate software can do. WHS's backup abilities as a result are Microsoft's attempts to bring corporate features down to a home user, in line with the entire theme of WHS being a home's first server.

Central to the backup feature of WHS is the WHS Connector package, which serves as both the backup client for the machine and the key piece of software that integrates a machine into a WHS server. Once a new client is connected, the console can be used to configure the backup settings for that individual machine; out of the box all clients are set to backup between 12am and 6am, and most users will only need to enable backups for the new client. The client also has some control over the backup process without using the administrative console, and can initiate a backup at any time. Finally, the connector software allows WHS to keep track of the general health of each client and report on problems such as missing updates.

On the server side, anyone familiar with corporate backup software will undoubtedly find themselves at home with WHS. Along with scheduling backup times and triggering backups, administrators can exclude folders (but not files or file types) on a per-machine basis, view a list of backups, and manually purge old backups. To that extent WHS will also purge old backups automatically based on retention settings. All of this past the first backup is done incrementally to minimize space used and data transferred.

Furthermore, as the developer of Windows, Microsoft gets a strong ace up their sleeve in backup management: the volume shadow copy ability. We've previously talked about this in our Vista review as Microsoft is using it to run Vista's Previous Version feature, and on a server this ability is much more potent. Because WHS can back up the entire contents of a system (including the OS) it will back up a lot of redundant files; with a 10 client limit that's potentially 10 copies of Windows that need to be stored. Volume shadow copy can recognize the redundant clusters making up all those files and only store a single copy, so in a completely homogenous environment WHS will only need to store a single copy of Windows for the entire house.

The benefits of this further extend to user data, as any other duplicate files (e.g. music) will also only be stored a single time. The incremental backups that WHS does further benefit from the cluster level identification as WHS will only need to store the cluster changes of a file whenever a file is changed. Finally all of this is compressed to squeeze out whatever last bit of space savings can be found. All of these abilities due to volume shadow copy results in WHS backups being exceptionally efficient and making it possible to back up several machines with a drive much smaller than their combined drive space.

The Interface of WHS WHS As A Backup Suite, Cont
Comments Locked

128 Comments

View All Comments

  • mindless1 - Wednesday, September 5, 2007 - link

    Surely the backup client can be disabled (On one of the two)? I would be very surprised if 2 WHS systems can't coexist given a configuration change if you just wanted to avoid the wasted redundancy of having both make backups. That is, unless MS had deliberately chosen to prevent the two from getting along.
  • ATWindsor - Tuesday, September 4, 2007 - link

    Does it souppert proper raid, like raid 5 for instance? That fits my use a bit better than this duplication of files. WHS looks interesting, but seemingly a bit to primitive to be honest, seems to be missing quite a few more or less nescessary features.
  • Rolphus - Tuesday, September 4, 2007 - link

    The choice of OS should be entirely separate to RAID considerations. Software RAID5 is a bit of a waste of time, seeing as any performance advantage over just mirroring the data would be more than offset by software parity calculations. I don't see any reason why a BIOS-level RAID system (as supplied by many high-end and server motherboards and add-in cards) wouldn't be supported by WHS; Windows 2003 Server supports any RAID level you care to throw at it.
  • mindless1 - Wednesday, September 5, 2007 - link

    Most people won't care about parity calculation overhead, it's not as though the system is being used like a PC or workstation, that's practically ALL the system would be doing besides sitting idle, particularly given the rough spec of a 1GHz or more processor which is not at all needed just to serve files. Maybe with GbE, you might want a 300-400MHz processor to keep networking performance good but on a system that old you'd probably be bottlenecked by the PCI bus before anything else.
  • yyrkoon - Wednesday, September 5, 2007 - link

    What is wrong with software RAID, if that is all the system does(server storage) ? In my book, implementing *any* so called server OS *needs* to have at least RAID1, and should have RAID5 in software. If not, there is not realy reason to stop using WinXP Pro, with a few registry hacks tp bypass the RAID5 limitation.

    Anyhow, why pay for something that is lacking when you can get an OS that does it for free, or another earlier version of windows that will do it with a few hacks, and yu're already familiar with.

    As I said in an earlier post, I used WHS for a few days several months ago(early beta program), and did not like what I saw. So . . .
  • ATWindsor - Wednesday, September 5, 2007 - link

    Software raid5 can have very good performance, modern computers are fast, besides the main consideration is not wasting so much space, if you want to have som security for your files, you get by on loosing 1/4 insted of 1/2 of the space.

    The main advantage off WHS is the whole storage-pool-setup, I hope they implment somethin similar in w2k3.

  • Gholam - Sunday, September 9, 2007 - link

    I tested software RAID5 on an nForce4 SLI motherboard (DFI LanParty nF4 SLI-DR) with Silicon Image 3114 chip and 4x WD 500GB drives. Reads were in 11-14MB/s range, writes sub-10MB/s, and CPU load was near full, on an Athlon 64 4000+.
  • ATWindsor - Sunday, September 9, 2007 - link

    Try to test a proper software-raid, instead of the inbuilt nforce-crap, just because you tested a poor solution doesn't make all solutions bad.

  • Gholam - Sunday, September 9, 2007 - link

    It's not nForce, it's SiI3114, nearly ubiquitous on higher-end motherboards of that era, as well as present on many lower-end PCI cards. Building RAID5 on an "affordable" solution from Silicon Image, Promise and such will give you exactly that kind of performance, as well as guarantee a high probability of data loss due to driver/firmware bug. In order to run RAID5 you need a proper controller from Adaptec/LSI Logic/3Ware, and that costs big bucks.
  • Ryan Smith - Tuesday, September 4, 2007 - link

    It only supports proper RAID if you can configure it all in the BIOS. Any kind of softRAID that needs Windows' help isn't supported. Basically it needs to appear as 1 disk to Windows.

Log in

Don't have an account? Sign up now