hi,
it seems like there is a restore bug in 2.2
i have a cluster of 3 nodes and backuped the system 210 on node 2
after the backup was successfull i did a restore on node 3 with the id 303
the restore itself was ok but the machine couldn't be started cause in the config file the wrong hdd entry was set
in the restored 303 config file the entry for the hdd was like this: 210/vm-210-disk-1.qcow2
no big deal, just a quick change from 210 to 303 and the problem was solved, but i think this is a new bug in 2.2 cause that happened never again before
to be honest, i havent had the time to try it a second time, but will do it this evening
hth and tia
it seems like there is a restore bug in 2.2
i have a cluster of 3 nodes and backuped the system 210 on node 2
after the backup was successfull i did a restore on node 3 with the id 303
the restore itself was ok but the machine couldn't be started cause in the config file the wrong hdd entry was set
in the restored 303 config file the entry for the hdd was like this: 210/vm-210-disk-1.qcow2
no big deal, just a quick change from 210 to 303 and the problem was solved, but i think this is a new bug in 2.2 cause that happened never again before
to be honest, i havent had the time to try it a second time, but will do it this evening
hth and tia