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.

How to Make Changes to an Existing Mirrored Cluster

  • Last updated on

This article refers to the Barracuda Message Archiver firmware version 5.0 and higher running on Barracuda Message Archiver model 450 and higher. Mirrored systems must be the same model and run the same firmware version, but need not reside in the same location or network. Each Barracuda Message Archiver must function independently and accept and archive messages before it can be mirrored to another system.

Important

Commonly used configuration settings are synchronized between appliances in a mirrored configuration including saved searches, retention policies, and litigation holds. Before completing your configuration, confirm that the saved searches, retention policies, and litigation holds are configured the same on all systems in the mirrored configuration, and verify each system is running the same firmware version. Upgrade clustered systems in a parallel time frame so that data from the primary system continues to reach the secondary system.

Before you perform maintenance on, or break a mirrored pair, contact Barracuda Networks Technical Support to determine the proper workflow for your environment.

To change the IP address on either appliance in a mirrored pair:

  1. Pause any new mail flow to both appliances in the mirrored configuration, including journaling (SMTP or POP/IMAP) as well as Exchange import, stubbing, and data imports such as FolderSync or PIMSync.
  2. Make the necessary IP address changes on the appliances.
  3. Resume journaling and any other data flows.

Configuration Variables

Many configuration variables automatically synchronize across the cluster. For example, saved searches, retention policies, and litigation holds configured on one appliance are also available on the other appliance in the mirrored pair.

Cluster Variables

The following list describes the cluster variables that are not synchronized across a mirrored pair:

  • GroupWise configuration details
  • Any Exchange Integration details (for example, stubbing, folder sync, etc.)
  • Serial number (this never changes)
  • Administrator password
  • Guest password
  • Whether the latest release notes have been read
  • IP Address, Subnet Mask, and Default Gateway (as configured on the BASIC > IP Configuration page)
  • Primary DNS Server and Secondary DNS Server (as configured on the BASIC > IP Configuration page)
  • Host Name (as configured on the BASIC > IP Configuration page)
  • Time Zone (as configured on the BASIC > Administration page)
  • Web Interface HTTP Port (as configured on the BASIC > Administration page); this must be the same value on all systems in the cluster
  • Any advanced IP configuration (as configured on the ADVANCED > ADVANCED Networking page)
  • All customized branding (models 650 and above, as configured on the on the ADVANCED > Appearance page)
  • Cluster Shared Secret; note that this must be the same on all systems for the cluster to work properly (as configured on the ADVANCED > Clustering page)
  • Cluster Hostname (as configured on the ADVANCED > Clustering page)
    Local Host Map (as configured on the ADVANCED > Clustering  page)
  • Web Interface HTTPS/SSL port (as configured on the on the ADVANCED > Secure Administration page); must be the same value on all systems in the cluster
  • Any other secure administration configuration, including saved certificates (as configured on the ADVANCED > Secure Administration page)
  • All SSL information, including saved certificates (as configured on the on the ADVANCED > Secure Administration page)
Last updated on