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.ga...@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" <arnaud.gaill...@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
