Good morning everyone. I would like to ask about the possibility of migrating 3 servers (WWW, MAIL, and DNS) to a multi-server environment with 7 servers (1x Panel, 2x WWW, 2x Mail, 2x DNS) using the ISPConfig Migration Tool. The current setup consists of 3 separate server instances, where the customer database on the WWW server is different from the one on the MAIL server, and yet another on the DNS server. Is it possible to import databases where customer IDs differ across servers? If this cannot be done using the migration tool, how should I approach this task? Best regards and thank you.
Customers are matched by username, so this should work unless you are using the same username multiple times for different users.
Thank you, Till. From what I’ve noticed in the databases of the migrated servers, several clients are recorded in different ways. I tried migrating the two WWW (client and www tables) and DNS (only dns tables) servers, and the result is that errors appeared, and now nothing can be saved in the new panel. Changes are not propagating to the databases on the WWW, MAIL, and DNS servers.
You can not just copy over records from different ISPConfig databases; the Migration Tool is not using that approach. The Migration tool uses the ISPConfig remote API to import records into the new server.
hello I migrate all records but CNAME record is not migrated why [ERROR] API call to dns_cname_add failed. See log file for details. [ERROR] API call to dns_cname_add failed. See log file for details. [ERROR] API call to dns_cname_add failed. See log file for details. [ERROR] API call to dns_cname_add failed. See log file for details. [ERROR] API call to dns_cname_add failed. See log file for details. 2025-02-26 11:11:05 - [ERROR] API call to dns_cname_add failed. 2025-02-26 11:11:05 - [ERROR] JSON API REPLY ERROR: data_error_regex<br />
See log migarte.log file for details. According to the error messages you posted, the new system did not accept the CNAME as it did not match the regular expression for CNAMES in ISPConfig.
2025-03-05 09:06:04 - [ERROR] API call to dns_cname_add failed. 2025-03-05 09:06:04 - [ERROR] JSON API REPLY ERROR: data_error_regex<br /> - Arguments sent were: array ( 'client_id' => '35', 'params' => array ( '_ID_' => '2055', 'server_id' => '7', 'zone' => '207', 'name' => 'www', 'type' => 'CNAME', 'data' => '@', 'ttl' => '38400', 'stamp' => '2025-03-05 09:06:04', 'serial' => '2025030509', 'active' => 'Y', 'sys_perm_user' => 'riud', 'sys_perm_group' => 'riud', 'sys_perm_other' => '', 'aux' => '0', '_migrate_status' => NULL, '_migrate_status_type' => true, '_migrate_status_dep' => true, '_primary_id' => '2055', ), 'session_id' => 'd81bb7425be62f9b702340774ae154658de4d718e', ) 2025-03-05 09:06:08 - [ERROR] API call to dns_cname_add failed. 2025-03-05 09:06:08 - [ERROR] JSON API REPLY ERROR: data_error_regex<br />
The new ISPConfig system rejected the CNAME record where you entered just "@" in the data field. Fix the name record on the old system by replacing @ with the domain name you want to point the name to like "yourdomain.tld." and run the Migration Tool again.
This is not about a site being active or not. You are using @ there when you should have used the domain name. You can not enter @ there in ISPConfig. That's why you got that error. So this is not a Migration Tool related problem. I am not sure how you entered these values in the old ISPConfig system, as the ISPConfig GUI rejects them as invalid. Did you import them manually with SQL? If you want to allow @ in that field, you must change the ISPConfig code and alter the regular expression in the form file of the CNAME record that checks the data field value.
I understand the problem and I have already solved it, but I have one more question about migration. Since I have a lot of websites that are disabled in the ISPConfig Panel, is there a way not to migrate them to the new server?
