Moving to new openVZ Server

Discussion in 'Installation/Configuration' started by theWeird, Jul 26, 2013.

  1. theWeird

    theWeird Member

    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?
  2. MaddinXx

    MaddinXx Member HowtoForge Supporter

    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.

    Why would you do that?

    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..

Share This Page