Re: {ANNOUNCE] 4.11.1 RC2 cut

Hi Daan I've tried installing 4.11 RC1 (i know i'm in the wrong thread) and noticed it does something funky - like installing marvin and going to pypi to get dependencies. If its already fixed in RC2 - please ignore this request - but if not... Unfortunately some environments dont have a luxury

Re: [PROPOSE] Backup and Recovery Framework

Thanks for clarifying Nicolas. I just wanted to make sure that there wasn't any confusion in this conversation as a 'snapshot' has different meanings to different people/vendors, so I wanted to make sure we were all on the same page. BTW, for what it is worth, I love this initiative. This is an

Re: {ANNOUNCE] 4.11.1 RC2 cut

There are few PRs in pipeline, let's try to review/merge them tomorrow. Then RC2 can be cut either by tomorrow Eod or on Monday. Regards. Get Outlook for Android From: Rafael Weingärtner Sent: Thursday, June 7, 2018 8:30:32 PM To: dev

Re: [PROPOSE] Backup and Recovery Framework

First of all, the framework is agnostic of any backup vendor/provider. It just provides the way to communicate with the provider to allow users to backup their VMs. Will is right, backups are not the same as snapshots, I got confused with the Veeam backup which starts from taking a snapshot

Re: [PROPOSE] Backup and Recovery Framework

Yes, this is important to note as most people don't understand this detail. It is VERY important to this discussion though. *Will Stevens* Chief Technology Officer c 514.826.0190 On Thu, Jun 7, 2018 at 11:10 AM Todd Pigram wrote: > I agree completely. That is why I

Re: [VOTE] Apache CloudStack 4.11.1.0 LTS [RC1]

I am testing 4.11.1.0 LTS [RC1] and found a bug, reported it on #2702 (https://github.com/apache/cloudstack/issues/2702) > On June 4, 2018 at 6:04 PM Rafael Weingärtner wrote: > > > Would you mind using Github issues instead of Jira? > > On Mon, Jun 4, 2018 at 1:03 PM, Frank Maximus <

Re: [PROPOSE] Backup and Recovery Framework

Now outside of our ACS, I use Veeam for vCloud and vSphere and use Alike for our XS pools. Inside ACS, the VMs use MaxBackup On Thu, Jun 7, 2018 at 11:09 AM, Todd Pigram wrote: > I agree completely. That is why I use inside VM backup products currently. > > On Thu, Jun 7, 2018 at 11:07 AM, Will

Re: [PROPOSE] Backup and Recovery Framework

I agree completely. That is why I use inside VM backup products currently. On Thu, Jun 7, 2018 at 11:07 AM, Will Stevens wrote: > I have not been following this thread entirely, but I would not count on > our snapshot mechanism for backups. If something like Veeam is used, then > an agent is

Re: [PROPOSE] Backup and Recovery Framework

I have not been following this thread entirely, but I would not count on our snapshot mechanism for backups. If something like Veeam is used, then an agent is in play and that agent will quiesce the running processes, such as MySQL. This is important in order to do backup and DR as you will lose

Re: [PROPOSE] Backup and Recovery Framework

Rafael, I would agree with that as well as how Quadric spins up a ABD at time of backup. I have tried both Alike and Unitrends (old PHD virtual) and ACS removed the device before it works, but that was back on v4.3. On Thu, Jun 7, 2018 at 11:03 AM, Rafael Weingärtner <

Re: [PROPOSE] Backup and Recovery Framework

I believe the framework is going to be agnostic, but we need to implement "driver" to deal with different vendors API, right? On Thu, Jun 7, 2018 at 5:01 PM, Todd Pigram wrote: > Nicolas, > > Given you Veeam example, this framework is backup vendor independent? So I > could use Veeam for

Re: [PROPOSE] Backup and Recovery Framework

Nicolas, Given you Veeam example, this framework is backup vendor independent? So I could use Veeam for vSphere or Hyper-V or use Quadric (Alike) for XenServer or Hyper-V. This would sure beat the way I am doing it now, inside the VM. I will be following this closely. On Thu, Jun 7, 2018 at

Re: {ANNOUNCE] 4.11.1 RC2 cut

Sure let's do that, but first, let's merge these PRs we have been discussing today. PS. I thought this was an e-mail announcing the RC2, and not an inquiry one On Wed, Jun 6, 2018 at 4:16 PM, Daan Hoogland wrote: > Devs, > > We have a number of issues out for milestone 4.11.1 but non of them

Re: [PROPOSE] Backup and Recovery Framework

Ok, now I start to understand. So, we will be handling snapshots and they will be sent to a third-party system. Now let’s proceed. If I configure this “feature” with external=false. What does it do? Nothing? I mean, what is the purpose of this “external” parameter? On Thu, Jun 7, 2018 at 4:09

Re: [PROPOSE] Backup and Recovery Framework

Its format may depend on the provider, but under the hood it is a snapshot which can be full or incremental and it is copied and stored in a backup repository in one of the backup servers. For example, if you use Veeam, you will find your backups stored as .vbk (for full backups) and .vib (for

Re: [PROPOSE] Backup and Recovery Framework

Ok, there are a lot of things, which are kind of blurry to me. So, let’s try to go step by step. Let me ask again. What is a backup of the VM? You mention restore-point. What is it? Is it a snapshot in the hypervisor (complete/partial snapshot)? If it is not a snapshot, what is it then? Are you

Re: [PROPOSE] Backup and Recovery Framework

Hi Daniel and Rafael, I have updated the diagram picture on the FS, please let me know if the problem persists. @Daniel you are right about restoring VMs, please let me update the FS. Regarding your question, we have considered the backups as a first

Re: [PROPOSE] Backup and Recovery Framework

Hi Nicolas, The idea is great. I have some questions though. Before getting to the questions, your pictures are broken, or at least they seem broken to me. How would the “dummy” backup provider work? I mean, what does it do? where does it storage the "backup"? What is the difference from this

Re: [PROPOSE] Backup and Recovery Framework

Hi all, +1 for this feature request, thank you for bringing this to life! Volume snapshots are what our users currently use as backup solution, which has some inherent problems such as handling large volumes and the handling of multiple volumes (consistency). One thought: when restoring a VM,