Last Modified: Feb 11, 2025
Affected Product(s):
BIG_IP_NEXT(CM) TMOS
Known Affected Versions:
20.2.0, 20.2.1
Opened: Apr 05, 2024 Severity: 2-Critical
Instance backup fails on BIG-IP Next Central Manager version 20.2.0 with message: 'Backup file creation failed'
Instance backup file generation fails with message: 'Backup file creation failed"
A BIG-IP Next Central Manager version 20.1.1 and BIG-IP Next version 20.1.0 1. Upgrade the BIG-IP Next instances to version 20.2.0. 2. In the BIG-IP Next Central Manager UI, go to Infrastructure > Instances. 3. Create a backup file for the instance by selecting the desired BIG-IP Next instance, select the Actions menu, select Back Up & Schedule and input the required information. 4. Create a backup file for the instance by selecting the desired BIG-IP Next instance, click Actions and select Back Up & Schedule and input the required information. 5. In the BIG-IP Next Central Manager UI, go to Infrastructure > Instances > Backup & Restore.
Once you have upgraded the BIG-IP Next instances to version 20.2.0, you need to delete large image files as they prevent the successful backup. In addition, you need to delete the failed backup file. You must send API calls to the instance to remove the large upgrade files and failed backup files before the backup will succeed. This example uses Postman to send the API calls. The following is an example procedure with variables {{ }} around them. You can use variables or insert the actual value for each request: 1. Send a login request to BIG-IP Next Central Manager and record the “access_token” from the response. This is used to make all other API calls. a. Use the command POST https://{{remote-CM-address}}/api/login, or if no variables are used, then use the command POST https://10.145.69.227/api/login b. The body for the request is a JSON object with the credentials for the user. { "username": "username", "password": "password" } 2. Send a request to BIG-IP Next Central Manager's inventory and identify the instance that you want to delete the file from. Record the “id” from the response. The access_token from the previous step is used as the Bearer Token for the request. Repeat this for all other requests as well: GET https://{{remote-CM-address}}/api/device/v1/inventory 3. Delete the large image files and failed backup files. Send a request for the files present on the instance. Note the instance ID from the previous step is used in the request URL. In the response, record the "id" for the "file name" or "description" in the response. Example files: - The upgrade image file: BIG-IP Next 20.2.0....tgz - The original backup file: backup and restore of the system GET https://{{remote-CM-address}}/api/device/v1/proxy/{{remote-Big-IP-Next-ID}}?path=/files 4. Send a request to delete the file on the instance. The file ID from the previous step and paste it to the end of delete URL. For example: DELETE https://{{remote-CM-address}}/api/device/v1/proxy/{{remote-Big-IP-Next-ID}}?path=/files/644fcd02-fa38-4383-ac1c-f67e0c899e0d 5.Wait at least 20 minutes after the deletion before initiating steps to create another instance backup. IMPORTANT NOTE: The file deletion process can take up to 20 minutes to complete. If the files are not fully deleted, the new backup attempt will fail. 6. If required, repeat step 4 to delete any other large files, unrelated to upgrade, such as QKView or core files.
None