Differences

This shows you the differences between two versions of the page.

--- sonicwall:hard_disk:how_to_expand_the_hard_drive_of_a_virtual_appliance [2021/02/16 15:04] – created dgonzalez
+++ sonicwall:hard_disk:how_to_expand_the_hard_drive_of_a_virtual_appliance [2021/02/16 15:23] – dgonzalez
@@ Line 1: / Line 1: @@
-asdfgfhg
+===== How To Expand The Hard Drive Of A Virtual Appliance =====
+**DESCRIPTION:**
+This article will explain how to expand the logical volume size of a Virtual appliance to grow beyond the 250 GB and 950 GB OVA templates provided on MySonicWall.com. This process does not overwrite the pre-existing data, it will add on more space to the pre-existing Hard Drive.
+***This process should not be used to expand the volume of Flow Server agents, or GMS 9.0 deployments installed with Flow Based reporting.**
+***This process should not be used on GMS versions 8.1 or older.  Please upgrade to minimum GMS version 8.2 prior to performing these steps.**
+----
+===ADD A NEW VIRTUAL HARD DRIVE===
+. Turn off the Virtual Appliance
+. Log into the VMware Web Client or vSphere Client
+. Select Edit Settings for the Virtual Appliance
+. Click the Add button, and select the Hard Disk as the device type then select Next
+{{:sonicwall:hard_disk:090170726616587.png?nolink&400|}} {{:sonicwall:hard_disk:090170726023029.png?nolink&200|}}
+. Input the size of the disk equal to the amount you would like to expand and select Thick Provision Lazy Zeroed then select next
+{{:sonicwall:hard_disk:090170726295989.png?nolink&400|}}
+. Check the radial for the appropriate drive type (match the drive type, SCSI or IDE,  currently in use on the Virtual Appliance)
+{{:sonicwall:hard_disk:090170726498388.png?nolink&400|}}
+. Select Finish and turn on the Virtual Machine
+{{:sonicwall:hard_disk:090170726372840.png?nolink&400|}}
+===EXPAND THE VIRTUAL HARD DRIVE===
+. Contact Technical Support to get the Root SSH password Best method is to open a Web ticket requesting Root SSH with this KB ID in the Title
+. Check that the disk has been partition by running (should be listed as /dev/sdb1): fdisk -l