Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 17B7A200B98 for ; Mon, 3 Oct 2016 17:59:20 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 166D1160ADC; Mon, 3 Oct 2016 15:59:20 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 5C6D5160ACD for ; Mon, 3 Oct 2016 17:59:19 +0200 (CEST) Received: (qmail 81536 invoked by uid 500); 3 Oct 2016 15:59:18 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 81508 invoked by uid 99); 3 Oct 2016 15:59:18 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Oct 2016 15:59:18 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 0628CDFB89; Mon, 3 Oct 2016 15:59:18 +0000 (UTC) From: syed To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack pull request #1600: Support Backup of Snapshots for Managed Stora... Content-Type: text/plain Message-Id: <20161003155918.0628CDFB89@git1-us-west.apache.org> Date: Mon, 3 Oct 2016 15:59:18 +0000 (UTC) archived-at: Mon, 03 Oct 2016 15:59:20 -0000 GitHub user syed reopened a pull request: https://github.com/apache/cloudstack/pull/1600 Support Backup of Snapshots for Managed Storage This PR adds an ability to Pass a new parameter, locationType, to the “createSnapshot” API command. Depending on the locationType, we decide where the snapshot should go in case of managed storage. There are two possible values for the locationType param 1) `Primary`: The standard operation for managed storage is to keep the snapshot on the device (primary). For non-managed storage, this will give an error as this option is only supported for managed storage 2) `Secondary`: Applicable only to managed storage. This will keep the snapshot on the secondary storage. For non-managed storage, this will result in an error. The reason for implementing this feature is to avoid a single point of failure for primary storage. Right now in case of managed storage, if the primary storage goes down, there is no easy way to recover data as all snapshots are also stored on the primary. This features allows us to mitigate that risk. You can merge this pull request into a Git repository by running: $ git pull https://github.com/syed/cloudstack snapshot-archive-pr Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/1600.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1600 ---- commit bfad68efa35b94f67470fd8b549aca0cc7ff7d30 Author: Syed Date: 2016-06-30T17:37:33Z Support Backup of Snapshots for Managed Storage This PR adds an ability to Pass a new parameter, locationType, to the “createSnapshot” API command. Depending on the locationType, we decide where the snapshot should go in case of managed storage. There are two possible values for the locationType param 1) `Standard`: The standard operation for managed storage is to keep the snapshot on the device. For non-managed storage, this will be to upload it to secondary storage. This option will be the default. 2) `Archive`: Applicable only to managed storage. This will keep the snapshot on the secondary storage. For non-managed storage, this will result in an error. The reason for implementing this feature is to avoid a single point of failure for primary storage. Right now in case of managed storage, if the primary storage goes down, there is no easy way to recover data as all snapshots are also stored on the primary. This features allows us to mitigate that risk. ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---