As I wrote some time ago, creating your own OpenVZ infrastructure is very easy, and it can save you a lot of money compared to the usual VPS providers. But it also has other advantages.
Hashtagify uses redis to store all its data in memory, which is great for performance, but… it requires a lot of RAM. So it happened that I almost finished my 24GB, right when I learned about a new great offer for a 32GB server which costs 33% less than my 24GB one. Moving to it means that I’m going to get back my 150€ of activation costs in just 5 months, while at the same time having 8GB more. Great!
This is why I bought a new server and decided to move all my virtual machines to it from the old one. It turned out to be quite easy, but I had to find the instructions in different places, so I’ll post here how I did it for both my future reference and for anybody else having the same problem.
First of all, you have to install OpenVZ: I did it just following my previous howto.
Then, you can migrate your machines. I thought I would need to back them up and then restore them in the new server, but I found out there is a more direct and much faster way to do it: The vzmigrate command.
To use it, you first need to enable password-less ssh login from the old server to the new one (this is because vzmigrate uses the ssh protocol to move the files). First, generate your public and private keys if you didn’t already:
It is important that you create it with no passphrase. Then, move the public key to your new server, like this:
Now log into the new server and do
chmod 600 authorized_keys2
cat ../id_rsa.pub >> authorized_keys2
After this, in the old server check that everything is ok with:
If everything is ok, you whould be logged in without being asked for a password. You can log out
and start migrating your machines. For each machine, for example the one with id 101, you do:
This will take a pretty long time, depending on how big the virtual machine and how fast the net between the two servers are. There is no progress indicator, but you can get an idea how it is proceeding by checking the original size of the machine and the size of the copied one, by using the command
on the old and the new server respectively (this of course only if you mapped the openvz data directory to /vz as shown in the original howto.
When the command finishes, the new machine is ready… but only if you could move the VM IP from the old to the new server. In my case that wasn’t possible, so I had to ask for new IPs on the new server. You can assign the new IP, and remove the old one, like this:
vzctl set 101 –ipdel OLD.OLD.OLD.OLD –save
So, now you’re really good to go:
And that’s it!