The issue can happen on the HA primary member, where configuration backups were generated as 0 KB files. The same behavior can be seen from GUI backup, CLI backup, both .conf and .yml formats, and with different administrator accounts. Backup from the HA secondary member was generated correctly.
Verification: Check if the issue is GUI-only or also CLI-related. Try a backup from the GUI: Select the Admin username in the top-right corner -> Configuration -> Backup -> Local PC.
Then test CLI backup to an external TFTP server:
execute backup config tftp test_config.conf
execute backup full-config tftp test_full.conf
execute backup yaml-config tftp test_yaml.yml
Check the generated file size after each test.
Check if the issue affects only one HA member.
Test backup from the current primary unit and from the secondary unit.
If one unit creates a 0 KB file and the other unit creates a valid backup, continue with the HA synchronization test.
Check HA status. Run the following command:
get system ha status diagnose sys ha status
Check for HA Health Status, and the primary and secondary serial numbers.
Configuration Status in-sync or out-of-sync state monitored interfaces status. If the HA cluster is out of sync, this should be fixed as the main problem first.
See the following knowledge base articles to synchronize the HA cluster:
Tip: Most out-of-sync tables have dedicated articles explaining how they should be fixed. Search for the specific table in the Knowledge Base.
Factory reset and config reload should only be considered if:
| 
