Mailing-List: contact cloudstack-users-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-users@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <B1DF26ECC0458748AC97CECE2DA98D41012FA385ECE0@SJCPMAILBOX01.citrite.net>
References: 
 <CADq5e0xWyPU5czJ35VYWhGvCoNB5qZkpaUOsaQEGKdeeAx+dhw@mail.gmail.com>
	<721618600.21672757.1357571059746.JavaMail.root@inria.fr>
	<B1DF26ECC0458748AC97CECE2DA98D41012FA385ECE0@SJCPMAILBOX01.citrite.net>
Date: Tue, 8 Jan 2013 08:28:09 +0100
Message-ID: 
 <CADq5e0zETYbLPySGbRk8bXDfsVn9G7Pe7tNKJXs9rV8inoA5Kw@mail.gmail.com>
Subject: Re: Secondary storage migration
From: Arnaud Gaillard <arnaud.gaillard@xtendsys.net>
To: cloudstack-users@incubator.apache.org
Content-Type: multipart/alternative; boundary=bcaec5040838353f8904d2c1e308

--bcaec5040838353f8904d2c1e308
Content-Type: text/plain; charset=ISO-8859-1

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.Huang@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
>

--bcaec5040838353f8904d2c1e308--