Open Stack

On Mon, Sep 16, 2013 at 5:31 AM, Michael Still <mikal at stillhq.com> wrote:

> On Fri, Sep 13, 2013 at 7:51 AM, Dolph Mathews <dolph.mathews at gmail.com>
> wrote:
>
> > ++ Data backups are a solved problem, and no DB admin should trust an
> > application to perform its own backups.
>
> I'm not completely sure I agree. Consider the case where a cloud with
> active users undertakes an upgrade. The migrations run, and they allow
> user traffic to hit the installation. They then discover there is a
> serious problem and now need to rollback. However, they can't just
> restore a database backup, because the database is no longer in a
> consistent state compared with the hypervisors -- users might have
> created or deleted instances for example.


> In this scenario if we could downgrade reliably, they could force a
> downgrade with db sync, and then revert the packages they had
> installed to the previous version.
>
> How would they handle this scenario with just database backups?
>

Great point, but I still wouldn't *rely* on an application to manage it's
own data backups :)


>
> Michael
>
> --
> Rackspace Australia
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 

-Dolph
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130916/b4497bd2/attachment.html>