Submitted by info@orderlastm... on Mon, 08/14/2017 - 20:39
Hi I know there is a document about upgrading from 14 to 16
https://www.virtualmin.com/documentation/system/os/ubuntu-trusty-to-xenial
PROBLEM: last time I fail to upgrade, end up I restore the image and cause a lot other side issues...SSH screw up....firewall screw up
QUESTION: to reduce the risk fail upgrading, what is the best strategy to do? I don't mind open a new identical Linode for duplicate but how about virtulamin? upgrading a live sever is a "real hazzle".....
Status:
Active
Comments
Submitted by andreychek on Mon, 08/14/2017 - 22:27 Comment #1
Howdy -- yeah some people like to do live upgrades, others prefer to migrate their domains to a new server.
Which you do comes down to personal preference.
If you decide you'd prefer to migrate your domains to a new server, there's instructions on how to do that here:
https://www.virtualmin.com/documentation/system/migrate
Submitted by info@orderlastm... on Mon, 08/14/2017 - 22:39 Comment #2
I roughly go through the document, one concner
1) "same license on both servers during your migration." s so I can input same licence key on new server and that won't kill the old one?
2) new server has new ip, any concern it will affect other software?
Submitted by andreychek on Mon, 08/14/2017 - 23:31 Comment #3
Yup, that's correct, you can use the same license on both servers during your migration. It won't do anything bad to the other server.
Regarding the IP, this is a common method to migrate, and it's normal to have a new IP when you're migrating to a new server... is there a specific software concern you have? Is there a particular piece of software you're concerned about?
Submitted by info@orderlastm... on Mon, 08/14/2017 - 23:38 Comment #4
I think most concern the is DNS pointing to new IP, how to I know it is point to new ip or old ip? because DNS is alwasy something takes time pointing to another server...make sense?
Submitted by andreychek on Tue, 08/15/2017 - 09:54 Comment #5
It can take a little time for DNS to update when switching from one server to another.
If you're using your Virtualmin server as a DNS server, the instructions above offer steps that temporarily reduce the DNS cache time during the transition. That's done in the section "DNS TTL".
However, we also recommend making changes such as migrations late at night, perhaps on a Friday, so it's outside of business hours.
Submitted by info@orderlastm... on Tue, 08/15/2017 - 19:43 Comment #6
I have stupid question...sorry I'm not a very very tech guy
without DNS pointing to new server, can I check all website on new sever "locally" to see before playing around with DNS TTL?
Submitted by andreychek on Tue, 08/15/2017 - 22:05 Comment #7
A common way to do that is using an alias.
If you have an available domain name -- for example, "example.com" -- use example.com on your new server.
To do that, give the domains on your new server aliases such as mydomain.example.com.
There are more details on that here:
https://www.virtualmin.com/documentation/web/faq#toc-how-do-i-make-domai...