[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: KVM Live Snapshots


Thanks, Simon.

So Cloudmonkey could call the VM snapshot?

On August 23, 2018 2:25:53 PM MST, Simon Weller <sweller@xxxxxxx.INVALID> wrote:
>There are lots of ways you can implement a Business Continuity or DR
>plan.
>
>Some folks implement a second region or zone in a different market and
>build their applications or services to be resilient across different
>data centers (and/or markets). This often involved various forms of
>data replication (DB, file et al).
>
>If you rely on secondary storage for backups, the assumption here is
>that it uses a different storage system than your primary storage and
>it can be used for recovery if your primary storage was to fail.
>
>
>Now since the VM snapshot feature can be called by API and the
>resulting QCOW2 file is written to primary storage, you could use a
>script to execute the snapshot and then copy off the QCOW2 files
>somewhere else.
>
>You could also use something like the Veeam agent -
>https://www.veeam.com/windows-linux-availability-agents.html and backup
>your VMs to an offsite NFS mount.
>
>
>- Si
>
>
>
>
>________________________________
>From: Asai <asai@xxxxxxxxxxxxxxxxxxxxx>
>Sent: Thursday, August 23, 2018 4:06 PM
>To: users@xxxxxxxxxxxxxxxxxxxxx
>Subject: Re: KVM Live Snapshots
>
>So, I think this is kind of an elephant in the room.
>
>How do we get a standalone VM backup?  Or what is the best way to back
>up Cloudstack?
>
>Right now we are making regular DB backups, and backing up secondary
>storage (for volume snapshots).  But in case of disaster, how do we
>recover this?
>
>Is there third party software available?
>Asai
>
>
>> On Aug 22, 2018, at 10:17 AM, Ivan Kudryavtsev
><kudryavtsev_ia@xxxxxxxxx> wrote:
>>
>> There is no way to run scheduled snapshots for whole vm, at least
>with KVM.
>> I suppose the function is for adhoc only, especially as you may know
>they
>> are not copied to secondary storage.
>>
>> чт, 23 авг. 2018 г., 0:10 Asai <asai@xxxxxxxxxxxxxxxxxxxxx>:
>>
>>> Great, thanks for that.
>>>
>>> So, is there a way then to make these whole VM snapshots recurring
>like
>>> recurring volume snapshots?
>>>
>>> What are best practices for recovering a volume snapshot?  e.g.
>disaster
>>> recovery scenario?
>>>
>>> Asai
>>>
>>>
>>>
>>>

-- Asai