Storage virtualization along with virtual storage and storage hypervisors have a theme of abstracting underlying physical hardware resources like server virtualization. The abstraction can be for consolidation and aggregation, or for enabling agility, flexibility, emulation and other functionality.
Storage virtualization can be implemented in different locations, in many ways with various functionality and focus. For example the abstraction can occur on a server, in an virtual or physical appliance (e.g. tin wrapped software), in a network switch or router, as well as in a storage system. The focus can be for aggregation, or data protection (HA, BC, DR, backup, replication, snapshot) on a homogeneous (all one vendor) or mixed vendor basis (heterogeneous).
Here is a link to a guest post that I recently did over at The Virtualization Practice looking at storage hypervisors, virtual storage and storage virtualization. As is the case with virtual storage, storage virtualization, storage for virtual environments, depending on your views, spheres of influence, preferences among other factors what you call a storage hypervisor will probably vary.
Additional related material:
Are you using or considering implementation of a storage hypervisor?
All Comments, (C) and (TM) belong to their owners/posters, Other content (C) Copyright 2006-2024 Server StorageIO and UnlimitedIO LLC All Rights Reserved
Does software eliminate or move location of vendor lockin?
Updated 1/21/2018
Does software eliminate or move location of vendor lockin?
I’m always interested when I hear or read a software vendor or their value added reseller (VAR) or business partner claim that their solution eliminates vendor lockin.
More often than not, I end up being amazed if not amused over the claims which usually should be rephrased as eliminating hardware vendor lock-in.
What is also amazing or amusing is that while some vendors make claims of eliminating (hardware) vendor lock-in, there is also some misdirection taking place. While some solutions may be architected to cut hardware vendor lock-in, how they are sold or packaged can force certain vendors technology into your solution. For example, the EMC Centera software in theory and architecture is hardware vendor independent, however it is sold as a solution (hardware and software), similar to how Dell sells the DX which uses software from Caringo and you guessed right, Dell hardware among many other similar scenarios from other vendors.
How about virtualization or other abstraction software tools along with cloud, object storage, clustered file systems and related tools.
Keep in mind the gold rule of management software and tools which includes virtualization, cloud stacks, clustered file systems among other similar tools. The golden rule is simply who ever controls the software and management controls the gold (e.g. your budget). In the case of a storage software tools such as virtualization, cloud or object storage, cluster or NAS system among others, while they can be correct depending on how packaged and sold of eliminating hardware vendor lock-in, the lock-in also moves.
The lock-in moves from the hardware to the software which even though a particular solution may be architected to use industry standard components, often to make it easy for acquisition, a vendor packages the solution with hardware. In other words, sure, the vendor unlocked you from one vendors hardware with their software only to lock you into theirs or somebody else’s.
Now granted, it may not be a hard lock (pun intended), rather a soft marketing and deployment packaging decision. However there are some solutions that give themselves or at least via their marketing on hardware independence only to force you into buying their tin wrapped software (e.g. an appliance) with their choice of disk drives, network components and other items.
So when a software or solution vendor claims to cut vendor lock-in, ask them if that is hardware vendor lock-in and if they are moving or shifting the point of vendor lock-in. Keep in mind that vendor lock-in does not have to be a bad thing if it provides you the customer with value. Also keep in mind that only you can prevent vendor lock-in which is like only you can prevent cloud data loss (actually its a shared responsibility ;) ).
Here is my point, so what if a vendor chooses to wrap their software with an appliance to make it easy for you to buy and deploy, however unless they are willing to work with you on what hardware that will be, perhaps they should think about going a bit easier on the vendor lock-in theme.
In the quest to race from hardware vendor lock-in, be aware with ears and eyes wide open to make sure that you are not fleeing from one point of lock-in to another. In other words, make sure that the cure to your vendor lock-in challenge is not going to be more painful than your current ailment.
What is your take on vendor lockin? Cast your vote and see results in the following polls.
All Comments, (C) and (TM) belong to their owners/posters, Other content (C) Copyright 2006-2024 Server StorageIO and UnlimitedIO. All Rights Reserved. StorageIO is a registered Trade Mark (TM) of Server StorageIO.
