• 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.

convert and restore

A

AlessioP

Guest
We have installed and operated a plesk 8.1 machine. Since the whole procedure is quite critical and we wanted to bring up to date the platform to 9.x.x release, a new windows 2003 server machine has been installed with the new version of plesk running on it. What we wanted to do next, is to bring plesk 8.1 which is now running, on this new machine. In order to do this we have created the backup with the proper utility and brought into the new machine.
Next, we have converted it with pre9-backup-convert.exe, the utility finished the conversion without detecting any problem.
Logging on new plesk, there's a backup available to be restored in Home, Backup Manager.
What we can't understand is why the interface report this error: This file is not a valid backup file. How can I find out what went wrong during the conversion? Is it a clue the fact that the operating machine has a different storage path of plesk and www files? I'll wait for an answer from you on how I can find a solution to this problem.
Let's suppose now that we have managed to succesfully complete the backup on the new machine, plesk recommends to keep the licence up to date. Once we bring it up to date, should any problem occur, the previous plesk 8.1 machine could experience licence issues? How can I avoid such a problem?
[15.26.02] derik78: We have installed and operated a plesk 8.1 machine. Since the whole procedure is quite critical and we wanted to bring up to date the platform to 9.x.x release, a new windows 2003 server machine has been installed with the new version of plesk running on it. What we wanted to do next, is to bring plesk 8.1 which is now running, on this new machine. In order to do this we have created the backup with the proper utility and brought into the new machine.
Next, we have converted it with pre9-backup-convert.exe, the utility finished the conversion without detecting any problem.
Logging on new plesk, there's a backup available to be restored in Home, Backup Manager.
What we can't understand is why the interface report this error: This file is not a valid backup file. How can I find out what went wrong during the conversion? Is it a clue the fact that the operating machine has a different storage path of plesk and www files? I'll wait for an answer from you on how I can find a solution to this problem.
Let's suppose now that we have managed to succesfully complete the backup on the new machine, plesk recommends to keep the licence up to date. Once we bring it up to date, should any problem occur, the previous plesk 8.1 machine could experience licence issues? How can I avoid such a problem?
 
Just in addition, logs may help to determine the actual reason of the error. You can find logs in Plesk\PMM\sessions\backup date\ folder, pay attention to migration.result file.

Regards,
Maria
 
Back
Top