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 CloudGen Firewall

This Firmware Version Is End-Of-Support

Documentation for this product is no longer updated. Please see https://campus.barracuda.com/doc/71862301/ for further information on our EoS policy.

How to Update High Availability Clusters

  • Last updated on

To prevent any operational errors in your high availability (HA) cluster, complete the following procedure to update and synchronize your primary unit (that is used for regular operations) and secondary unit (for failovers):

You cannot synchronize an HA unit that is running version 5.4.x with another HA unit that is running a version below 5.2; the partner unit must run at least version 5.2.

Step 1: Stop the Server on the Secondary Unit

  1. Log into the secondary unit with Barracuda NG Admin.
  2. Block the (standby) server. On the CONTROL > Server page, select the server and click Block Server.

    When you block the server, the Control service shuts it down and sends a signal that starts the server on the HA partner unit. Keep in mind that when you block a server, the Control service is not able to perform automatic failovers.

Update02.png

Step 2: Update the Secondary Unit

Update the secondary unit via SSH or NG Admin. For more information, see Migrating to 6.1.

Do not interrupt the update. The updated system will reboot and display the new version on the console login prompt.

Step 3: Switch All Servers to the Secondary Unit

  1. Log into the secondary unit with Barracuda NG Admin.
  2. Verify that the secondary unit is operating correctly.
  3. On the secondary unit, stop the (standby) server. On the CONTROL > Server page, select the server and click Stop Server.

    When you stop a server after it has been blocked, you are re-enabling the Control service to perform automatic failovers. When the server on an HA unit goes down or is blocked, the Control service automatically starts the server on its partner unit.

  4. Log into the primary unit with Barracuda NG Admin.

  5. Block the primary unit servers. On the CONTROL > Server page, select all servers and click Block Server.
    All the servers are taken over by the secondary unit.

You may leave the primary unit in standby mode until you have verified that the secondary unit is operating correctly. You can verify this by stopping the primary unit servers. If functional errors occur on the secondary unit, you may switch the servers back to the primary unit.

Step 4: Update the Primary Unit

Do not interrupt the update. The updated system will reboot and display the new version on the console login prompt.

Step 5: Switch All Servers Back to the Primary Unit

  1. Log into the primary unit with Barracuda NG Admin.
  2. Verify that the primary unit is operating correctly.
  3. On the primary unit, re-enable all servers. On the CONTROL > Server page, select all servers and click Stop Server.
  4. Log into the secondary unit with Barracuda NG Admin.
  5. On the secondary unit, block all the servers. On the CONTROL > Server page, select the servers and click Block Server.
  6. Verify that the primary unit is operating correctly.
  7. On the secondary unit, set all the servers back to standby. On the CONTROL > Server page, select the servers and click Stop Server. 
Last updated on