Hi JM I see your point, actually we are trying to backup the hbase data to AWS S3 on a daily/weekly basis, that's why in my first mail i think maybe org.apache.hadoop.hbase.mapreduce.Export / org.apache.hadoop.hbase.mapreduce.Import would be the best choice for us, any idea?
Thanks aij On Wed, Apr 2, 2014 at 9:51 PM, Jean-Marc Spaggiari <jean-m...@spaggiari.org > wrote: > Hi, > > For incremental, you might want to look at replication.... > > JM > > > 2014-04-02 9:49 GMT-04:00 R W <aijw...@gmail.com>: > > > Hi JM > > > > Here is the problem if we use the ExportSnapshot feature to export data > to > > the dest cluster, it seems we cannot do incremental backup. > > > > Thanks > > aij > > > > > > On Wed, Apr 2, 2014 at 7:54 PM, Jean-Marc Spaggiari < > > jean-m...@spaggiari.org > > > wrote: > > > > > Hi, > > > > > > You can take a look at replication. Activate replication from a date X > > and > > > then copy table from date 0 to date x from the origin to the dest > > cluster. > > > > > > You can also export the snapshot. Take a look at 15.8.8 here: > > > http://hbase.apache.org/book/ops.snapshots.html > > > > > > JM > > > > > > > > > 2014-04-02 7:23 GMT-04:00 R W <aijw...@gmail.com>: > > > > > > > Hi Esteban > > > > > > > > I checked the snapshot feature and tried myself, it's very good, one > of > > > the > > > > introduction > > > > > > > > > > > > > > http://blog.cloudera.com/blog/2013/03/introduction-to-apache-hbase-snapshots/mentioned > > > > about: > > > > > > > > Clone a snapshot: This operation creates a new table using the same > > > schema > > > > > and with the same data present in the specified snapshot. The > result > > of > > > > > this operation is a new fully functional table that can can be > > modified > > > > > with no impact on the original table or the snapshot. > > > > > > > > > > > > I think this clone operation will make a copy of the snapshot, then > > > create > > > > the new table from the copy of the snapshot, am i correct? Otherwise, > > > > modification to the new table will change the snapshot, right? > > > > > > > > Another question, if we want to backup hbase data somewhere else, it > > > seems > > > > we cannot go with snapshot feature, we want the data to be backup > even > > > > after the whole Hadoop cluster down, any idea? > > > > > > > > Thanks > > > > aij > > > > > > > > > > > > On Wed, Apr 2, 2014 at 2:12 PM, Esteban Gutierrez < > > este...@cloudera.com > > > > >wrote: > > > > > > > > > Hello Aij, > > > > > > > > > > Snapshots are the suggested method since HBase 0.94.6, they provide > > > > better > > > > > consistency for backing up data in HBase. You can find more > > information > > > > in > > > > > the HBase Book here: > > > > > > > > > > https://hbase.apache.org/book.html#ops.snapshots > > > > > > > > > > Depending on your use case and resources you might want to consider > > > > > replication as well: > > > > > > > > > > http://hbase.apache.org/replication.html > > > > > > > > > > cheers, > > > > > esteban. > > > > > > > > > > > > > > > -- > > > > > Cloudera, Inc. > > > > > > > > > > > > > > > > > > > > On Tue, Apr 1, 2014 at 10:56 PM, R W <aijw...@gmail.com> wrote: > > > > > > > > > > > Hi Guys > > > > > > > > > > > > I'm using hbase org.apache.hadoop.hbase.mapreduce.Export > > > > > > / org.apache.hadoop.hbase.mapreduce.Import to backup and restore > > > HBase > > > > > > data, at least it's good to me, i would like to know if there are > > any > > > > > > better solutions or practices on how to backup HBase data, that > > will > > > be > > > > > > really helpful for us, thanks. > > > > > > > > > > > > Cheers > > > > > > aij > > > > > > > > > > > > > > > > > > > > >
