<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Volume and Datastore configuration for SQL Server VM's using VMDK's in Data Protection</title>
    <link>https://community.netapp.com/t5/Data-Protection/Volume-and-Datastore-configuration-for-SQL-Server-VM-s-using-VMDK-s/m-p/72900#M6975</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mark ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How many SQL Server instances are you planning to run per VM? The restriction with 64 datastores is gone with ESX 5.0 .So there is a more&amp;nbsp; headroom for drawing the layout architecture.This is not a hard and fast rule to have a datastore dedicated to a single SQL VM .&lt;/P&gt;&lt;P&gt;You can still have multiple datastores for a single VM if there are high number of SQL instances running per VM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Abhishek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 30 Apr 2012 11:08:09 GMT</pubDate>
    <dc:creator>abhisek</dc:creator>
    <dc:date>2012-04-30T11:08:09Z</dc:date>
    <item>
      <title>Volume and Datastore configuration for SQL Server VM's using VMDK's</title>
      <link>https://community.netapp.com/t5/Data-Protection/Volume-and-Datastore-configuration-for-SQL-Server-VM-s-using-VMDK-s/m-p/72895#M6974</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've read the most recent &lt;EM&gt;Microsoft SQL Server and SnapManager for SQL on NetApp Storage Best Practices Guide&lt;/EM&gt; (TR-4003), but am still unclear of the the Netapp Volume and VM Datastore configuration for SQL Server VM's using VMDK's. The question is:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Should we create a separate Netapp Volume for each SQL Server VM (apx. 20 VM’s), then place all the Database VMDK’s for each SQL Server into these dedicated Volumes/Datastores? &lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There seem to be some conflicting limitations on the VM and Netapp side that have made this a more difficult decision:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Since we use NFS on our VM hosts, each Netapp Volume will correspond to a single datastore. A VM host (or cluster) is limited to a maximum of 64 datastores, so 20 volumes/datastores would consume a large portion of the maximum limit.&lt;/LI&gt;&lt;LI&gt;If we mix the VMDK's for several SQL Servers into a single Datastore, then we will need to offset the snapshot schedules for those SQL Servers, so they do not conflict with each other.&lt;/LI&gt;&lt;LI&gt;Since there is a maximum of 255 snapshots per Volume, having multiple SQL Servers in a single Volume/Datastore would mean we would need to schedule fewer snapshots per SQL Server or a have a shorter snapshot retention period.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:28:31 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/Volume-and-Datastore-configuration-for-SQL-Server-VM-s-using-VMDK-s/m-p/72895#M6974</guid>
      <dc:creator>markwidrig</dc:creator>
      <dc:date>2025-06-05T06:28:31Z</dc:date>
    </item>
    <item>
      <title>Re: Volume and Datastore configuration for SQL Server VM's using VMDK's</title>
      <link>https://community.netapp.com/t5/Data-Protection/Volume-and-Datastore-configuration-for-SQL-Server-VM-s-using-VMDK-s/m-p/72900#M6975</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mark ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How many SQL Server instances are you planning to run per VM? The restriction with 64 datastores is gone with ESX 5.0 .So there is a more&amp;nbsp; headroom for drawing the layout architecture.This is not a hard and fast rule to have a datastore dedicated to a single SQL VM .&lt;/P&gt;&lt;P&gt;You can still have multiple datastores for a single VM if there are high number of SQL instances running per VM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Abhishek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Apr 2012 11:08:09 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/Volume-and-Datastore-configuration-for-SQL-Server-VM-s-using-VMDK-s/m-p/72900#M6975</guid>
      <dc:creator>abhisek</dc:creator>
      <dc:date>2012-04-30T11:08:09Z</dc:date>
    </item>
    <item>
      <title>Re: Volume and Datastore configuration for SQL Server VM's using VMDK's</title>
      <link>https://community.netapp.com/t5/Data-Protection/Volume-and-Datastore-configuration-for-SQL-Server-VM-s-using-VMDK-s/m-p/72904#M6976</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Abhisek,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the quick response. We only run one SQL Server instance per VM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are also in the process of upgrading our VMWare environment from v4.1 to v5.0. So, that will help with the datastore limitation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Apr 2012 16:16:25 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/Volume-and-Datastore-configuration-for-SQL-Server-VM-s-using-VMDK-s/m-p/72904#M6976</guid>
      <dc:creator>markwidrig</dc:creator>
      <dc:date>2012-04-30T16:16:25Z</dc:date>
    </item>
  </channel>
</rss>

