<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Cloud Datacenter Storage Approaches in the Windows Server 2012 era</title><link>http://blogs.technet.com/b/privatecloud/archive/2012/04/17/cloud-datacenter-storage-approaches-in-the-windows-server-8-era.aspx</link><description>In our previous blog post, we talked about the network architecture of a Windows Server 2012 datacenter and how it opens up the door for new ways of thinking about networking. In this post, we’ll discuss the different conceptual approaches for storage</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Cloud Datacenter Storage Approaches in the Windows Server 2012 era</title><link>http://blogs.technet.com/b/privatecloud/archive/2012/04/17/cloud-datacenter-storage-approaches-in-the-windows-server-8-era.aspx#3494978</link><pubDate>Fri, 27 Apr 2012 16:36:52 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3494978</guid><dc:creator>Yigal Edery [MSFT]</dc:creator><description>&lt;p&gt;@Martin - you probably wouldn&amp;#39;t do it in most cases, but I thought it&amp;#39;s worthwhile mentioning it&amp;#39;s doable. &lt;/p&gt;
&lt;p&gt;Think of this as a migration path - if you&amp;#39;re moving to rely on file servers (with low cost storage such as SAS JBODs and Spaces), and you&amp;#39;re moving to manage file shares instead of LUNs, but you still have SANs in your datacenter that you want to keep using, it might be easier to you to manage everything the same way. &lt;/p&gt;
&lt;p&gt;Also, in terms of fabric, in the case of Fibrechanell SANs, you will now need to lay out the FC fabric only to the File Servers instead of to all your Hyper-V hosts.&lt;/p&gt;
&lt;p&gt;If your long term strategy is to have both SANs and File Servers side by side (each for what they&amp;#39;re best at), then I agree you will not want to front-end your SANs with a file servers layer.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3494978" width="1" height="1"&gt;</description></item><item><title>re: Cloud Datacenter Storage Approaches in the Windows Server 2012 era</title><link>http://blogs.technet.com/b/privatecloud/archive/2012/04/17/cloud-datacenter-storage-approaches-in-the-windows-server-8-era.aspx#3494710</link><pubDate>Thu, 26 Apr 2012 13:22:29 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3494710</guid><dc:creator>Martin Edelius</dc:creator><description>&lt;p&gt;One thing I&amp;#39;m wondering is why I should connect my Hyper-V hosts, over Ethernet (SMB), to a file server that in turn connects to a SAN, over Ethernet (iSCSI), and not just connect my Hyper-V hosts directly to the SAN, over Ethernet (iSCSI).&lt;/p&gt;
&lt;p&gt;Why would I add the file server &amp;quot;layer&amp;quot;?&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3494710" width="1" height="1"&gt;</description></item></channel></rss>