On Windows Server 2012, you can create storage pools, virtual disks, and finally volumes.
Looking more closely, you will find that it's a software RAID system that allows you to :
Warning : as mentioned before, this will be a software RAID and not a hardware RAID (as it's possible to do with an Adaptec RAID controller, for example).
In this tutorial, we will explain how to create the main RAID levels :
To get started, in the Server Manager, click "File and Storage Services".
Then, click on "Storage Pools".
As mentioned earlier, you will be able to create :
For now, we see a storage pool named "Primordial" which is of type "Available Disks".
In other words, it doesn't exist. It's simply Windows Server that tells you that you have 2 physical hard drives that are not yet used by your server.
To begin, we will create a RAID 0 that increases performance for data storage, but it's strongly discouraged for the security of your data.
Indeed, when you store data on a RAID 0, the system will store :
If you lose a hard drive, you will lose ALL data. Which is logical since you will only have half of each file left.
To start, you must create a storage pool in which you add 2 disks.
The new storage pool wizard is displayed.
Specify a name for the storage pool.
When you add a physical disk to a storage pool, you can choose the type of assignment :
In our case, we will use the default option : Automatic.
Confirm the creation of this pool.
Once the pool has been created, chek the "Create a virtual disk when the wizard closes" box.
Now, we will create a virtual disk.
Select your storage pool and click Next.
Provide a name for your virtual disk.
In our case, we specify "RAID 0" to make it clearer in the tutorial.
To create a "RAID 0" virtual disk, simply choose the "Simple" storage layout.
As indicated in its description, this type of layout divides the data to store the different parts on the different physical hard disks used.
Which corresponds to the RAID 0 level.
For the provisioning type, you will have the choice between :
For now, we will create a virtual disk that will be the same size as our storage pool.
For this, we choose : Maximum size.
Confirm the creation of your virtual disk.
After the virtual disk is created, check the "Create a volume when the wizard closes" box and click Close.
Finally, we will create a new volume on our virtual disk.
In other words, we will create our first partition on this virtual disk.
Select your virtual disk and click Next.
For RAID 0, we will simulate a virtual machine storage and ISO files to install various operating systems (such as Windows 7, Debian, ...).
In short, as you will understand, we will need a lot of space for virtual machines and little for ISO files.
For our virtual machines, we will use 800 GB of the 998 GB available on this virtual disk.
By default, a letter will be assigned to this volume (partition).
As expected, we have the opportunity to choose :
Confirm the creation of this first volume.
When the volume is created, click Close.
In storage pools, if you select your storage pool, you will only see the virtual disks and physical disks that it's composed of.
But, you will not find the option to add a new volume.
To add a new volume to your virtual disk, you will need to click on "Disks" on the left side and select your virtual disk from the list.
Then, in the "Volumes" block, click : Tasks -> New Volume.
Note : the first disk (numbered 0) on the image below corresponding to the physical disk where Windows Server 2012 is installed.
Leave the default value to use the remaining space.
Windows Server will also assign him a letter.
As before, we can choose the file system, as well as the name to use.
In this case, it will be : ISOs and data.
Click Create to create this second volume.
Once the volume created, click Close.
Now, our "RAID 0" virtual disk has 2 volumes (partitions).
As expected, the created volumes (partitions) appear on Windows.
And we can of course store there data.
Finally, since RAID 0 doesn't provide any fault tolerance, if a hard drive fails (or is unplugged), the virtual disk will become inaccessible.
As well as the associated data.
In addition, it isn't possible to recreate the data that was present on the defective hard drive.
Windows Server 5/7/2017
Windows Server 11/16/2018
Windows Server 2/8/2019
Windows Server 4/19/2019
® InformatiWeb-Pro.net - InformatiWeb.net 2008-2020 - © Lionel Eppe - All rights reserved.
Total or partial reproduction of this site is prohibited and constitutes an infringement punishable by articles L.335-2 and following of the intellectual property Code.