IMPORTANT ANNOUNCEMENT FOR OUR READERS!
AskPFEPlat is in the process of a transformation to the new Core Infrastructure and Security TechCommunity, and will be moving by the end of March 2019 to our new home at https://aka.ms/CISTechComm (hosted at https://techcommunity.microsoft.com). Please bear with us while we are still under construction!
We will continue bringing you the same great content, from the same great contributors, on our new platform. Until then, you can access our new content on either https://aka.ms/askpfeplat as you do today, or at our new site https://aka.ms/CISTechComm. Please feel free to update your bookmarks accordingly!
Why are we doing this? Simple really; we are looking to expand our team internally in order to provide you even more great content, as well as take on a more proactive role in the future with our readers (more to come on that later)! Since our team encompasses many more roles than Premier Field Engineers these days, we felt it was also time we reflected that initial expansion.
If you have never visited the TechCommunity site, it can be found at https://techcommunity.microsoft.com. On the TechCommunity site, you will find numerous technical communities across many topics, which include discussion areas, along with blog content.
NOTE: In addition to the AskPFEPlat-to-Core Infrastructure and Security transformation, Premier Field Engineers from all technology areas will be working together to expand the TechCommunity site even further, joining together in the technology agnostic Premier Field Engineering TechCommunity (along with Core Infrastructure and Security), which can be found at https://aka.ms/PFETechComm!
As always, thank you for continuing to read the Core Infrastructure and Security (AskPFEPlat) blog, and we look forward to providing you more great content well into the future!
Thanks for great feedback and for reading my prior AskPFEPlat post regarding Storage Spaces in Windows Server 2012. Based on feedback and questions following that post, it seemed like a great time to show how to import a storage pool on another server. Storage Spaces in Windows Server 2012 writes the configuration about the storage pool onto the disks themselves. Therefore, if disaster strikes and the server hardware requires replacement or a complete re-install – there is a relatively simple procedure involved to mount and access a previously created storage pool…perhaps on another server. Notice I said server. The implementation of Storage Spaces on Windows 8 doesn’t offer the same feature set that Windows Server 2012 does, so therefore you can only import a storage pool on the same OS version for which it was created.
Step By Step Example
1. Make the disks available to the server
The first step, which may have multiple sub-steps, is to physically attach and successfully make available all drives from the pre-existing storage pool. To be successful in this endeavor, you would need appropriate drivers, cables, firmware, etc. to make this work. Obviously if these are SAS drives and the destination server doesn’t have a SAS interface, this will be somewhat of a difficult task without the proper interface. Once you’ve completed this task, from Server Manager you should see something similar to the following (please click on any of the included screen captures for a clearer, more detailed image):
2. Make the storage pool read-write.
As you can see from the prior screenshot, the storage pool (as well as the virtual disk) has a warning exclamation mark symbol to indicate a problem. By default, Windows Server 2012 will detect the foreign volume and mark it read-only. The indicator appears because of this condition. To proceed, right-click the storage pool and choose Set Read-Write Access…
Make it read-write.
Choose the server where the storage pool may be mounted read-write. If this is a clustered storage pool, multiple nodes may appear in the Choose a Server for Read-Write Access dialog.
3. Attach the virtual disk.
The activities in prior steps make the storage pool available. However, within the storage pool will be any virtual disks previously created using pool resources. Just like a VHD, these must be attached in order to be accessible. Therefore, the yellow exclamation warning sign indicates that the virtual disk is not currently attached. To proceed, right-click on each virtual disk and choose Attach Virtual Disk.
If all is successful, each Virtual Disk chosen will be attached.
4. Online the resulting logical disk(s).
As you may recall, Windows Server 2008 Enterprise and Datacenter editions, by default do not automatically mount every disk device seen (providing that the default SAN policy has not been changed.) Windows Server 2012 is no different. To use any of the virtual disks that belong to the imported storage pool, you must online them first.
In Server Manager under Volumes\Disks, select the disk, right-click, and choose online.
Notice at this point that the volume now appears and remains accessible.
Hopefully the above notes and screenshots illustrate how easy it is to import a storage pool when you have a need to do so, or as a proof of concept when learning about Storage Spaces. The example above was created using Hyper-V Virtual Machines, and using iSCSI targets (for example only, not production) made available to a second newly installed VM after the first VM was conveniently destroyed. You could also use individual VHD files as components for the storage pool members.