Buying everything from one vendor has advantages and disadvantages. The advantages include:

• The solutions are integrated and will work together better than individually acquired products.
• Dealing with a single support organization results in faster resolution of issues and greater concern from the vendor because it has greater responsibility (and greater revenue).
• Cost will be reduced with what is presumed to be a volume purchase.
• There will be fewer vendors to deal with, which takes less time in purchasing and implementing.

The downside includes:

• The costs might be more because customers could end up having to purchase a more expensive component in the package than they would normally select.
• Customers might not get the best individual product available when a bundle is purchased, and buying a bundle might eliminate potentially better solutions from consideration.

Building a complete storage and storage software portfolio has become a major focus in vendor acquisitions. Dell’s recent purchase of Quest Software is a good example. Dell now has storage, storage management, data protection software, and other important software that can be packaged as a complete solution. This makes Dell more competitive with other major vendors who have integrated offerings.

For vendors, selling integrated storage solutions also make sense. These packages bring larger deal sizes, and the amount of money per time invested in the sales opportunity can be much greater. A larger sale also results in a greater footprint (more products sold to a particular customer) for the vendor. With more products (from the integrated solution) installed in a customer environment, there is much greater difficulty for the customer to turn to another vendor. While not a lock-in, there is greater resistance to change vendors.

Judging from my interactions with IT customers, I believe buying bundles from a single vendor will become the prevalent purchasing pattern. The main reason is because the purchase of the integrated solution is simpler for IT than buying multiple products from different vendors. It also requires less training. That simplicity translates to less administration required and less operational expense.

You can expect to see the trend of more integrated solutions continue. For the IT customer, it is important to understand what they may be giving up with a single solution commitment.

Simplifying the operational environment is a constant struggle, and anything that makes buying and using storage less complex is a big help. This Evaluator Group article on storage efficiency has more information on how to optimize storage.

(Randy Kerns is Senior Strategist at Evaluator Group, an IT analyst firm).

Okay, maybe not the audit part, but for most of us, getting the type of disk we need in the quantity we need it is an uphill battle. Add SSD, deduplication, and longer-term retention to the mix, and things are getting a bit hairy with my budgetary requests. I’m at such a point now with a few of my smaller clients, and when they get that “you’re crazy” look, I bring up the chargeback model.

I think I just heard a collective sigh from the interwebs.

I understand both sides of the chargeback dilemma: the accounting side, that has to somehow keep track of all this without keeping track of all this; and the IT side, that is constantly being painted as the cost center only because no one is taking ownership of their parts of the “plumbing.” People (read departments) will request outrageous resources when they don’t have to directly foot the bill. That part I get, but are they so vehemently against accounting for their infrastructure usage?

In my opinion, chargeback would actually lead to better data management habits — at least in the long term — because if you have to pay for everything out of your own budget, then you’ll be more careful about separating what you need from what you want. How many of our managers and accounting folks have processes in place to account for each department’s use of the “utilities” that make up IT and understand that IT isn’t the root of all expenses?

I had an energetic debate with a co-worker about this very issue. I took the stance that chargeback is the way to go. He offered a more community-oriented accounting method. We went back and forth, point and counterpoint, until concluding that it just depends on what your business environment will support and the level of organization that business has in place.

For instance, if you have a well-organized, project-oriented IT environment, and have a project portfolio ready for sizing, you can plan a community budget very well and effectively fund addition to your infrastructure through a single IT budget. The reality from <i>my</I> experience (read, SMB clients) is that most companies are not so well-organized, don’t have a project portfolio for the next 12 months, and will not be able to identify budgetary requirements for infrastructure improvements.

In these cases, chargeback (or, at the very least, departmental accounting) is key to being able to answer my opening question with confidence.

Traditional SAN storage may be easy to bill for, but what of virtualized storage? Take it a step further, how about Softricity/Microsoft’s Softgrid? (Softricity is the company Microsoft acquired not too long ago that allows for application-level virtualization as opposed to host virtualization.) How do you quantify and itemize a streamed, virtualized application?

Then there’s the question floating just below the surface of the chargeback debate: How do I, as a department, know you are giving me what I’m being “billed” for? That question opens a giant can of worms in my mind (and there are already creepy crawlies up there, no need to add worms to the mix).

