<?xml-stylesheet type="text/xsl" href="http://edutogether.com/virtualit/rss/rssstyles.xsl"?>
<rss version='2.0'   xmlns:dc='http://purl.org/dc/elements/1.1/'>
    <channel xml:base='http://edutogether.com/virtualit/'>
        <title><![CDATA[IT Virtualization : Activity]]></title>
        <description><![CDATA[Activity for IT Virtualization, hosted on Edutogether : Education Network for Teachers, Students and Online Learners.]]></description>
        <generator>Elgg</generator>
        <link>http://edutogether.com/virtualit/</link>        
        <item>
            <title><![CDATA[RAID]]></title>
            <link>http://edutogether.com/virtualit/weblog/204.html</link>
            <guid isPermaLink="true">http://edutogether.com/virtualit/weblog/204.html</guid>
            <pubDate>Sat, 21 Jun 2008 04:47:35 GMT</pubDate>
		<dc:subject><![CDATA[Disk stripping]]></dc:subject>
		<dc:subject><![CDATA[Redundant disks]]></dc:subject>
		<dc:subject><![CDATA[mirroring]]></dc:subject>
		<dc:subject><![CDATA[storage]]></dc:subject>
		<dc:subject><![CDATA[stripping with parity]]></dc:subject>
		<dc:subject><![CDATA[RAID]]></dc:subject>
		<dc:subject><![CDATA[RAID levels]]></dc:subject>
            <description><![CDATA[<p>RAID stands of Redundant Array of Independent Disks. It is used to describe a storage systems' resilience to disk </p><p>failure through the use of multiple disks and by the use of data distribution and correction techniques.</p><p>RAID can be software, hardware or combination of both.</p><p>SOFTWARE RAID uses more system resources as more disk ports and channels are required. It may have lower</p><p>cost than hardware RAID because it has no dedicated RAID controller but has lower performance.</p><p>HARDWARE RAID offloads parity generation and checking. It also allows for greater disk capacity per disk port.</p><p>It requires expensive RAID controller.</p><p>RAID has got many levels.</p><p>Level 0: Also known as disk stripping, because it uses a disk file system called a strip set. This level does not</p><p> provide fault tolerance. Data is divided into blocks and is spread in a fixed order amond all the disks in the array.</p><p>This level improves read and write performance by spreading operations across multiple disks, so that operations</p><p>can be performed independently.</p><p>&nbsp;</p><p>Level1: This level is also known as disk mirrroring because it uses a disk file system called a mirror set. This level</p><p>provides fault tolerance.</p><p>It provides a&nbsp; redundant, identical copy of a selected disk. All data written to the primary disk is written to the</p><p>mirror disk. It also generally improves read performance but may degrade write performance.</p><p>&nbsp;</p><p>Level 2: RAID level 2 uses error correction algorithm that employs disk stripping strategy that breaks a file into</p><p>bytes and spreads it across multiple disks. The error correction method requires several disks. RAID level 2 is</p><p>more advanced than level 0, because it provides fault tolerance, but is not as efficient as other RAID levels and</p><p>is hence not generally used.</p><p>&nbsp;</p><p>Level 3: It is similar to level 2, because it uses the same stripping method as level 2, but it requires only one disk</p><p>for parity data. This level suffers from a write bottleneck, because all parity data is written to a single drive, but</p><p>provides some read and write performance improvement.</p><p>&nbsp;</p><p>Level 4: It is similar to level 3, because the stripping method stands the same and requires only one disk for</p><p>parity data, but it employs striped data in much larger blocks or segments. This level is not as efficient as level 5</p><p>because(as in level 3) all parity data is written to a single drive, so it also suffers from a write bottleneck.</p><p>&nbsp;</p><p>Level 5: Known as Stripping with parity. It is most popular and is similar to level 4 in that it stripes the data in</p><p>large blocks across all the disks in the array. It differs in that it writes tha parity across all the disks. The data&nbsp;</p><p>redundancy is provided by the parity information. Data and parity information are arranged on the disk array so</p><p>that the two are always on different disks. It also has better performance than level 1 and provides fault tolerance.</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p>]]></description>
        </item>
                
        <item>
            <title><![CDATA[Storage Virtualization]]></title>
            <link>http://edutogether.com/virtualit/weblog/196.html</link>
            <guid isPermaLink="true">http://edutogether.com/virtualit/weblog/196.html</guid>
            <pubDate>Thu, 05 Jun 2008 04:27:20 GMT</pubDate>
		<dc:subject><![CDATA[storage]]></dc:subject>
		<dc:subject><![CDATA[networks]]></dc:subject>
		<dc:subject><![CDATA[Virtualization]]></dc:subject>
            <description><![CDATA[<div id="mv_content_actual"><div class="mv_illustration mv_floatright">Generally speaking, storage virtualization refers to providing a logical, abstracted view of physical storage devices. It provides a way for many users or applications to access storage without being concerned with where or how that storage is physically located or managed. It enables the physical storage in an environment to be shared across multiple application servers, and physical devices behind the virtualization layer to be viewed and managed as if they were one large storage pool with no physical boundaries. </div><p>Virtualizing storage networks enables two key additional capabilities: </p><ul><li>The ability to mask or hide volumes from servers that are not authorized to access those volumes, providing an additional level of security. </li><li>The ability to change and grow volumes on the fly to meet the needs of individual servers.</li></ul><p>Essentially, anything other than a locally attached disk drive might be viewed in this light. Typically, storage virtualization applies to larger SAN (storage area network) arrays, but it is just as accurately applied to the logical partitioning of a local desktop hard drive, redundant array of independent disks (RAID), volume management, virtual memory, file systems and virtual tape. A very simple example is folder redirection in Windows, which lets the information in a folder be stored on any network-accessible drive. Much more powerful (and more complex) approaches include SANs. Large enterprises have long benefited from SAN technologies, in which storage is uncoupled from servers and attached directly to the network. By sharing storage on the network, SANs enable highly scalable and flexible storage resource allocation, high efficiency backup solutions, and better storage utilization. </p></div>]]></description>
        </item>
        
    </channel>
</rss>