You can easily reach influential IT professionals including decision makers. Talk to us about your products and services and we will do our best to make sure our viewers and readers find you.
Get email updates every time we post!
http://www.snia.org/education/tutorials/2006/fall/virtualization/Storage_Virtualization-I.pdf
At the moment, your storage, your server, the fibre cards, the patching is all different. Your application sits on a server with a specific operating system, which then has storage presented to it with fibre cards. The operating system then works with the network attached storage to have a data drive. When this drive needs to be upgraded, it can take days to do so:
* You might need a new volume on another rig - the rig might be full – more patching required
* Your operating system might not support a bigger drive
* Your storage team might require that you use emulex and not q-logic cards for san connectivity
* You might need to get another disk presented then copy the data
* You might not have the space right now, so you need to purchase a new emc rig
With virtual storage, there is a layer between your server and the storage. You server access filespace 7 and writes there, filespace 7 could be comprised of two different emc disks/volumes in different sites, it’s not your concern. You write to filespace 7, the virtual storage does the rest. Very cool, obviously needs to evolve into a supportable industrial solution.
Related posts:
Related posts brought to you by Yet Another Related Posts Plugin.