Bug ID 1593745: Issues identified during Backup, Restore, and User Operations between two BIG-IP Next Central Managers for Standalone and High Availability Nodes.

Last Modified: Feb 11, 2025

Affected Product(s):
BIG_IP_NEXT(CM) TMOS(all modules)

Known Affected Versions:
20.2.1

Opened: Jun 11, 2024

Severity: 4-Minor

Symptoms

Performing a backup on one BIG-IP Next Central Manager, followed by user operations, and then performing a restore on another BIG-IP Next Central Manager with subsequent user operations may result in the following issues You cannot download the QKView on the restored BIG-IP Next Central Manager if it was created by the previous BIG-IP Next Central Manager before the backup operation. After you restore the backup on the new BIG-IP Next Central Manager setup, any BIG-IP Next instance deleted on the previous BIG-IP Next Central Manager enters an unknown state. Additionally, after you restore the backup on the new BIG-IP Next Central Manager, the deleted app on the previous BIG-IP Next Central Manager cannot process traffic until you redeploy the app. The BIG-IP Next Central Manager does not support uploading and downloading backup files when configured with external storage.

Impact

After restoring the new BIG-IP Next Central Manager, certain operations might not function properly.

Conditions

Perform a backup on one BIG-IP Next Central Manager and restore it on another BIG-IP Next Central Manager.

Workaround

If you delete the app after taking a backup on the BIG-IP Next Central Manager and then restore it on a new BIG-IP NEXT Central Manager, traffic will not pass through. Users must edit and redeploy the app for traffic to function properly.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips