<?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: SMVI 2.0 Scalability in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/SMVI-2-0-Scalability/m-p/69263#M16190</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't have experience with SMVI&amp;nbsp; 2.0 yet (soon), but on SMVI 1.0 we have 15 (very large 24CPU, 256GB RAM) hosts with 7 NFS datastore and about 425 VMs.&amp;nbsp; I did notice that if I create a single schedule to perform the snapshots, I would get timeouts on disk on VMs and a lot of alerts about high latency.&amp;nbsp; I created separate schedules for each datastore and staggered them by 10 minutes--all the latency issues and timeouts disappeared.&amp;nbsp; This surprised me since I have filer based daily snapshots which all occur at midnight as a backup (in case SMVI is not functioning I still want snapshots).&amp;nbsp; Those never caused timeouts, but I suspect there must be logic to handle that workload serially.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 03 Nov 2009 19:10:18 GMT</pubDate>
    <dc:creator>benjstarratt</dc:creator>
    <dc:date>2009-11-03T19:10:18Z</dc:date>
    <item>
      <title>SMVI 2.0 Scalability</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/SMVI-2-0-Scalability/m-p/69258#M16187</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Community,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anyone know how SMVI 2.0 scales?&amp;nbsp; I mean, how many virtual machines, datastores, clusters, ESX hosts, etc. can SMVI handle without getting timeout errors or just not working?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jeff&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:22:22 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/SMVI-2-0-Scalability/m-p/69258#M16187</guid>
      <dc:creator>berks</dc:creator>
      <dc:date>2025-06-05T07:22:22Z</dc:date>
    </item>
    <item>
      <title>Re: SMVI 2.0 Scalability</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/SMVI-2-0-Scalability/m-p/69263#M16190</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't have experience with SMVI&amp;nbsp; 2.0 yet (soon), but on SMVI 1.0 we have 15 (very large 24CPU, 256GB RAM) hosts with 7 NFS datastore and about 425 VMs.&amp;nbsp; I did notice that if I create a single schedule to perform the snapshots, I would get timeouts on disk on VMs and a lot of alerts about high latency.&amp;nbsp; I created separate schedules for each datastore and staggered them by 10 minutes--all the latency issues and timeouts disappeared.&amp;nbsp; This surprised me since I have filer based daily snapshots which all occur at midnight as a backup (in case SMVI is not functioning I still want snapshots).&amp;nbsp; Those never caused timeouts, but I suspect there must be logic to handle that workload serially.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Nov 2009 19:10:18 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/SMVI-2-0-Scalability/m-p/69263#M16190</guid>
      <dc:creator>benjstarratt</dc:creator>
      <dc:date>2009-11-03T19:10:18Z</dc:date>
    </item>
  </channel>
</rss>

