You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Arnaud Gaillard <ar...@xtendsys.net> on 2012/12/12 22:19:11 UTC
Secondary storage migration
Hello,
We are currently trying to change our secondary storage NAS, and we would
like to know if you have some experience to share on the best way to
decommission a secondary storage and replace it with a new one.
We already have added our new secondary storage, to the different zone, but
there is no specific controle over it. I know that template created from
now are duplicated on both storage but what about existing one?
What about system VM template?
Any thought?
Thanks!
AG
Re: Secondary storage migration
Posted by Nitin Mehta <Ni...@citrix.com>.
Arnaud - thanks for your feedback. Let me know if you need further help on
this.
It would be great if you could file a bug for all the issues you think
should be fixed in this area. There is some work going on this front so
please expect improved behavior.
On 08/01/13 12:58 PM, "Arnaud Gaillard" <ar...@xtendsys.net>
wrote:
>Hello
>
>We tried the method that you are describing, this is more or less the one
>that is mentionned in the cloudstack wiki, however we still have a lot of
>issue... we had to recreate the SSVM and we are still struggling to finish
>this migration. (currently we had to kill the SSVM again and we are unable
>to recreate it...). This is may not be as easy as it seems.
>
>I think that cloudstack should improve how it handles multiple secondary
>storage. Currently it is very poorly done (when you have multiple
>secondary
>storage for instance only newly template/iso are copied on the new
>storage,
>and there is no way to copy old template to the new storage from GUI or
>API).
>
>We should be able to recover easily from situation where you secondary
>storage get corrupted, is becoming unavailable, or is suffering a major
>crash.
>
>We have no problem to recreate a secondary storage from our backup, but to
>make cloudstack work with it smoothly is another story.
>
>Arnaud
>
>On Tue, Jan 8, 2013 at 2:07 AM, Alex Huang <Al...@citrix.com> wrote:
>
>> erience doing this. It involves
>>
>> - Stop CloudStack
>> - copying everything from one secondary storage to another.
>> - change the references to that secondary storage in the database to the
>> new secondary storage. I can't recall all the places that need chang
>>
Re: Secondary storage migration
Posted by Arnaud Gaillard <ar...@xtendsys.net>.
Hello
We tried the method that you are describing, this is more or less the one
that is mentionned in the cloudstack wiki, however we still have a lot of
issue... we had to recreate the SSVM and we are still struggling to finish
this migration. (currently we had to kill the SSVM again and we are unable
to recreate it...). This is may not be as easy as it seems.
I think that cloudstack should improve how it handles multiple secondary
storage. Currently it is very poorly done (when you have multiple secondary
storage for instance only newly template/iso are copied on the new storage,
and there is no way to copy old template to the new storage from GUI or
API).
We should be able to recover easily from situation where you secondary
storage get corrupted, is becoming unavailable, or is suffering a major
crash.
We have no problem to recreate a secondary storage from our backup, but to
make cloudstack work with it smoothly is another story.
Arnaud
On Tue, Jan 8, 2013 at 2:07 AM, Alex Huang <Al...@citrix.com> wrote:
> erience doing this. It involves
>
> - Stop CloudStack
> - copying everything from one secondary storage to another.
> - change the references to that secondary storage in the database to the
> new secondary storage. I can't recall all the places that need chang
>
RE: Secondary storage migration
Posted by Alex Huang <Al...@citrix.com>.
I've had experience doing this. It involves
- Stop CloudStack
- copying everything from one secondary storage to another.
- change the references to that secondary storage in the database to the new secondary storage. I can't recall all the places that need changing but it was not a lot.
- restart cloudstack
Other thoughts:
- Why not just add secondary storage to cloudstack and use both?
- in the future, should use fqdn for secondary storage then you can just swap out the ip address in your dns.
--Alex
> -----Original Message-----
> From: Julien Garet [mailto:julien.garet@inria.fr]
> Sent: Monday, January 07, 2013 7:04 AM
> To: cloudstack-users@incubator.apache.org
> Subject: Re: Secondary storage migration
>
> Hello,
>
> We are in the same situation, did you have any answer about the secondary
> storage migration ?
>
> ----
> Julien Garet
>
> ----- Mail original -----
>
> > De: "Arnaud Gaillard" <ar...@xtendsys.net>
> > À: cloudstack-users@incubator.apache.org
> > Envoyé: Mercredi 12 Décembre 2012 22:19:11
> > Objet: Secondary storage migration
>
> > Hello,
>
> > We are currently trying to change our secondary storage NAS, and we
> > would
> > like to know if you have some experience to share on the best way to
> > decommission a secondary storage and replace it with a new one.
>
> > We already have added our new secondary storage, to the different
> > zone, but
> > there is no specific controle over it. I know that template created
> > from
> > now are duplicated on both storage but what about existing one?
>
> > What about system VM template?
>
> > Any thought?
>
> > Thanks!
>
> > AG
Re: Secondary storage migration
Posted by Julien Garet <ju...@inria.fr>.
Hello,
We are in the same situation, did you have any answer about the secondary storage migration ?
----
Julien Garet
----- Mail original -----
> De: "Arnaud Gaillard" <ar...@xtendsys.net>
> À: cloudstack-users@incubator.apache.org
> Envoyé: Mercredi 12 Décembre 2012 22:19:11
> Objet: Secondary storage migration
> Hello,
> We are currently trying to change our secondary storage NAS, and we
> would
> like to know if you have some experience to share on the best way to
> decommission a secondary storage and replace it with a new one.
> We already have added our new secondary storage, to the different
> zone, but
> there is no specific controle over it. I know that template created
> from
> now are duplicated on both storage but what about existing one?
> What about system VM template?
> Any thought?
> Thanks!
> AG