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