The crux of what I’m getting at is: Are we as technologists — and storage pros specifically — asking for too much or too little when it comes to chargeback? Are there still companies out there that don’t see the light when it comes to chargeback and departmental accounting. Should we as storage pros be leading the way for other areas of IT to follow our example?

First, I need to define constraints before we dig into the meat: What I consider a small to medium-sized business (SMB) is a company that would have a problem justifying a $50,000 purchase for a product that would perform a migration then have no use for it for 3 to 5 years until they migrate again, or have one to two IT people doing the work, or think a SAN is just a typo for SAN-D that you’d find at a beach. I know IBM, Sun, Symantec et al. have migration services but I’m looking at the smaller business space where people need to store more on tighter budgets that were small to begin with.

We’ve recently upgraded our SAN infrastructure and while our data migration chores aren’t all that intense, I’d still prefer that a computer did it. I’ve built some tools to handle my cleanup work (I’ll share them as soon as some bugs are worked out) but only because I couldn’t easily buy something to do the same or better. Now I’ll admit that sometimes I can be blind or ignorant (or both), but I’ve noticed a HUGE gap in the availability of migration tools for the lower end of the SMB spectrum. With me being a part of The Matrix like I am, or akin to Mr. Universe from Serenity, one would think I’d have caught a whiff of something significant.

With all the hoopla about the structured and unstructured data needs of SMBs and vendors tripping over themselves to create products for this space (HP’s new MSA and NetApp’s StoreVault come to mind), it’s hard for me to swallow that data migration for that very same SMB space wouldn’t be just as hot.

If you sense some irritation on my part, you’re spot on. While it may not directly affect me, it most certainly does affect those who rely on my expertise. I’d like to be able to say “Hey, just get Product X from Vendor Y and it will take care of at least 60% of your migration woes. ”

Bigger irritation: From my admittedly unscientific data gathering, I’ve found that when I ask SMBs about migration, the most popular answer is backup software. “Well, we were planning on just restoring the server to a folder on the array. Why? Is that bad?”

Most times the answer is yes, it is bad. In my presentation at Storage Decisions I talked about what’s actually stored on your centralized storage and file shares, and most of it is stuff that shouldn’t be there, like MP3s, AVIs, etc. By restoring backups to the new array, they would simply be carrying forward a wasteful, and potentially harmful, data storage practice.

Furthermore, if you subscribe to the numbers from major analyst houses, you wouldn’t be able to restore 30% to 40% of the data you had on backups anyway, so relying on them for migration could be an exercise in futility. My own unscientific polling has come up with a similar amount of people that say, “We can never pull anything back we really need in a pinch, unless you count the i386 directory.”

I’m sure there are a couple of you out there thinking, “This guy is losing it. Why can’t he just create a filter for his backup software and have it selectively restore said data, or, better still, create a simple shell (bash, csh, powershell, vbscript, jscript, insert the rest here) with some regular expressions to handle that work. He could even stick something into Visual Basic or managed code (ducks the rotten tomatoes) that does the work!!

While I (or the people I work with) could certainly do all those things (with the help of Google and copious amounts of coffee), we aren’t the targets I’m talking about here. The people I’m talking about, who rely on the expertise of people like me or of consultants, cannot — or in some cases will not — for their own reasons. Homegrown apps also require a deep level of knowledge of the environment you are crafting them for, and you can see how it would be a difficult proposition for one person once you grew to 15 or 20 different small environments simultaneously.

Because of my own issues of dealing with not only illegal/unwanted data but depreciated legacy data that can be deleted and need not be dragged around for every iteration of a data storage infrastructure, I have come up with a simple and reliable data classification scheme. I should be able to ring up vendor A or B and say, “Give me something that will take my criteria and email me when it’s done moving and verifying my stuff, but DOESN’T cost $50,000.” There are cheap tools out there that will transfer file and NTFS permissions, even shares and share permissions. But, while very helpful, they don’t address the issue of the data itself.

I don’t live in an ivory tower, nor am I a strict idealist, but this topic does aggravate me. If companies can figure out how to turn one reasonably powered computer into 20 adequately powered ones for free, or have my economy car listen and respond to me intelligently when I want to listen to the Black Eyed Peas, why can’t I have a data migration tool that doesn’t cost as much as an SMB’s quarterly gross income?

