#1  
Old 26th July 2013, 13:51
theWeird theWeird is offline
Member
 
Join Date: Nov 2009
Posts: 70
Thanks: 10
Thanked 6 Times in 5 Posts
Default Moving to new openVZ Server

Hey there,

I am thinking about grabbing a new, more powerful server from my datacenter than the server I use at the moment.

To be able to easy switch all websites, mail accounts and other services to a new hardware I have the following setup on my old machine:

Hardware Node: Debian 6.0 with Proxmox pve kernel
All other servers: openvz-containers

ISPConfig3 installed on all servers, virtual and hardware
Panel server is one of the virtual servers

My first question:
Do you have any suggestions on the selection of the distribution for the new server? Would you suggest me to go on using Debian with Proxmox kernel or is it better to rely on RedHat/CentOS? Which distribution has the better maintained openVZ packages?

For the serverchange I planned the following steps:
- Setting up the new hardware node and installing as ISPConfig V-Server
- Setting a lower TTL for all A and AAAA DNS records
- Stopping first container
- Creating a vzdump
- Copy the dump to the new server
- restore from dump on new server
- changing V-Server ID for migrated server in panel database
- changing IP for migrated server via ISP
- next container

What do you think about this steps?
Reply With Quote
Sponsored Links
  #2  
Old 27th July 2013, 20:00
MaddinXx MaddinXx is offline
Senior Member
 
Join Date: Jul 2011
Location: Switzerland
Posts: 200
Thanks: 26
Thanked 65 Times in 48 Posts
 
Default

RHEL/CentOS/EL is better supporter as it's the main distro OpenVZ is developed for. However, they started creating "official" packages for Debian again which should also be up-to-date... but personally I prefer CentOS for OpenVZ nodes.

Quote:
Setting up the new hardware node and installing as ISPConfig V-Server
Why would you do that?

Quote:
- Creating a vzdump
- Copy the dump to the new server
- restore from dump on new server
You should be able to use vzmigrate which can migrate on the fly over network so you don't have to vzdump, copy manually and restore again. This should already be pretty stable.

I may be wrong, but wouldn't it be the easiest to just replace the IP's of the current server's in ISPConfig DB rather than re-adding your server?

So you would migrate all to new node, have old + new running. Change IPs in ISPConfig DB (so it used the new ones) while pointing DNS records on old ones to the new IPs and lowering TTL so clients get this fast.

That way, the old server will still be online (trying to point visitors to the new server) and all changes made via ISPConfig are done on the new ones. As soon as some time is over and everyone has the IPs of the new server, you can shutdown the old one.

Would be my idea..
Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
ISPConfig 3 system installation script Mark_NL Tips/Tricks/Mods 12 7th March 2014 07:30
500 internal error after upgrade abintipl Installation/Configuration 9 18th July 2012 13:51
Sending email issue lezelf Installation/Configuration 15 9th August 2011 12:20
Not working emails (DNS and postfix problem?) shekiman Installation/Configuration 9 1st March 2011 17:25
Can't Ping over VPN RoMiONeT Server Operation 2 4th July 2010 01:19


All times are GMT +2. The time now is 05:12.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.