Global Database - Loss of Objects and Policies after Upgrade

[LarW63]

Hi,

We started out with all of our FGs and FM running v5.2.  We have since worked through upgrading all FGs to v5.4.4 and FM to v5.4.3.  Yet our Global Database is still aligned with v5.2.  So, we tried upgrading it to v5.4 and surprisingly all of the Global objects and policies were reset in the process.  

Fortunately, it's a VM and we took a snapshot prior to the upgrade.  So, we rolled back and are running again with Global Database at v5.2 level.

Does anyone have any guidance on upgrading the Global Database, while preserving the existing objects and policies?

Thank you,

LarW63

[chall_FTNT · Accepted solution]

For the necessary steps (upgrade FGTs, then ADOM, then global), see ADOM versions in our online guide.  If your problem with objects being lost in the global DB, I'd encourage you to open a support ticket.

[chall_FTNT]

After upgrading the global ADOM, assignment status for global policy package should change and the action option will shows as Assign.  This means you have to reassign.  But the objects and packages in global ADOM should still be there.  It is just that they may have changed during upgrade.  This is why the global policy package needs reassigned.

[LarW63]

After reviewing the online documentation, I realized that I was incorrectly trying to upgrade the ADOM by editing it and setting the version to 5.4.  The proper way to upgrade an ADOM is to right-click and select 'Upgrade'.  This maintains objects, policies and assignments.

Thank you,

LarW63