Return-Path: X-Original-To: apmail-incubator-cloudstack-users-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 70D59E986 for ; Wed, 30 Jan 2013 22:48:51 +0000 (UTC) Received: (qmail 35186 invoked by uid 500); 30 Jan 2013 22:48:50 -0000 Delivered-To: apmail-incubator-cloudstack-users-archive@incubator.apache.org Received: (qmail 35164 invoked by uid 500); 30 Jan 2013 22:48:50 -0000 Mailing-List: contact cloudstack-users-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-users@incubator.apache.org Delivered-To: mailing list cloudstack-users@incubator.apache.org Received: (qmail 35156 invoked by uid 99); 30 Jan 2013 22:48:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Jan 2013 22:48:50 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.219.49] (HELO mail-oa0-f49.google.com) (209.85.219.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Jan 2013 22:48:45 +0000 Received: by mail-oa0-f49.google.com with SMTP id j6so2267996oag.8 for ; Wed, 30 Jan 2013 14:48:24 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type:x-gm-message-state; bh=8P5kEGfaJziKDCjREr+R/pfqiCLGwf9jWH/IXg/xtvs=; b=BVppe+0oIPaf8/0WQksIxqXqLDvzwUUC+k1Cs7aLDBMODhoqVSADhFrkGQSdqE+J+N THPCbe1m+omuJIZWdCrFUICPsZxq37V1+p6424tgDYZN28aichb+x0KkXRWGHamz/NQa P3dxTb1EkpqEJQ8NR4I69Uql/v/JgEXTLQXHgbf/1U/L0jY7kZs0fyF7JBqhb7xfUdW3 9QdHZCzuN3wV339d/2/eh4+mfUGAf15GCPZ6ZEoaofQJOuq3JllOHTcdlvxPXeUhgPr4 9DDv4DqRMoCLno/ufmAUDBpopvIFbj4oRTfqYo8fZmXvcKICYbMI2rbMjM7mXpcj5g1W OZgg== X-Received: by 10.182.117.5 with SMTP id ka5mr4789119obb.49.1359586104359; Wed, 30 Jan 2013 14:48:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.76.2.48 with HTTP; Wed, 30 Jan 2013 14:48:04 -0800 (PST) In-Reply-To: References: <11662326.1769.1359566398715.JavaMail.andrei@finka> <31530213.1794.1359566712831.JavaMail.andrei@finka> <790E7BCBCDD98F45BD43B85D7326B8D060C782AD@AMSPRD0710MB364.eurprd07.prod.outlook.com> From: David Nalley Date: Wed, 30 Jan 2013 17:48:04 -0500 Message-ID: Subject: Re: Slow snapshots with KVM To: cloudstack-users@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQn+wjxTbLfLcrXw2TopNMCYoMbmef5Q/Cg+3Liw1/gFsn8r0sHcRV5aIhCfkvvxTEsXrzJR X-Virus-Checked: Checked by ClamAV on apache.org On Wed, Jan 30, 2013 at 5:04 PM, Nux! wrote: > On 30.01.2013 21:14, Ahmad Emneina wrote: >> >> KVM does a snapshot of the whole disk, as opposed to delta's like >> xenserver. Which is why your kvm snapshots take ages to copy to secondary >> storage. > > > Is then safe to assume that a Cloudstack KVM snapshot can be used as a "full > backup" that can be restored even though there is nothing left of the > original virtual machine? Doesn't sound so bad from a reliability point of > view; an incremental/delta snapshot would not be of much case in a disaster > scenario. > As long as you realize that these are 'crash consistent' snapshots, then yes. I personally dislike using the term 'backup' for snapshots - it's certainly not a method I'd use to backup data that was important to me. --David