<?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 CVO instances and Trident backend in Cloud Volumes ONTAP</title>
    <link>https://community.netapp.com/t5/Cloud-Volumes-ONTAP/CVO-instances-and-Trident-backend/m-p/459443#M503</link>
    <description>&lt;P&gt;Hello Community, I have a question about CVO storage instances and backend upgrade in Trident, recently one of the CVO instances created an aggr and moved a Volume to the new aggr automatically (Capacity Management Mode = Automatic), but a week later, I checked the backend in Trident and saw that the new created aggr was reflected in the Trident backend (lika&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;automatically).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; my undertanding is.. the only way to&amp;nbsp; reflect a new aggr&amp;nbsp; in trident bckend is updating the backend with a json:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;tridentctl update backend &amp;lt;backend_name&amp;gt; -f backend-file.json -n trident&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;or&amp;nbsp; Between Trident and CVO Storages, is there a scheduled task to update the backend?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks in Advance Community&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 13 Mar 2025 19:16:34 GMT</pubDate>
    <dc:creator>wolfkiler</dc:creator>
    <dc:date>2025-03-13T19:16:34Z</dc:date>
    <item>
      <title>CVO instances and Trident backend</title>
      <link>https://community.netapp.com/t5/Cloud-Volumes-ONTAP/CVO-instances-and-Trident-backend/m-p/459443#M503</link>
      <description>&lt;P&gt;Hello Community, I have a question about CVO storage instances and backend upgrade in Trident, recently one of the CVO instances created an aggr and moved a Volume to the new aggr automatically (Capacity Management Mode = Automatic), but a week later, I checked the backend in Trident and saw that the new created aggr was reflected in the Trident backend (lika&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;automatically).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; my undertanding is.. the only way to&amp;nbsp; reflect a new aggr&amp;nbsp; in trident bckend is updating the backend with a json:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;tridentctl update backend &amp;lt;backend_name&amp;gt; -f backend-file.json -n trident&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;or&amp;nbsp; Between Trident and CVO Storages, is there a scheduled task to update the backend?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks in Advance Community&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 13 Mar 2025 19:16:34 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Cloud-Volumes-ONTAP/CVO-instances-and-Trident-backend/m-p/459443#M503</guid>
      <dc:creator>wolfkiler</dc:creator>
      <dc:date>2025-03-13T19:16:34Z</dc:date>
    </item>
  </channel>
</rss>

