Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: error (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <DC5EBE7F3610EB4CA5C7E92D76873E15180DD42AAD@exchange2007.carrieriq.com>
References: 
 <CAJzooYfX44YjLo5+Ffn9ZQ38ONcScyMutLANv1JenTyPOQqaSw@mail.gmail.com>
	<DC5EBE7F3610EB4CA5C7E92D76873E15180DD42AAB@exchange2007.carrieriq.com>
	<CAMdGtQ+pFdGeeA2=u9dgg=+9uKyWA5AdePUQFCe3rwOZz8qp3Q@mail.gmail.com>
	<DC5EBE7F3610EB4CA5C7E92D76873E15180DD42AAD@exchange2007.carrieriq.com>
Date: Mon, 9 Sep 2013 17:44:27 -0700
Message-ID: 
 <CAMdGtQLdJd1C9i8ukEYG9TJu3=620Lr=89Ps72KL3A6xho0JAQ@mail.gmail.com>
Subject: Re: Hbase ExportSnapshot with AWS
From: Carlos Espinoza <carlos@imgur.com>
To: user@hbase.apache.org
Content-Type: multipart/alternative; boundary=089e0160b5e49c975804e5fcce7f

--089e0160b5e49c975804e5fcce7f
Content-Type: text/plain; charset=ISO-8859-1

That'd be a great enhancement.


On Mon, Sep 9, 2013 at 4:42 PM, Vladimir Rodionov
<vrodionov@carrieriq.com>wrote:

> Great, thanks.  One possible enhancement: support for  arbitrary file
> system (not only s3).
>
> Best regards,
> Vladimir Rodionov
> Principal Platform Engineer
> Carrier IQ, www.carrieriq.com
> e-mail: vrodionov@carrieriq.com
>
> ________________________________________
> From: Carlos Espinoza [carlos@imgur.com]
> Sent: Monday, September 09, 2013 2:57 PM
> To: user@hbase.apache.org
> Subject: Re: Hbase ExportSnapshot with AWS
>
> You might be interested in a tool I recently wrote. It's a wrapper around
> the Export Snapshot tool. It's not heavily tested, but it has worked for us
> so far. You can use it to create a snapshot and export it to S3. It can
> also be used to import a snapshot from S3 into a running HBase cluster. You
> need to dedicate a bucket for this.
>
> https://github.com/lospro7/snapshot-s3-util
>
>
> On Mon, Sep 9, 2013 at 1:13 PM, Vladimir Rodionov
> <vrodionov@carrieriq.com>wrote:
>
> > There is no option to export materialized snapshot to AWS yet - only to
> > another HBase cluster.
> > You can export snapshot metadata to s3 using S3 FileSystem  in Hadoop,
> but
> > this is not you are looking for.
> > You can export snapshots to table(s) in another cluster and then use
> > distcp to copy data over to s3.
> > One caveat: you have to have spare cluster for that, because you can't
> > export table's snapshot to different cluster and
> > different table (name).
> >
> > yea, too many limitations. One major enhancement to snapshots which is
> > definitely welcomed is ability to export materialized
> > snapshots to a different DFS location (S3 in this case)
> >
> >
> > Best regards,
> > Vladimir Rodionov
> > Principal Platform Engineer
> > Carrier IQ, www.carrieriq.com
> > e-mail: vrodionov@carrieriq.com
> >
> > ________________________________________
> > From: Dhanasekaran Anbalagan [bugcy013@gmail.com]
> > Sent: Monday, September 09, 2013 12:51 PM
> > To: cdh-user; user@hbase.apache.org
> > Subject: Hbase ExportSnapshot with AWS
> >
> > Hi Guys,
> >
> > It's possible to Export Snapshot with Amazon S3 or Glacier. Currently we
> > have two hbase cluster running on same datacenter.  We want
> > backup solution for Hbase data.
> >
> > want redundant backup solution for data store. something like S3 or
> > Glacier.
> >
> > I will use CopyTable and snapshot for Hbase data. But the what is use
> > cluster are in same datacenter.
> >
> > If two cluster are down. I want retrieve data from
> >
> > Please guide me. what are the possible solution.
> >
> > -Dhanasekaran.
> >
> > Did I learn something today? If not, I wasted it.
> >
> > Confidentiality Notice:  The information contained in this message,
> > including any attachments hereto, may be confidential and is intended to
> be
> > read only by the individual or entity to whom this message is addressed.
> If
> > the reader of this message is not the intended recipient or an agent or
> > designee of the intended recipient, please note that any review, use,
> > disclosure or distribution of this message or its attachments, in any
> form,
> > is strictly prohibited.  If you have received this message in error,
> please
> > immediately notify the sender and/or Notifications@carrieriq.com and
> > delete or destroy any copy of this message and its attachments.
> >
>
> Confidentiality Notice:  The information contained in this message,
> including any attachments hereto, may be confidential and is intended to be
> read only by the individual or entity to whom this message is addressed. If
> the reader of this message is not the intended recipient or an agent or
> designee of the intended recipient, please note that any review, use,
> disclosure or distribution of this message or its attachments, in any form,
> is strictly prohibited.  If you have received this message in error, please
> immediately notify the sender and/or Notifications@carrieriq.com and
> delete or destroy any copy of this message and its attachments.
>

--089e0160b5e49c975804e5fcce7f--