We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Load Balancer ADC

Disk Expansion of the Barracuda Load Balancer ADC on Amazon Web Services (AWS)

  • Last updated on

The Barracuda virtual machines (VMs) purchased through the Amazon Marketplace prior to April 28, 2015 do not support disk expansion. If you want to expand the disk for the virtual machines that were deployed prior to this date, you must re-deploy the VMs using the latest Barracuda Load Balancer ADC AMI available in the Amazon Marketplace.

Step 1: Note the Barracuda Load Balancer ADC Information

  1. Log into the AWS EC2 Management Console.
  2. From the EC2 dashboard, scroll to INSTANCES and select Instance. 
  3. In the Instances table, select the Barracuda Load Balancer ADC requiring an increased disk size and note the following:
    1. Instance ID
    2. Availability Zone
    3. EBS ID by clicking on the Root device value.

Step 2: Shutdown the Barracuda Load Balancer ADC Instance

  1. If the Barracuda Load Balancer ADC is still running, go to the web user interface.
  2. Navigate to the BASIC > Administration page, go to the System Reload/Shutdown section, and click Shutdown. 

Step 3: Note the Disk Size and Create a Snapshot of the Volume

  1. From the EC2 dashboard, scroll to ELASTIC BLOCK STORE and select Volumes.
  2. In the search filter, enter the EBS ID noted in step 3.c under Step 1: Note the Barracuda Load Balancer ADC Information.
  3. Note the current disk size listed next to Size.
  4. Right click on the volume, and select Create Snapshot.
  5. In the Create Snapshot window, enter a name and description, and click Create.

             Snapshot.png
  6. Note the snapshot ID.  

                Snapshot_Created.png

Step 4: Create a New Volume for the Snapshot

  1. From the EC2 dashboard, select Snapshots under ELASTIC BLOCK STORE.
  2. In the search filter, enter the snapshot ID noted in step 5 under Step.2: Create a Snapshot of the Volume.
  3. Right click on the snapshot when Status displays completed, and click Create Volume.
  4. In the Create Volume window, do the following:
    1. Select the desired volume type.
    2. Enter a new volume size.
    3. Ensure the Availability Zone matches the instance Availability Zone noted in step 3.b under Step 1: Note the disk size of the Barracuda Load Balancer ADC and stop the instance.
    4. Click Create.

        Create_Volume.png
    5. Note the volume ID. 

                Volume_Created.png

Step 5: Detach the Old Volume from the Instance

  1. From the EC2 dashboard, select Volumes under ELASTIC BLOCK STORE.
  2. In the search filter, enter the EBS ID noted in step 3.c under Step 1: Note the disk size of the Barracuda Load Balancer ADC and stop the instance.
  3. Right click on the volume, and select Detach Volume.

           Detach_Volume.png
  4. In the Detach Volume window, click Yes, Detach to confirm.

Step 6: Attach the New Volume to the Instance

  1. From the EC2 dashboard, select Volumes under ELASTIC BLOCK STORE.
  2. In the search filter, enter the volume ID noted in step d under Step.3: Create a New Volume for the Snapshot.
  3. Right click on the volume, and select Attach Volume. 
  4. In the Attach Volume window, complete the following:
    1. Enter the name or instance ID in the Instance field, and select the instance noted in step 3.a under Step 1: Note the disk size of the Barracuda Load Balancer ADC and stop the instance.
    2. Ensure the device name is /dev/xvda.
    3. Click Attach.
      attach_volume.png

Step 7: Restart the Instance to Apply the New Volume

  1. From the EC2 dashboard, select Instance under INSTANCES.
  2. In the Instances table, select the Barracuda Load Balancer ADC instance to which the new volume was attached in step 4 under Step.5: Attach the New Volume to the Instance .
  3. Right click on the instance, select Instance State and then select Start.
  4. In the Start Instances window, choose Yes, Start. If the instance fails to start and this is a root volume, verify that you attached the expanded volume using the same device name as the original volume, for example /dev/xvda.
Last updated on