I faintly remember that XS 6.2 had a bug where if the destination SR is
full, volume migration used to fail and that used to keep volume in very
vulnerable situation, where garbage collector will kick in and remove those
volumes.
You can go through SM.log in xenserver and verify what might have
Hi Tejas,
You may want to read this email thread that I initiated in past around same
problem. I mainly moved the volumes with VMs running.
https://mail-archive.com/users@cloudstack.apache.org/msg20650.html
What is path parameter value under volume table for the missing volumes?
That value
Congratulations Wido! :)
Thank you very much for all the hard work Will!
2017-03-16 14:20 GMT-03:00 Erik Weber :
> Thanks for all you hard work and dedication, Will!
>
> Congratulations Wido! :-)
>
> --
> Erik
> tor. 16. mar. 2017 kl. 18.00 skrev Will Stevens
Thanks for all you hard work and dedication, Will!
Congratulations Wido! :-)
--
Erik
tor. 16. mar. 2017 kl. 18.00 skrev Will Stevens :
> Hello Everyone,
> It has been a pleasure working with you as the ACS VP over the past year.
> I would like to say Thank You to everyone who
Hello Everyone,
It has been a pleasure working with you as the ACS VP over the past year.
I would like to say Thank You to everyone who has supported me in this role
and have supported the project as a whole.
It is my pleasure to announce that Wido den Hollander has been voted in to
replace me as
Hi,
I searched for few documents but in all documents they are mentioning
that VHD will be available on destination storage (but database will point
to source storage)
In our case VHD file is missing from source and destination storage.