Change in behaviour - Address Manager v25.1
Address Manager v9.5.0 introduced a different migration engine that was set as the default engine for the migration service. In Address Manager v25.1, the legacy engine has been returned as the default engine for the Address Manager migration service. The migration engine introduced in v9.5.0 can still be accessed by uploading the migration file with a manifest file, for more information refer to Selecting the migration engine.
Use one or more XML files to migrate data into Address Manager.
After structuring the data in the XML file, you import the files to Address Manager and queue them for migration. You can use the migration function to migrate data from another system into Address Manager, or to add large amounts of new data.
To migrate configuration data from other types of servers, contact BlueCat Professional Services for assistance. For more information, visit https://care.bluecatnetworks.com.
The Address Manager migration engine Document Type Definition (DTD) file defines the structure of the migration XML file. To receive the DTD file for validation of migration XML, contact BlueCat Customer Care.
On the Migration service page, you can upload XML files and queue them for migration. On the System logs page, you can download migration logs to your workstation and delete logs from the server.
- If a suitable parent block exists in Address Manager, the network will be added to that block.
- If no parent block exists, Address Manager won't create the network and will instead log an error and skip the element.
A known issue exists where DNS/DHCP Servers may not appear in the Dashboards page if they are within a configuration that was created with migration XML. For more information and workaround steps, refer to KI-026967.