<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SOFS - Scale-Out File Server on Cloud.Architect BVBA Website</title>
    <link>https://www.cloud-architect.be/categories/sofs-scale-out-file-server/</link>
    <description>Recent content in SOFS - Scale-Out File Server on Cloud.Architect BVBA Website</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Wed, 12 Jul 2017 00:00:00 +0000</lastBuildDate><atom:link href="https://www.cloud-architect.be/categories/sofs-scale-out-file-server/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Extending a S2D (Storage Spaces Direct) Pool on Azure, and increase your IOPS!</title>
      <link>https://www.cloud-architect.be/2017/07/12/extending-a-s2d-storage-spaces-direct-pool-on-azure-and-increase-your-iops/</link>
      <pubDate>Wed, 12 Jul 2017 00:00:00 +0000</pubDate>
      
      <guid>https://www.cloud-architect.be/2017/07/12/extending-a-s2d-storage-spaces-direct-pool-on-azure-and-increase-your-iops/</guid>
      <description>Introduction As more and more companies move their environment(s) to the Azure Cloud, the need for a high-available fileserver grows with it. At the time of the migration/installation, a 128GB volume might be sufficient, at some point in time, the volume needs to be increased. But this is not the same procedure as you would do on a on-premise datacenter. In this blog, you will see how to increase the available diskspace for a Clustered Volume, optimizing the available IOPS &amp;amp; throughput of the disks.</description>
    </item>
    
  </channel>
</rss>
