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 Backup

Barracuda Backup Replacement and Data Migration

  • Last updated on

This article refers to the Barracuda Backup Legacy Release firmware or newer.

If you have any questions or concerns regarding your Barracuda Backup Replacement, contact Barracuda Networks Technical Support.

Barracuda will migrate configuration data and data residing on the Barracuda Backup appliance and Barracuda Cloud Storage for customers receiving replacements through:

  • Instant Replacement
  • Hardware Refresh
  • Upgrade/Trade-in Program

See also: Barracuda Backup Replacement and Data Migration FAQ

Pre-Migration Steps

Before you can replace a device and migrate the data, you must first install and configure the new Barracuda Backup device with an IP address, ensuring that it is online. Use the Barracuda Quick Start Guide included with your appliance (also available as a PDF download from the Overview page). For step-by-step instructions, see the Getting Started section of this library.

You can take these additional steps to ensure a smooth migration and reduce the initial setup time:

  • Have the replacement device installed and online with a valid IP address (see Barracuda Console)
  • Verify a support tunnel is open on the old/existing device, preferably before linking the new device (see How to Open a Support Tunnel):
    SupportTunnelOpen.png
  • If possible, have both the old/existing device and the replacement/new device on the same networking switch and subnet for the best data transfer/migration performance
  • Have the replacement device linked to your Barracuda Cloud Control account (see How to Link a Barracuda Backup Product as a User or Reseller):
    ActivateBackup.png
  • Ensure that any firewall or web filtering rules configured for the old/existing device are configured for the replacement device (see Barracuda Console)

Replacement and Data Migration Process

Data_Migration_Process.png

The replacement and data migration process consists of the following steps:

  1. An RMA, upgrade, or hardware refresh is processed (see Replacing a Failed Barracuda Backup Appliance).
  2. The subscriptions (Energize Updates, Instant Replacement, Cloud) on the old/existing device are moved to the new/replacement device (see Firmware Upgrade Policy and How to Upgrade Firmware).
  3. A replacement/data migration ticket is created and sent to the Barracuda migrations team.
  4. An email is sent to the customer with a list of available options for the replacement/data migration process, as described in the Data Migration Options section below.
  5. The customer replies to the email in Step 4 with their selected data migration option.
  6. A technical support case/ticket is created to track the replacement/data migration progress.
  7. The case/ticket is sent to the migrations team queue.
  8. The ticket is picked up based on priority by a Barracuda migrations team member and an email is sent to the customer notifying them that the replacement/data migration has begun.
  9. The configuration (metadata) is pulled from the old/existing device or cloud (based on the option selected by the customer) and copied to the new/replacement device.
  10. After the metadata pull is complete, backups are functional and run as normal. The entire backup configuration is now present on the new/replacement device and can be accessed and/or modified as normal.
  11. The backed up data (binary data) is pulled from the old/existing device or cloud (based on the option selected by the customer) and copied to the new/replacement device.
  12. Once the binary pull is complete, an email is sent to the customer notifying them that the replacement/data migration is complete.

Data Migration Options

Select the data migration option that best suits your deployment.

Option 1. Pull Data from the Cloud

If you elect to pull the data from the cloud, Barracuda Networks uses the following procedure to complete your request:

  1. Once the new unit is linked, Barracuda Networks connects to the new device and begins wiping the metadata in the database ensuring the unit is completely clean of any data.
  2. Barracuda Networks then pulls the metadata associated with all binary data (your backed-up data).

    The metadata is a description of the data, whereas the binary data is comprised of your actual files.

  3. As the metadata is downloaded, it is inserted into the database tables on the new device. Depending on the amount of metadata to be pulled, this process may take 24 or more hours to complete.
  4. Once the metadata download is complete, backups are enabled on the new device, and the binary data is then pulled from the cloud. The process of pulling the binary data from the cloud can take 24 hours or more depending on the amount of data to be retrieved.
  5. You will receive a notification at the time backups start and the binary data begins to be pulled.

    At this point you can make any changes to the configuration via the web interface; the device is now at full capability.

  6. Once the initial binary data pull is complete, a final check is run with the cloud to ensure data integrity and to verify that all data is present and accounted for. Once verification is complete, the data migration as a whole is finished.
  7. You will receive a notification indicating the process is complete.

Option 2. Pull Data from an Existing Barracuda Backup Appliance

If you have elected to pull the data from your existing Barracuda Backup appliance, confirm the following:

  • Both appliances are on the same LAN/subnet, and
  • Both appliances are linked to a Barracuda Networks Account 
  1. Once the new device is linked to the existing Barracuda Backup appliance, Barracuda Networks begins prepping the old device for the migration including:
    • Shutting down all dependent functions of the old device
    • Dumping the metadata tables from the databases on the old device in order to pull them across and import them into the new appliance
  2. Once prepping is complete, Barracuda Networks begins the actual data migration by importing the metadata tables from the old device to the new appliance.
  3. Once the metadata import is complete, backups are enabled on the new appliance and backups can run on all data sources. The binary data is migrated across to the new appliance in the background. The process of pulling the binary data from the old device can take 24 hours or more depending on the amount of data being migrated.

    Running a backup on all data sources assists in populating the new device with the synchronized data. By backing up the data sources, those data parts that already exist are skipped over, thus reducing the time it takes to complete the process.

  4. You will receive a notification alerting you that the backup process has begun on the new device and that data is syncing.

  5. Once the initial binary data pull is complete, a final check is run with the cloud to ensure data integrity and to verify that all data is present and accounted for. Once verification is complete, the data migration as a whole is finished.
  6. You will receive a notification indicating the process is complete.
Option 3. Use an Existing Configuration

You can set up and configure a new Barracuda Backup appliance with an existing configuration, data sources, retention policies, and all other aspects of backup.barracuda.com. This is the fastest type of migration because you are not migrating large amounts of data. To use an existing configuration:

  1. Once the new device is linked, Barracuda Networks pulls the configuration from the cloud.
  2. You will receive a notification indicating the process is complete.
Option 4. Set Up a New Appliance from Scratch

You can set up and configure a new Barracuda Backup appliance without utilizing an existing configuration. With this option, you must configure the new device from scratch as it is treated as a brand new unit. For step-by-step instructions on setting up backups, refer to Data Backup Tasks in the Getting Started section.

Last updated on