ZFS online migration (replication) doesnt work

Jan 18, 2017
97
2
8
42
Hi, i have 2 proxmox servers updated till the latest version. (Virtual Environment 5.1-36)
both nodes has ZFS pools with the same name.

Offline migration works fine.

when i want to migrate online, i got this message: (screenshot either). i dont know what state-test disk is.

()
2017-12-13 09:57:29 starting migration of VM 100 to node 'server4' (10.0.0.4)
2017-12-13 09:57:29 found local disk 'ZFSimages:vm-100-disk-1' (in current VM config)
2017-12-13 09:57:29 found local disk 'ZFSimages:vm-100-state-test' (via storage)
2017-12-13 09:57:29 can't migrate local disk 'ZFSimages:vm-100-disk-1': can't live migrate attached local disks without with-local-disks option
2017-12-13 09:57:29 ERROR: Failed to sync data - can't migrate VM - check log
2017-12-13 09:57:29 aborting phase 1 - cleanup resources
2017-12-13 09:57:29 ERROR: migration aborted (duration 00:00:01): Failed to sync data - can't migrate VM - check log
TASK ERROR: migration aborted

replication status = ok. But when i click migration, i got the same error.
()
2017-12-13 10:19:56 starting migration of VM 100 to node 'server4' (10.0.0.4)
2017-12-13 10:19:56 found local disk 'ZFSimages:vm-100-disk-1' (in current VM config)
2017-12-13 10:19:56 found local disk 'ZFSimages:vm-100-state-test' (via storage)
2017-12-13 10:19:56 can't migrate local disk 'ZFSimages:vm-100-disk-1': can't live migrate attached local disks without with-local-disks option
2017-12-13 10:19:56 ERROR: Failed to sync data - can't migrate VM - check log
2017-12-13 10:19:56 aborting phase 1 - cleanup resources
2017-12-13 10:19:56 ERROR: migration aborted (duration 00:00:00): Failed to sync data - can't migrate VM - check log
TASK ERROR: migration aborted
 

Attachments

  • replication.png
    replication.png
    41.6 KB · Views: 5
hmm, i thought zfs will give me the option for using local storage and live migration.

i have also a nas with shared storage. live migration works indeed.

But when do i need replication then if i cant bring this VM up on the other node?
 
ah oke. i thought. handy, if i make replication and migrate, he brings the latest data to this node and goes up.
save for migration and safe as backup.

how could i bring the vm up on the other nodeB when node A fails?