The world of video surveillance is changing so rapidly that the user and the traditional supplier are both in a state of frenzy. It is within this transformation that the role of IT is becoming increasingly critical. The reasons for the increase in video surveillance are pretty easy to understand. Post 9/11, enterprises as well as governments are all adding or increasing video surveillance to the security equation. Of course, casinos and banks have always been the leading users of video surveillance, but now everyone is in the game. On a typical day, a person living in a city may be videotaped five or more places, as he drives to work (and passes through specific traffic lights), parks his car in the company parking lot, enters the building, makes a trip to the bank at lunch, grabs a couple of items at the local K-mart and heads home. There are all kinds of privacy issues that can be debated, but I am staying away from that. At least for now. Right now, I am more interested in the technology and IT’s increasing role in video surveillance.

Traditional video surveillance equipment was not designed to deal with this onslaught and is gasping for air. It is being replaced almost completely with IP-based equipment.  That’s where you come in. Until now, most video surveillance equipment was based on CCTV (closed circuit TV), which basically meant the cameras, which recorded analog video, were hooked up via coaxial cable to the central point, where the video was taped on VCRs. Later, DVRs converted the analog signal to digital at the central location before storing it. But, these technologies cannot deal with the onslaught of data from more and more cameras and the fact that cameras are increasingly adding higher resolutions.

The latest crop of cameras records video in a digital format, and compresses it using MJPEG or MPEG before transmitting it over standard IP network to a central location that stores the data on scalable disk arrays. Once in the realm of IP, all the goodies we are used to in IT become available to an industry that still thinks of guards manning physical structures. Centralized management become feasible, data can be accessed asymmetrically, from multiple locations, replicated when appropriate. Another level of sophistication is being added at the end points. Now cameras can be activated when they detect motion or switch into a higher resolution if certain criteria are met. Video analytics allow software to recognize facial characteristics. Searches can be conducted for specific objects or people. You get the idea. It is like James Bond gadgetry becoming available to regular folks. But, that is reflective of the world we live in.

I think you (IT) need to be prepared to play a major role in this transformation that is occurring. You are the resident experts in storage and, at this point, pretty well up on IP technologies as well. Video surveillance simply becomes another application you have to support. So, if you are not already deeply involved in the selection and day to day management of the video surveillance equipment, it is only a matter of time. Security people who used to make decisions on such purchases without any consultation, will now insist on your involvement. You should gladly offer to help.

Another important thing to realize is that the type of storage you end up selecting for these applications will very likely be different than storage for other applications. For video surveillance the attributes that matter for storage include cost effectiveness (dirt cheap), highly scalable across both capacity and performance (cannot afford to create islands of storage), low entry price point, cost effective availability (mirroring may be too expensive), protection from disk drive or nodal failure and, most importantly, it needs to IP-based. Everything else in this environment is IP based, so making storage IP-based makes it easier to understand and manage. FC storage would bring in a level of complexity that is unnecessary here. Also, legacy architectures that have grafted an IP (iSCSI) interface would not cut it here, because they would not meet the other requirements above. Storage players that I believe merit consideration include Pivot3, Intransa, LeftHand Networks and to a lesser degree, EqualLogic (their price point may be too high for this application). There are other inexpensive storage offerings, such as from Nexsan or Xyratex but if an architecture does not allow clustering and presentation of a single system image, as it scales, it misses a criterion that I consider absolutely necessary for this application. However, you may want them in the initial mix as you start the evaluation process. I am sure you have enough on your plate without adding yet another storage-hungry application. But the way the winds are blowing, you either pro-actively plan on this or you will get pulled in pushing and screaming.

I’ve been agonizing for a week on what to say for my first Blog. I think it has to be earth-shatteringly profound, so of all the catchphrases and tag lines I came up with, this seemed to sum it all up best:

Hello and thanks for reading my Blog.

What do you think? Just imagine a guy smiling ear to ear and waving at you from behind his keyboard .

An admission: I’m absolutely fascinated by storage. The technology that goes into connecting computers and people to storage today was the stuff of science fiction 20 years ago. Pause for a second and take a look at where we are in storage: 1 TB hard drives, 55GB optical discs, 10Gb Ethernet, 4Gbps Fibre Channel, 3 millisecond seek times, 300MBps throughput… all these numbers add up to wow, at least to me. When I think about all the technology out there, I feel like that kid at the toy store window with my eyes the size of saucers, staring at the GI Joe with the Kung-Fu grip, and the Spiderman Hotwheels set.

