backup compatibility with new server
In my past experience, when I tried loading a passworded domain backup (created via Plesk) to a new Plesk server, the backup wasn't accepted, with a msg stating that only backups created on same Plesk server can be restored.
Maybe I wasn't doing something right, and it is actually possible to restore a plesk created domain backup to a new server, however, it created a considerable mess and seemed a very unnecessary situation.
If it isn't possible to presently restore backups on a new Plesk server, please can you add this to the to-do list, as this really is essential functionality. A password is more than sufficient security on a backup. As well, Plesk should of course create any databases contained in the backup, if they don't already exist on the domain.
BTW, I'm referring primarily to being able to FTP domain backups onto a new server, into the correct directory, so they then appear as valid backups for a domain (which can be restored). Restoring GB sized backups via http/https is not a first choice (especially as http/https connection can get broken & thus one has to start all over again).
Either-way, please can you clarify the situation, as to how it stands today.
Thinking back, I seem to remember, that (maybe) I could restore via https/http but not via ftp'ing files into backup directory on Plesk. I also seem to recall the process taking something like a week of http/https based restore 24/7. Plus then I'm pretty sure I had to create all DBs manually. Whatever, it wasn't a nice process, and not looking forward to maybe having to do it again this year - when such a process should be straightforward and simple via FTP.
Thankyou.
Due security reason only Plesk administrator can restore backups from another Plesk server.
Corresponding documentation available by link: http://download1.parallels.com/Plesk/PP12/12.0/Doc/en-US/online/plesk-installation-upgrade-migration-guide/71256.htm#
- SU
-
simes commented
Again, thinking back, I think the FTPing was reported as not possible, because of a different certificate being present in the backup, than needed for the present server. Am therefore thinking, this is what needs to be 'overridable'.