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 Message Archiver

Disk Expansion on Amazon Web Services

  • Last updated on

Virtual machines (VMs) deployed from Amazon Marketplace prior to April 28, 2015 do not support Disk Expansion. If you deployed prior to this date and want to expand the disk, you must re-deploy using the latest VM AMI available in the Amazon Marketplace.

Perform the steps in this article to expand the deployed Barracuda Message Archiver disk on Amazon Web Services.

Step 1: Note the disk size of the Barracuda Message Archiver and stop the instance

  1. Log into the AWS EC2 Management Console.
  2. From the EC2 dashboard, select Instance under INSTANCES.
  3. In the Instances table, select the Barracuda Message Archiver for which you want to increase the disk size and note the following:
    1. Instance ID
    2. Availability Zone
    3. EBS ID by clicking on the Root device value.
      ebs_id.png
  4. If the instance is running, ensure you shut down the instance by following the steps below:
    1. Right click on the instance, select Instance Settings and then select Change Shutdown Behavior.
      change_shutdown.png
    2. In the Change Shutdown Behavior window, select Stop from the Shutdown behavior list and click Apply.
      apply_shutdown.png
  5. If the Shutdown behavior is already set to Stop, then choose Cancel.

Step 2: Create a Snapshot of the Volume

  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 Message Archiver and stop the instance.
  3. Right click on the volume, and select Create Snapshot.
  4. In the Create Snapshot window, enter a name and description, and click Create.
    create_snapshot.png
  5. Note the snapshot ID.
    close_snapshot.png

Step 3: 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 and enter a new volume size.
    2. Ensure the Availability Zone matches the instance Availability Zone noted in step 3.b under Step.1: Note the disk size of the Barracuda Message Archiver and stop the instance.
    3. Click Create.
      create_volume.png
  5. Note the volume ID.
              volume_success.png

Step 4: 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 Message Archiver 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 5: 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 5 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, do 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 Message Archiver and stop the instance.
    2. Ensure the device name is /dev/xvda.
    3. Click Attach.
      attach_volume.png

Step 6: 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 Message Archiver 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.
    start.png
  4. In the Start Instances window, choose Yes, Start. If the instance fails to start, and the volume being expanded is a root volume, verify that you attached the expanded volume using the same device name as the original volume, that is, /dev/xvda.

 

Last updated on