Here in my little corner of cyberspace I’ll be blogging about some of those stare-inducing storage technologies from my perspective, which is that of a network administrator (and according to friends is sometimes “warped and twisted” by my own particular brand of logic. I’ll also be touching on the ennui (SAT word I’ve been dying to use in a sentence) that I see creeping into the market. Check back from time to time and let me know if you agree with me. (And dig out that old SAT prep book while you’re at it–send me a word or two I’ll see if I can roll it in.)

One last thing: I gave a presentation on mobile storage at the recent Storage Decisions show in New York, and at the end of the presentation I mentioned a few scripts I wanted to share with the attendees. Below is a copy-and-paste of a simple script using ADfind from Joeware.net to archive users’ home directories that no longer have Active Directory accounts. This script can certainly be more elegant so feel free to expand, expound and extend.  There are a few things on the “to-do” list for it: first, make it self-contained and not need an input file (i.e., do the AD query using ADODB or something similar). Second, provide logic to validate permutations of a username or directory. Third, be a pretty HTA (HTML Application). I’m working on migrating this script to Powershell.

The code is below the jump. Copy it out using notepad (not wordpad) or some script editor and save it as a .vbs. Run it from the command line with an input text file with one username per line. You’ll need to insert specifics for your environment like domain names, etc. 

Again, thanks for the read!

‘==========================================================================
‘
‘ VBScript Source File — Created with SAPIEN Technologies PrimalScript 4.0
‘
‘ NAME: archive.vbs
‘
‘ AUTHOR: Tory Skyers , None
‘ DATE : 06/19/2007
‘
‘ COMMENT: Searches Active directory for usernames and moves the folder if it is not found
‘ You will need to create a text file w/ usernames; and you need adfind.exe somwhere in your path
‘ eg: username1
‘ username2
‘ username3
‘
‘==========================================================================
‘ Parts adapted from Windows 2000 magazine Septemeber 2003 issue crisis mode scripting article

Const ForReading = 1, ForWriting = 2, ForAppending = 8

Dim Args, inputfile
‘Slashes break things in file names so let’s take them out
strdate = replace(date, “/”, “-”)

‘ Ask for a file on the command line , tell the user what to type
If wscript.arguments.count <> 1 Then
wscript.echo “Syntax is: fixmove.vbs ”
wscript.quit
End If

‘ Read the input filename into an Array
Set args = wscript.arguments
strinputfile = args(0)

‘ Create the file system objects to manipulate files and folders
Set objFSO = Createobject(“Scripting.FileSystemObject”)

‘ Read in the text file and create an array with it.
‘ Use a linebreak as the delimiter
Set ObjTextStream = objFSO.OpenTextFile(strInputFile, ForReading)
arrUsers = Split(objTextStream.ReadAll, vbCrlf)
ObjTextStream.Close

‘ Make sure the stdout object is defined and create a shell object
Set StdOut = Wscript.StdOut
Set objShell = CreateObject(“Wscript.Shell”)

‘ Keep going in case of errors
‘On Error Resume Next

‘ Step through the array we created earlier
For Each strUser In arrUsers

‘ Execute the adfind (copyleft joeware.net)
Set objScriptExec = objShell.Exec (“adfind -b dc=fabrikam,dc=com -f ” & chr(34) & “(objectcategory=user)(samaccountname=” & struser & “)” & chr(34))
strResults = Lcase(objScriptExec.StdOut.ReadAll)

‘Define the error and success log
Set objError = Objfso.OpenTextFile(“e:\fileserver\archived\” & strDate & “error.txt”, 8, True)
Set objSuccess = Objfso.OpenTextFile(“e:\fileserver\archived\” & strDate & “sucess.txt”, 8, True)

‘Move the folder from one place to another
If InStr(strResults, “0 objects returned”) Then
objFSO.MoveFolder strUser, “e:\fileserver\archived”

‘ Write to the console and error logs.
WScript.Echo “User ” & struser & “NOT Found! Moving Folder”
objError.WriteLine( “User ” & struser & “NOT Found! Moving folder”)
objError.Close
Else
WScript.Echo “User ” & struser & “Found, not moving folder”
objSuccess.WriteLine (“User ” & struser & “Found, not moving folder”)
objSucess.close
Next