• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Full backup and restore problem

J

John Smith2

Guest
I have Fedora 6 server and Plesk 8.4 (a few clients and domains).
I do a full backup :

cd /usr/local/psa/bin
./pleskbackup all my_full_backup

Then I copy my_full_backup.gz to another server CentOS 5.3

Install Plesk 8.4
parallels_installer_v3.3.1_build080407.16_os_CentOS_5_i386

And try to restore backup
pleskrestore --create-map my_full_backup.gz -map my_mapfile.txt

Replace in file my_mapfile.txt the old IP addresses to the new IP.
pleskrestore --restore my_full_backup.gz -level all -map my_mapfile.txt

And get this migration.log
...
<stderr>An error occured during client creation: You have reached the limit on number of client accounts defined by your
license key (1 clients)
</stderr>

Why? Because my license key must be inside an archive my_full_backup.gz!

See Parallels Plesk Control Panel 8.4 for Linux/Unix Backup and Restore Utilities Administrator's Guide :
"To back up all data, including server and control panel configuration, remote database servers, license keys, user accounts, Web sites, databases, and mailboxes with e-mail messages, run the command:
/plesk_installation_directory/bin/pleskbackup all <backup file name>
"
 
not quite correct. One license may be installed just on one Plesk server (I supppose "license keys" mean drweb\kaspersky licenses). Please, contact Parallels sales team, ask temporary license key with unlimited featured for migration/transferring data on few days. Install it on the destination server, restore all data. Then you should disable the license key on the old(source) server and install your valid license on the destination server.
 
Back
Top