cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nguyen Anh Tu <>
Subject Re: [DISCUSS] Disaster Recovery solution for CloudStack
Date Mon, 03 Jun 2013 08:40:42 GMT

Any idea?

2013/5/31 Wido den Hollander <>

> On 05/31/2013 11:02 AM, Nguyen Anh Tu wrote:
>> Hi forks,
>> I'm looking for a Disaster Recovery solution on CS. Looking around I found
>> an article showing some great informations but not enought. Personally I
>> think:
>> + Host: CS already implemented migration, which can move VMs to another
>> pearful host
>> + Database: we have replication
> Replication is not enough. Your database with CloudStack is key, it's your
> most precious metadata, so make sure you have GOOD, very good backups of it.
> The best would be a dump of the database every X hours and have binary
> logs as well to be able to go into into point in time with your database.
>  + Management Server: we can use multi MS
>> + Primary Storage: it's the important component when Disaster Recovery
>> happen. It contains ROOT and DATA volumes and nobody happy if they're
>> lost.
>> We need mirror (or replicate) solution here. Many distribute file system
>> can help (GlusterFS, Ceph, Hadoop..). An interesting solution I found on
>> XenServer is Portable SR, which make the SR become fully self-contained.
>> We
>> can detach it and re-attach to a new host. Nothing lost.
> CloudStack can't tell you anything about how safe the data is on your
> primary storage, so you just want to make sure you never loose data on it.
> Ceph is a great example (I'm a big time fan!) of how you can store your
> data on multiple machines. But even when not using Ceph, just make sure you
> don't loose data on it.
> ZFS with zfs send|receive is a great way to backup your data to a
> secondary location in case something goes wrong and you need to restore.
> Wido
>  + Secondary Storage: Easy to backup.
>> How do you think? Did you have a plan to do Disaster Recovery?
>> Thanks,



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message