<?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: AltaVault Virtual Appliance; Expand Harddisk in NetApp Console</title>
    <link>https://community.netapp.com/t5/NetApp-Console/AltaVault-Virtual-Appliance-Expand-Harddisk/m-p/139637#M84</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;You can update the size of the cache that AVA-v uses. First, shut down the AltaVault appliance using the Maintenance &amp;gt; Shut down screen. From VMware, then edit the VM and modify the 2nd disk to the new size 200GB in this case). Note: the disk is the one you added during the deployment of AVA-v from the template, and is not the first disk (the AVA operating system disk). Once done expanding the disk, you can boot AVA-v, and it should detect the new size properly.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The cloud consistency error seems to be something else entirely and not related to the disk - perhaps something tied to you not cleanly shutting down the AVA-v VM while operations were ongoing with the cloud. Assuming this is a test environment, I'd suggest starting over from a data standpoint. From AVA-v command line after the VM boots (connect to the command line via an SSH session), you can issue the following:&lt;/P&gt;
&lt;P&gt;enable&lt;/P&gt;
&lt;P&gt;configure terminal&lt;/P&gt;
&lt;P&gt;no service enable&lt;/P&gt;
&lt;P&gt;datastore format all (note: this wipes the cloud and cache of data, and assumes the cache expansion issue is resolved per above)&lt;/P&gt;
&lt;P&gt;stats clear-all&lt;/P&gt;
&lt;P&gt;logging files rotation force&lt;/P&gt;
&lt;P&gt;service enable&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Christopher&lt;/P&gt;</description>
    <pubDate>Mon, 16 Apr 2018 21:07:52 GMT</pubDate>
    <dc:creator>chriswong</dc:creator>
    <dc:date>2018-04-16T21:07:52Z</dc:date>
    <item>
      <title>AltaVault Virtual Appliance; Expand Harddisk</title>
      <link>https://community.netapp.com/t5/NetApp-Console/AltaVault-Virtual-Appliance-Expand-Harddisk/m-p/139604#M83</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am doing a test. It involves Veeam backup to AltaVault(VMware) to Azure.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;On the second harddisk for AltaVault, i set it as 100GB, but now due to lack of space, i wanted to expand it again by 100GB.&lt;BR /&gt;But after expanding by 100GB and rebooting Altavault, i am unable to start the service.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cloud consistency issue.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;May i know if there is a proper way to expand the hard disk in altavault?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 13:49:06 GMT</pubDate>
      <guid>https://community.netapp.com/t5/NetApp-Console/AltaVault-Virtual-Appliance-Expand-Harddisk/m-p/139604#M83</guid>
      <dc:creator>josephtan88</dc:creator>
      <dc:date>2025-06-04T13:49:06Z</dc:date>
    </item>
    <item>
      <title>Re: AltaVault Virtual Appliance; Expand Harddisk</title>
      <link>https://community.netapp.com/t5/NetApp-Console/AltaVault-Virtual-Appliance-Expand-Harddisk/m-p/139637#M84</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;You can update the size of the cache that AVA-v uses. First, shut down the AltaVault appliance using the Maintenance &amp;gt; Shut down screen. From VMware, then edit the VM and modify the 2nd disk to the new size 200GB in this case). Note: the disk is the one you added during the deployment of AVA-v from the template, and is not the first disk (the AVA operating system disk). Once done expanding the disk, you can boot AVA-v, and it should detect the new size properly.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The cloud consistency error seems to be something else entirely and not related to the disk - perhaps something tied to you not cleanly shutting down the AVA-v VM while operations were ongoing with the cloud. Assuming this is a test environment, I'd suggest starting over from a data standpoint. From AVA-v command line after the VM boots (connect to the command line via an SSH session), you can issue the following:&lt;/P&gt;
&lt;P&gt;enable&lt;/P&gt;
&lt;P&gt;configure terminal&lt;/P&gt;
&lt;P&gt;no service enable&lt;/P&gt;
&lt;P&gt;datastore format all (note: this wipes the cloud and cache of data, and assumes the cache expansion issue is resolved per above)&lt;/P&gt;
&lt;P&gt;stats clear-all&lt;/P&gt;
&lt;P&gt;logging files rotation force&lt;/P&gt;
&lt;P&gt;service enable&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Christopher&lt;/P&gt;</description>
      <pubDate>Mon, 16 Apr 2018 21:07:52 GMT</pubDate>
      <guid>https://community.netapp.com/t5/NetApp-Console/AltaVault-Virtual-Appliance-Expand-Harddisk/m-p/139637#M84</guid>
      <dc:creator>chriswong</dc:creator>
      <dc:date>2018-04-16T21:07:52Z</dc:date>
    </item>
  </channel>
</rss>

