Module:Hatnote list

From Wiki.CoreyBlair.US
Revision as of 20:34, 23 July 2015 by Corey (talk | contribs)
Jump to navigation Jump to search

Documentation for this module may be created at Module:Hatnote list/doc

Script error: Lua error: Internal error: The interpreter exited with status 1.

It Finally happened. I have this bad habit of updating all of my virtual Ubuntu servers at once which in turn puts a lot of load on the hosts. Tonight was the first time that I lost the main solid state cache drive on the host which in turn took the main servers that host this site along with my others. Luckily I have shared storage (which is backed up) on my NAS4Free box. The big dilemma was manually migrating the config files on the other host to activate the Virtual Servers. With a bit of googling I ran across a very helpful command which I tweaked a bit for my younger version of Proxmox. The commands below will bring your virtual machines back to life.

*First you will need to be absolutely sure that the dead node is indeed dead. Otherwise you are going to complicate life in a terrible way.
*Second, you will want to set the expected votes in quorum to 1 to make the live host realize that its the only one that matters anymore.
  pvecm e 1
*Next you will issue a series of commands being mindful that you will need '''edit to coincide with your host names and the VM ID's''' of the virtual machines you which to manually migrate.
*For Example
 mv etc/pve/nodes/'''yourdeadhostname'''/qemu-server/'''deadvmID.conf''' /etc/pve/nodes/'''yourlivehostname'''/qemu-server/
*If you are watching your live node at this point, you will see your virtual machines automagically appear on the live host.
*You can now fire your VM's up while you prepare to rebuild your failed host.

Original info found [http://pve.proxmox.com/pipermail/pve-user/2013-May/005616.html HERE]

[[Category:ProxMox]]