Creating a Storage Pool in Windows Server 2012 April 21, 2013Posted by vbry21 in Microsoft Training, Windows 2012.
Tags: Microsoft, Windows 2012
One of the courses I teach is the Microsoft Windows 2012 Installing and Configuring course, the Microsoft designation is the 20410B
In the presentation, we look at creating Storage Pools in Windows Server 2012.
A storage pool is a collection of one or more physical disks that you can use to create virtual disks. You can add to a storage pool any available physical disk that is not formatted or attached to another storage pool.
Virtual Disk Configuration Options
You can create virtual disks from storage pools. If your storage pool contains more than one disk, you can also create redundant virtual disks. To configure virtual disks or Storage Spaces in Server Manager or Windows PowerShell, you need to consider the following features and their redundancy functionalities.
This feature defines the number of disks from the storage pool that are allocated. Valid options include:
Simple. A simple space has data striping but no redundancy. In data striping, logically sequential data is segmented across all disks in a way that access to these sequential segments can be made to different physical storage drives. Striping makes it possible to access multiple segments of data concurrently. Do not host important data on a simple volume, because it provides no failover capabilities when the disk that is storing the data fails.
Two-way and three-way mirrors. Mirror spaces maintain two or three copies of the data that they host (two data copies for two-way mirrors and three data copies for three-way mirrors). Duplication happens with every write to ensure that all data copies are always current. Mirror spaces also stripe the data across multiple physical drives. Mirror spaces provide the benefit of greater data throughput and lower access latency. They also do not introduce a risk of corrupting at-rest data, and do not require the extra journaling stage when writing data.
Parity. A parity space is similar to RAID 5. Data, along with parity information, is striped across multiple physical drives. Parity enables Storage Spaces to continue to service read and write requests even when a drive has failed. Parity is always rotated across available disks to enable I/O optimization. Storage spaces require a minimum of three physical drives for parity spaces. Parity spaces have increased resiliency through journaling.
The demonstration is available at the BryanQA Youtube site