With the release of Windows Server 2008, Microsoft is making a number of improvements to the server's underlying storage mechanisms.
Discussed here are four of these improvements and what they mean for the typical IT organisation.
SMB 2.0
First shipped with Windows Vista, SMB 2.0, alternatively known as the Common Internet File System (CIFS), is also included in Windows Server 2008 and sports a number of improvements over its predecessor.
Most immediately noticeable in SMB 2.0 is support for symbolic links, a powerful feature that Unix admins have enjoyed for a long time. SMB 2.0 also supports the sending of multiple SMB commands in a single network packet, thus significantly reducing the network overhead required for communication. Also increased in SMB 2.0 are the buffer sizes and the number of concurrent allowed file handles, resulting in increased scalability for a pure Windows environment.
To work with older systems, Windows Server 2008 supports both SMB 1.0 and SMB 2.0 and automatically uses the version most appropriate for communication. SMB 2.0 is used only between Windows Server 2008 systems and with Windows Vista systems. SMB communication with all other operating systems uses SMB 1.0.
BitLocker Drive Encryption
Included in Windows Server 2008 is Microsoft's BitLocker Drive Encryption software. BitLocker is also included in Windows Vista Enterprise and Ultimate editions but, for Windows Server 2008, Microsoft has made improvements to the technology (which are likely to be extended to Vista when Service Pack 1 is released).
Under Vista, BitLocker can be used to encrypt the contents of the operating system volume. If you have multiple volumes of data on your desktop computer, however, BitLocker — at present — cannot be used to protect anything except the operating system volume. In Windows Server 2008, this limitation has been removed and all server volumes can be protected via BitLocker.
Full-disk encryption is usually considered primarily for mobile computers that can be easily stolen, but this technology should also be considered for use in branch offices or areas in which physical security cannot be guaranteed.
Self-healing NTFS
It's a bad day when you have to reboot a file server just to run chkdsk.exe to correct a minor corruption in NTFS. You have to schedule downtime for a server, maybe come in after hours or, in a worst-case scenario, interrupt your users while you perform this task during the day. But no more: with Windows Server 2008 comes an online NTFS corruption repair tool. While it is not a silver bullet for volume repair, it does correct many problems without having to reboot the server to run chkdsk.exe. Self-healing NTFS is enabled by default in Windows Server 2008 installations.
Symbolic links
Earlier, I mentioned that SMB 2.0 supports symbolic links. The fact that SMB 2.0 has this feature is great but it would be utterly useless without the same feature being included in the operating system. As such, symbolic links have been added to Windows Server 2008 — a feature that is long overdue. A symbolic link is simply an object in the file system that points to another object in the file system. A symbolic link appears as a normal file or directory object and can be used by an application as if it were the actual object.
Unix and Linux users have been able to use symbolic links for a very, very long time, and this feature can make it much easier to administer a system and share data.
Summary
Windows Server 2008 includes a massive number of improvements to the server's storage underpinnings that will result in a more stable and more available infrastructure for users.
Talkback
Symbolic links have not been added. They were implemented within ntfs as far back as windows 2000, the problem was getting the tools to set them up. As far as I know, based on my limited experience of windows server environments, the same applies to server 2003, and clearly now, 2008.
A microsoft tool called junction allows the creation of symbolic links between directories. In XP and above, direct file symbolic links could be created. I personally have used the tool a few times, mainly whilst building code trees with shared components and not wanting my source mixed. I'd assume the uses in a server environment make it a much more useful utility.
Just thought I'd point it out. The link to the tool is:
http://www.microsoft.com/technet/sysinternals/FileAndDisk/Junction.mspx
Oh and to clarify, the network symlinks is a new feature, its just the comment about ntfs' internal use of symlinks that was incorrect.
This piece was taken from our Australian sister site Builder Australia so it's sometimes difficult to fact-check every issue - but we'll look into the points you raised.
The main launch of Windows Server 2008, SQL 2008 and Visual Studio is happening next week and we are trying to track down opinions on the products. I am not sure what size organisations you work with or for but be good to know if you have had a chance to think about the platform and whether you'll be looking to migrate to it anytime soon?