Ok tonight I had a strange situation:
1. One of my servers was fenced during a backup of KVM VM.
2. The server was going up good.
3. The server would start all VM's on the machine.
4. All VM's where started, except the one that was backupping.
5. I needed to manualy unlock that VM and start it by hand.
In my opinion that is very strange behavior because:
- The server was FENCED and restarted to ensure everything will run smooth
- It did, but one VM wasn't because of the lock.
I understand where the lock is for, but in this situation it gives a strange outcome, because one VM isn't started, and so downtime on that VM. I understand that if the VM was a HA VM it also isn't a problem, because it was started then on a other server, but this particular VM I would like to have on this server.
1. One of my servers was fenced during a backup of KVM VM.
2. The server was going up good.
3. The server would start all VM's on the machine.
4. All VM's where started, except the one that was backupping.
5. I needed to manualy unlock that VM and start it by hand.
In my opinion that is very strange behavior because:
- The server was FENCED and restarted to ensure everything will run smooth
- It did, but one VM wasn't because of the lock.
I understand where the lock is for, but in this situation it gives a strange outcome, because one VM isn't started, and so downtime on that VM. I understand that if the VM was a HA VM it also isn't a problem, because it was started then on a other server, but this particular VM I would like to have on this server.