Capital budgets are pretty tight this year and IT teams all over the globe are being to do more with the same or less. This is good in many ways and hopefully we will overcome some of the profligacy of the past but the responsibility is in our (the end-users) hands, we can’t simply expect the vendors who have encouraged of profligacy in the past to come riding to our rescue. There is an old adage which depending on which continent you sit on goes either ‘Beware Greeks bearing gifts’ or ‘Beware Indians bearing gifts’ or perhaps in modern parlance ‘There aint no such thing as a free lunch’.
So when a vendor comes knocking on your door saying they save you 30/40/50% of your current opex/capex; you have to look very carefully and closely at what they are offering and before you do, I would suggest that there are a few things that you can do prior to this.
1) Go through your spreadsheets or however you manage your storage and find all that storage which was reserved for projects which never happened!
2) Whilst you’re at that; try and locate that storage which has been freed up from all those servers which have been consolidated and virtualised. Those are the ones that Control Center has been spamming you with alerts about and you studiously ignore as no-one is complaining about the server being down.
3) Tell users that there is no more storage available and that they should start deleting things. It is amazing how much stuff can be removed/archived. I’ve just taken over a new team and they have project documentation going back years. I’ve asked them to move all the stale project documentation into an archive directory which I will then zip. Will I gain huge amounts of storage back? No but I’ll get some back and if everyone did this, we’d get quite a lot back.
4) Look at your RAID levels; do you actually need everything at RAID-1? Even the Evil Machine Company no longer recommends RAID-1 for everything. You can generate huge wins with this. Last year, we allocated a lot more storage than we bought by doing this.
5) And whilst you do the above, perhaps take the chance to right size over-sized file-systems.
Okay, all this stuff takes time and time isn’t always available but before you buy ‘pixie dust’ from vendors; it might be worth having a look at doing some of the above. It’s not a free lunch but it’s a lunch you packed yourself and might be a little cheaper than that free lunch you’ve just been offered.
Just some thoughts anyway….
Another. If you don’t have the agents on hosts to see tablespace utilisation from the storage end, get your DBAs to check for tablespaces that they configured but never ended up using. Often as not, there are whole file systems sitting there doing naff-all, full of dud tablespaces.
Of course, they might just shout, “Yay! More storage”, but you might also get some back.
One of the good sides of the credit-crunch (other than cheaper monthly mortgage payments) is that it’s forcing people / companies to actually think properly rather than just write a cheque. Forcing people to adopt a “what do I need” rather than “what would I like” culture.
It’s very easy to be perceived as good when the cash is rolling around, but any idiot can sign a cheque to a grinning sales droid – the real skill comes in delivering the same (or better) when there is no option to write a cheque. That’s when the real optimisation occurs and the real value of things gets exposed.
Absolutely agree that this has to occur for each application owner down, one way to help them is to make it clear the 3/5yr full-TCO cost consequences of their decisions – so that they can reduce costs in areas to free up funds for those areas where they have no reduction options.
Orphaned storage is a classic, as is over-provisioned storage. Raid levels – we’re mitigating 50% of our normal growth through internal raid level changes. Snapshots instead of clones is another good one, and of course do you really need all those replicas? Oh and don’t rely on the electronic tools do a floor walk – you’d be amazed how many ‘unpowered’ disks you can find in arrays (or unpowered arrays) in a mature estate The FTE & disruption cost of realising all of this in a usable fashion may be prohibitive but you’ll find a bunch that can be used and it will force a focus for the future. Have a peek at your SAN switch utilisations as well – there will plenty of cabled ports not in use (freeing up cables, ports & HBAs) and of those in use how many really honestly do need more than 4 HBA ports in a server?
Oh and ‘pixie dust’ – that’s what we rely on around here for everything! 🙂