Host name could not be imported due to an unexpected server error. Reason: Specified file does not contain any backup images for the selected device
Article ID: 433931
Updated On:
Products
Issue/Introduction
A situation has been identified where a backup of a Virtual Appliance, successfully created and exported from the Management Center (MC) to an external server, cannot be restored after the virtual appliance is deleted from the MC, subsequently re-deployed with the identical initial setup and host name, and then re-added to the same Management Center.
The process followed was:
- A backup of the existing Virtual Appliance configuration was made on the Management Center.
- The backup file was exported to an external server for safe keeping.
- The Virtual Appliance device was deleted from the Management Center.
- A new instance of the Virtual Appliance was re-deployed, configured with the same host name and initial settings as the original.
- The newly deployed Virtual Appliance was re-added to the Management Center.
- An attempt was made to restore the configuration to the newly added appliance using the previously taken backup file.
Environment
When attempting to upload the backup file from the external server via the Management Center interface, the restoration process fails, presenting the following error message:Host name could not be imported due to an unexpected server error. Reason: Specified file does not contain any backup images for the selected device
Cause
The failure occurs because, despite the newly deployed Virtual Appliance having the same configuration (e.g., hostname) as the old one, the Management Center treats it as a completely distinct entity.
The underlying reason is that upon deletion and subsequent re-deployment of the Virtual Appliance, even if it uses the same virtual machine image or configuration template, a different internal Appliance ID is assigned to the new instance. This Appliance ID is a unique identifier used by the Management Center to associate a backup file with a specific managed device. Since the backup file contains the Appliance ID of the original device, the Management Center correctly rejects the file during the restoration attempt on the new device, interpreting it as a backup intended for a different appliance, hence the "Specified file does not contain any backup images for the selected device" error. In essence, the new device is functionally identical but internally unique from the perspective of the Management Center's database.
Resolution
Recommended Solutions and Workarounds
Since the Management Center's backup/restore mechanism is tied to the unique Appliance ID, configuration restoration must be handled at the individual appliance level (on the appliance itself or via alternative methods) rather than via a Management Center backup created for a different Appliance ID.
The following solutions should be implemented depending on the specific appliance being managed (e.g., Content Analysis System or Proxy):
1. For Content Analysis System (CAS)
If the device being managed is a Content Analysis System, the configuration and system information should be backed up directly on the CAS appliance itself, independent of the Management Center.
- Action: If you need to reinstall a CAS device and restore its configuration, you should directly access the CAS's user interface (UI) or command-line interface (CLI) to make a backup of the configuration and system information (sysinfo).
- Procedure: Utilize the built-in system utilities within the CAS to Archive or Restore the System Configuration. This method ensures the backup is tied to the internal configuration format of the CAS, which is not dependent on the Management Center's Appliance ID tracking.
- Reference: Consult the official technical documentation for detailed instructions on Archive or Restore the System Configuration.
2. For Proxy Appliances (e.g., Edge SWG, ProxySG/ASG)
If the device is a Proxy appliance, a different process is required to export and import the configuration, particularly if sensitive data like keyrings is involved.
- Action: Instead of relying on the MC backup, use the native Proxy functionality to export the configuration, which can then be imported to the newly deployed proxy appliance.
- Procedure: Follow the detailed instructions for Copying / exporting the configuration (including keyrings) from one Proxy to another Proxy. This process typically involves exporting the configuration and often requires specific steps to handle encrypted elements like SSL keyrings securely.
- Reference: Consult the official knowledge base article: Copy / export the configuration (including keyrings) from one Proxy to another Proxy.
Feedback
