Easing Server Sprawl and Storage Traffic Load

With stored information growing at an amazing rate, enterprise storage infrastructures face a crushing burden. Here's how a division of the largest wine and spirits distributor in the U.S. tackled the challenge.
Posted April 19, 2004
By

Drew Robb

Drew Robb


(Page 1 of 2)

According to most analysts, the amount of stored information is growing at a rate anywhere between 50 percent and 125 percent annually.

This places an enormous burden on the storage infrastructure. Servers are typically thrown at the problem, new storage arrays added, and additional SAN islands implemented. Yet performance suffers, disk space remains a problem, backup windows swell, and storage administrators are tied to the eternal firefight treadmill.

Such challenges faced Southern Wine & Spirits of California (SWS). A business unit of Southern Wine & Spirits of America, the nation's largest wine and spirits distributor with more than $4 billion in revenue. Operating in 10 states, it represents more than 300 suppliers, 5,000 brands and services 125,000 retail and restaurant customers.

"We were suffering serious amounts of downtime and having to add two or three servers each month just to keep up with storage demands," said Robert Madewell, director of networks at SWS. "As much as 10 percent of our storage resources were eaten up in non-business and duplicate files, and backup times were killing us."

SWS employs more than 2,000 people in California and maintains a sizeable distribution network that is managed from two sites -- Union City in Northern California and Cerritos in Southern California.

In total, 70 HP Proliant servers are installed and traffic is divided functionally rather than regionally between the two sites. Some applications are from Union City while others are housed at Cerritos. The application mix includes Exchange Server, proprietary collections software, a sales reporting system, SQL Server databases, fax servers, web servers and call center servers. Cisco networking gear predominates. Most servers run Windows 2000, though some NT units remain to be upgraded.

Organizationally, the storage management load was placed on an already overworked networking crew. This resulted in severe storage issues such as losing a couple of servers each month due to them running out of disk space.

Unfortunately, SWS had no way of tracking disk utilization. Thus, when a server filled up, users could be left with nowhere to store newly created documents. That generated a large volume of calls to IT to remedy system downtime. IT would spend hours manually correcting the problem.

"IT staff spent an average of two or three hours each day putting out storage-related fires and troubleshooting network storage issues," said Madewell. "At the same time, our eight staff had seen storage consumption grow fivefold without any more personnel being added to the unit."

Storage usage grew from 170G to 400G in one year in the north part of the state and from 90G to 200G in the south. Two or three servers were being added each month to cope with storage demands. And if a disk filled up, Madewell and his staff were forced to spend hours poring through it to see what space could be freed up.

But IT couldn't just delete anything that looked suspicious. PowerPoint presentations could either be valuable sales tools or unnecessary junk. MP3s could be personal music or marketing department tools for the Web. Lacking a means of central tracking of storage consumption and its content, two IT staff would routinely go through the various directories checking files one by one to determine which were of value and which could be deleted.

Page 2: Backup Woes


Page 1 of 2

 
1 2
Next Page





0 Comments (click to add your comment)
Comment and Contribute

 


(Maximum characters: 1200). You have characters left.