I encountered the same problem a few months ago. With help from this list, I
fixed my problems without any data loss, and posted my solution on the list.
If you search the following subject line “corrupt DB after VM live migration
with storage migration”, you should see my posts.
Good luck
Ilya,
Point to be noted is that my job didn't failed coz of the timeout, but
rather coz of some VDI parameter at XENServer with below exception.
[SR_BACKEND_FAILURE_80, , Failed to mark VDI hidden [opterr=SR
96e879bf-93aa-47ca-e2d5-e595afbab294: error aborting existing process]]
I am still digg
this happened to us on non XEN hypervisor as well.
CloudStack has a timeout for a long running jobs - which i assume in
your case - it has exceeded.
Changing volumes table should be enough by referencing proper pool_id.
Just make sure that data size matches on both ends.
consider changing
"copy.
Guys,
My setup:- ACS 4.4.2. Hypervisor: XENserver 6.2.
I tried moving a volume in running VM from primary storage A to primary
storage B (using GUI of cloudstack). Please note, primary storage A LUN
(LUN7)is coming out of one storage box and primary storage B LUN (LUN14)
is from another.
For V
