In most cases, NG Firewall configurations are at least partly linked to repositories for easier administration purposes. When migrating a Barracuda NG Firewall to a newer release, pay special attention to these repository links to ensure that your future administration structure remains simple.
Similar to when you move or copy managed units (see: How to Move, Copy and Delete Barracuda NG Firewalls), the repository links cannot be maintained if, for example, a version 5.2 cluster is migrated to version 5.4 while the repository is still in use by other 5.2 version units. If you migrate the configuration before migrating the repository, the repository links will be broken and the content of the repository will be copied to the NG Firewall configuration page. Proceed as follows to maintain the linked configurations while keeping the original repository objects.
- Step 1 - Create a version 5.2 repository object with the same configuration settings as the former object.
- Step 2 - Migrate the configuration.
- Step 3 - Delete the configuration files that have been created during migration.
- Step 4 - Create new links from the configuration nodes to the up-to-date repository object.