Talk:Storage virtualization

message: * Suggested structure.... deleted as its now in place in the article ... Notice the complete lack of vendor and product references.  Some of the storage virtualization technologies are still emerging and others are waning, so it would be hard to give a fair treatment to all.  If anyone wants to take that on, be my guest! Plowden 20:57, 19 August 2006 (UTC)
replies: text: I'll happily start drafting some content as outlined above, may need some grammatical checking, but content wise not a problem (been working in Storage Virt for 5+ years)  Agree that leaving vendor specifics and product references out is a good idea - also an unbiased view of implementation approach is needed, as each vendor tends to try and sell theirs as the 'correct' approach. Baz whyte 11:38, 25 February 2007 (UTC)

text: Sure, go ahead. It looks quite good. I may also chip in sometimes. :) --soumসৌমোyasch 02:42, 26 February 2007 (UTC)
thread_title:  Article Improvements 

message: :Host based - need some more detail and contents on the various styles of host based storage virtualization
:: Almost all commercial OSs ship with a stipped down version Veritas (symantec) Volume Manager whic enables very basic storage virtualization at the host level with capabilities like, but not limited to, RAID and volume management.</p>
:Block vs NAS - needs completing
::NAS
:: NAS or Network Attached Storage is a dedicated file serving computer whose primary finction is to store and retrieve files in rsponse to clients which connect through, normally and most often, an ethernet LAN.
:: Since the NAS box serves files, most NAS boxes run a file system locally, like WAFL in NetApp Appliances
::Mostly implemented in environments where file sharing is a dominant feature and file storage consolidation becomes priority.
::NAS is most preferred when Applications are concerned prmarily with file-level operations and have inherent tolerance towards delays in file operations
::Relatively cheaper than a Fiber-Channel SAN solution because it leverages existing Ethernet LAN infrastructure for transport
::SAN
Will add soon :)
John.joji (talk) 16:05, 31 August 2008 (UTC)
thread_title:  Needing work 

message: Vasko, added a couple of comments to clarify above, but otherwise feel free to make ammendments.
I am concerned that this page is reverting back to its old state which used to just list all of the vendors doing SV products. The point of the re-write was to remove ANY vendor specific references and provide an independent view of what storage virtualization is, and what approaches can be taken to implement virtualization NOT a list of products that can do it - I propose we remove the Spam that is the lists of products - otherwise it ends up with vendor X coming along an saying - we do that and adding a reference to their product. If nobody objects I will remove in a week or so. Baz whyte (talk) 21:04, 25 February 2009 (UTC)
thread_title:  Thoughts ? 

message: This article seems a bit confused. It never gives a good overview or introduction to the topic. There's a lot of material here, but its organization seems to be unclear. Peter Flass (talk) 15:59, 11 May 2021 (UTC)
thread_title:  Seems very muddled 

message: This page talks about virtualizing subsystems and networked devices. Is there a place to talk about virtualizing a single device? CMS Minidisks were an early example of making a single physical disk look like multiple smaller devices. I would think that PC-DOS partitition tables {Disk partitioning) are later examples of the same. Then there are RAM drives, which also implement a virtual disk. Peter Flass (talk) 15:57, 11 May 2021 (UTC)
thread_title:  Other concepts