• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • 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.

Migration from 1 Server to 2

A

AiG

Guest
Hi,

I have an old server running Plesk (8 I think) and two new servers (Plesk 10.3.1). I'd like to migrate the old server to the new one's, although one server should handle only mail, the other only web.

How would I migrate them? What happens when I migrate them using the Migration Manager? I think it will only create copies, right? The Nameserver is external, so as long as I dont swap DNS pointers, nothing else will happen, am I right??

Regards
 
Generally you can migrate web content to one node and mail content to another one. Those would be two separate migrations. See the migration guide for details. Note, that your customers will have 2 separate accounts - one for mail server and another one for web. If they create new site on one server, it won't function on another server until created manually.

Yes, migration creates copies only. Your external DNS won't be changed, you'll have to reconfigure it when migration is done.
 
One additional thing to consider: You should disable email for each account on the server that's only doing the web side of things.

There are a couple of reasons for this. Most importantly, if a web application sends email to a local address (e.g. a form to email script that sends to [email protected]), then it would try to deliver the message locally, and if no mailbox by that name is found, it will bounce it. But if you switch email off for the domain it will then do a DNS lookup to find the MX record and send to there (which will be your email server).

Faris.
 
Back
Top