SolutionBase: Expanding storage options with Windows Storage Server

by Derek C. Schauland | Mar 29, 2007 7:08:00 PM

Tags: Servers, Derek C. Schauland, storage, server, Microsoft Windows Storage Server, Windows Storage, storage server, Microsoft Windows

12 comment(s)

Takeaway: Windows Server 2003 is a fine file and print server solution, but it when it comes to large amounts of storage, you need extra help. Here's what you'll find in Windows Storage Server to help solve the problem.

This article is also available as a TechRepublic download.

Storing files and data efficiently has arguably been a problem since paper files were put in cabinets. For computer-based file storage, Microsoft has created a Windows server platform to expand the available options for network storage in Windows Storage Server. This article will present an overview of the product and how it operates; I will also fill you in on how to get your own copy of Windows Storage Server (WSS).

What is WSS?

WSS is a file and print server. Sure, these systems have been around for a long time, and any PC could provide these capabilities; but WSS brings a rich feature set built on Windows Server 2003, providing a more seamless integration with your network than an older PC. WSS can be clustered across multiple servers to create a seemingly endless storage network, allowing expansion as needs change. Recoverability is another benefit. I am sure that one or both of the following scenarios has crossed your path at some point.

WSS usage example

Let's assume you have a user who doesn't like to save files to the network server. The user has been reminded several times to save documents to the file server so these items can be backed up to tape. Because the files are large -- drawings, novels, bookmark lists, or Grandma�s super-secret chili recipe -- the user doesn�t want to risk these files being unavailable in a network failure, or to have a document save take abnormally long because of file location.

Then, because of a lightning storm or another unforeseeable act, the PC has to be rebuilt. Since this user saved files to a PC, the data may be unrecoverable, or only accessible by using an expensive data-recovery company. This could have been avoided by making use of the company file server.

In the above scenario, a recovery from tape backup might have been the fastest method of getting the user�s files. Data recovery jobs take time and might not be performed immediately, which leaves the user waiting on IT to get back the lost data.

Using WSS as your file storage platform, you can avoid the delays in data recovery from tape because you gain features like enhanced-volume shadow copy. This allows for point-in-time recovery of a file by taking a snapshot of specified folders at intervals throughout the day. For example, if you have spent the weekend getting your company�s file server migrated to WSS, and have configured volume shadow copy to snapshot the server at 12 P.M., 4 P.M., and 11 P.M. each day, the support ticket for lost files might go a bit differently.

When this user calls the help desk asking if you can restore the lost work from tape or somewhere, you could restore the latest snapshot of the file she needs in a few mouse clicks, causing much less rework than pulling the file from last night�s tapes.

These are high-level views of some things WSS can do. I will explore some of these key features in greater depth in future articles, but for now let�s look more at WSS.

Other great features

Exchange storage

You can store files and share printers just like the old-time file servers, but there are other features that those servers do not have, including the ability to store mail data for up to 15,000 Exchange users; allowing data to be stored more reliably than within Microsoft Exchange; and freeing up resources within Exchange. This allows Exchange data to be stored on a file server -- or cluster -- and be accessed by Exchange, leaving your mail environment free to perform mail tasks rather than also storing mail data. The Microsoft Storage Server Feature Pack is required to integrate Exchange Database storage.

Server consolidation

Since WSS is very scalable and supports clustering, you have the option to consolidate multiple file and print servers into one easy-to-manage storage platform. This reduces IT management and support overhead by limiting the number of servers you have to maintain.

SAN integration

WSS integrates with your existing SAN architecture, using that storage to make use of existing investment rather than bringing a replacement to the table. Using WSS in conjunction with a SAN can bring many benefits, not least of which is the speed of the SAN environment.

Recoverability

As mentioned in the above example, the ease of recoverability is second to none. The use of shadow copy technology to snapshot the server contents can greatly increase your ability to get files back on track without needing to run to the latest backup tape, providing peace of mind and reducing the time it takes to restore items.

Replication

With the use of tools from Microsoft partners, this platform can replicate with other WSS servers in multiple sites on your WAN. If your corporate office is in Los Angeles, but you have remote offices throughout the United States that need quick access to their own files, you can use replication along with WSS at these sites to ensure each day all of the files are up to date throughout your network. Doing this might also reduce backup time by bringing all of your data to a central location throughout the day, allowing backups to be performed faster at remote locations.

Where to get WSS

You can�t purchase WSS as a standalone solution. WSS is available from Microsoft OEM partners on many storage appliances. Check with your hardware vendor when you�re purchasing a storage solution to see if they offer it.

I have configured and used WSS for some time, and it is a great tool to help lower total cost of ownership while improving efficiency and reliability. While researching the product for this article, I discovered additional features that I will study further for my own use and in future articles. Even though this solution is OEM driven, it can save money in the long run by allowing management of fewer devices through a simpler interface.

12 comment(s)