-
Notifications
You must be signed in to change notification settings - Fork 153
How to migrate everything properly between VPS-s? #330
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already o 8000 n GitHub? Sign in to your account
Comments
Hi @manaus0xff! You should copy the config/ and data/ directories from the old machine to the new machine, and start mox. If the new machine has a new hostname, you would have to update the Hostname in config/mox.conf. With a new hostname, you would also update some DNS records, for example the MX records. If you're using the mox.service (systemd unit file), you would copy that too. By the way, the old and new machine both need to 32-bit or 64-bit. The database files (for the message indexes) can't be moved between 32-bit and 64-bit machines. |
Alright. What would be the correct way to set up the paths in this case? On the 2nd machine, on Arch Linux, after installation from the AUR repo (
And a
Although I could run
? Must And I won't have to run |
Let's say, I've decided to move to a VPS of other VPS provider. After having updated my DNS records accordingly, how would I properly
a) back up everything on server S1
b) restore it server S2
?
To then re-run it smoothly.
Meaning, which precisely files should be backed up for migration? And how to, properly?
And the same for restoration.
The text was updated successfully, but these errors were encountered: