SYSTEM INFORMATION
OS type and version
Debian Linux 12
Virtualmin version
7.20.2 Pro
Hi there,
I have in my mind to change the server to reduce maintenance costs.
What is the main concerns to be aware?
In my current server i have ~11 virtual servers and each of them point to my NS server also hosted on same server.
Is the making ISO from root of the server and cloning it to a new server will be successful without any loses and problems?
Will i have problems with DNS propagation or something else maybe?
My plan is to do the migration after midnight when there is no traffic at all, coz this is production servers.
Thanks.
Edit:
new server has different specifications
@maxyo.vip ,
Migrating an install to a new server, with a new IP address isn’t generally going to cause problems if you do it correctly.
Migrating your Virtualmin installation to a new server involves several steps, such as backups and restores, testing, and going live. This document is designed to help you navigate through this process. The process of migrating your Virtualmin...
However, keep in mind you DO need to plan these things appropriately, and make sure you’ve registered your new IP address at the registrar if it’s being used for nameserver…
In my registrar i only setup the NS… here is the example…
At registrar:
maindomain[.]com
NS1: ns1.maindomain[.].com
NS2: ns2.maindomain[.].com
domain2[.].com
NS1: ns1.maindomain[.].com
NS2: ns2.maindomain[.].com
domain3[.].com
NS1: ns1.maindomain[.].com
NS2: ns2.maindomain[.].com
I access to Webmin via maindomain[.]com:10000
I want to transfer ALL servers including maindomain.
Joe
November 23, 2024, 11:18pm
4
That’s not a Virtualmin question. That’s well below the level where Virtualmin is involved.
But, generally, that is a reasonable way to move from one VM to another at a cloud hosting provider.
1 Like
I have the same question, but not got any solution.
Joe
December 1, 2024, 12:09am
6
Have you read the documentation that was linked above? Perhaps start a new topic with the problems you have following that documentation.