Hi,

Sid is right - you'll need to get the SSL certificate copied across to the
new VPS. It will be fine having it running on both while you're testing it.
You can put the new IP address in your hosts file to test it to make sure
everything is right.

Then, you'll have to get all the email accounts set up and migrated across.
We've used a tool called imapsync in the past which works pretty well - you
can run it progressively and it will sync email that is new meaning your
final sync (or even sync AFTER the fact) will ensure that no mail is lost.

Hopefully you don't have hundreds to do!

Attached is a document that we give to our clients who are moving to
Office365. I direct your attention to the bit near the bottom regarding
imapsync though.

Another option we had explored with our service provider was some IP
routing so that we would retain the old IP address, but traffic to it would
be routed to our new server. We had decided against that in the end because
we wanted the setup to be as transparent as possible.

Cheers, and good luck!

 - Bob -

On Sun, 28 Feb 2021 at 11:11, Stefan Schulz <[email protected]> wrote:

> I guess this is something that a lot of folks have come across and done
> successfully?!?
> My hosting provider needs me to move my VPS to a different hardware as
> well as doing a system update at the same time (from fully updated Ubuntu
> 18.04 to new install of Ubuntu 20.04)
> I have read quite a few guides/tutorials/how to's by now and have a pretty
> good grasp, but there are a few questions that remain.
>
> Because of the simultaneous upgrade, I can not 'simply' copy the full VPS
> over, but rather need to transfer single websites (and their emails) to the
> new machine and then set the DNS records to reflect the change. But here
> lies the issue. Website/Database is easy, but all my clients have their
> email programs pointing to a central domain name, which has the SSL
> certificate. Now if I move the email to the new server and point the MX
> records there, then things become disjointed.
>
> First I thought I tell my clients to prepare and let them set their email
> programs to use mail.<their-domainname>, but that means they can't use SSL
> to communicate (wich belongs to the central domain). Ideally the whole move
> will not include my clients to do anything!, BUT if they do not change
> settings in their email programs, then incoming mail is on a different VPS
> than the machine they are contacting to read/send email.
>
> Would anyone have a clue of how to avoid this issue? Bonus points for a
> solution, that does not include my clients having to do anything on their
> own devices.
> I will have to think about a solution, where I move the central domain
> INCLUDING all email files in one go, right?
>
> Note: I have full access to both VPS (incl firewall) as well as the
> respective DNS records.
>
> Back to googlefoo
> Stefan
>
> --
> --
> NZ PHP Users Group: http://groups.google.com/group/nzphpug
> To post, send email to [email protected]
> To unsubscribe, send email to
> [email protected]
> ---
> You received this message because you are subscribed to the Google Groups
> "NZ PHP Users Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/nzphpug/e4ada8ec-7507-43e5-8ad4-12955fbb7823n%40googlegroups.com
> <https://groups.google.com/d/msgid/nzphpug/e4ada8ec-7507-43e5-8ad4-12955fbb7823n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Bob Brown, Web Developer.

-- 
-- 
NZ PHP Users Group: http://groups.google.com/group/nzphpug
To post, send email to [email protected]
To unsubscribe, send email to
[email protected]
--- 
You received this message because you are subscribed to the Google Groups "NZ 
PHP Users Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nzphpug/CAOV%3D4jz%3DuBhFPrJAjBJgeGZZmCz%2BRMw6sFUeFOaBCO8Vmv1M1w%40mail.gmail.com.

Attachment: Leaving Turboweb Email Migration.pdf
Description: Adobe PDF document

Reply via email to