Hi there, i've been using proxmox for some time now and i'm pretty happy with it. Though i have a question about it's failover functionality..
I am using lvm on top of DRBD. All data is synchronized live to the other node, ok cool .. so that means that if i have 10 vm's running on server A and that servers burns down/explodes/or something else that won't make it come back on-line, all the data is safely on server B .. but now, .. why can't i start them if the master of my cluster goes down ..
Besides all the great things proxmox has, this is a real drawback of proxmox .. i have a cluster for failover, master dies, np i have a backup! ow, .. no wait, i can't control it because the master is down.. This is the main reason why i'm not using backup scheduler, because i'm using this thing in production and some time ago the master decided to crash .. I found out it was an LVM issue during backup, now that's np, as long as i know i can start the vm's easily on the slave.
(to bad the Troubleshoot page on the wiki is still emtpy )
Sorry for whining
I am using lvm on top of DRBD. All data is synchronized live to the other node, ok cool .. so that means that if i have 10 vm's running on server A and that servers burns down/explodes/or something else that won't make it come back on-line, all the data is safely on server B .. but now, .. why can't i start them if the master of my cluster goes down ..
Besides all the great things proxmox has, this is a real drawback of proxmox .. i have a cluster for failover, master dies, np i have a backup! ow, .. no wait, i can't control it because the master is down.. This is the main reason why i'm not using backup scheduler, because i'm using this thing in production and some time ago the master decided to crash .. I found out it was an LVM issue during backup, now that's np, as long as i know i can start the vm's easily on the slave.
(to bad the Troubleshoot page on the wiki is still emtpy )
Sorry for whining