The replication.html reference appears to contain a reference to a bug (2611) which was solved two years ago :)
On Wed, Mar 6, 2013 at 12:15 AM, Damien Hardy <[email protected]> wrote: > IMO the easier would be hbase export. For long term offline backup (for > disaster recovery). It can even be stored on a different hdfs storage than > the one used by hbase using a full hdfs:// url as destination directory. > Le 5 mars 2013 22:52, "Leonid Fedotov" <[email protected]> a écrit > : > > > Rita, > > it seems like replication will be the best option for you. > > Take a look on this doc: > > http://hbase.apache.org/replication.html > > > > Thank you! > > > > Sincerely, > > Leonid Fedotov > > On Mar 4, 2013, at 4:18 PM, Rita wrote: > > > > > the end goal is to have a backup of our hbase tables. > > > > > > > > > On Mon, Mar 4, 2013 at 7:10 AM, Kevin O'dell <[email protected] > > >wrote: > > > > > >> DistCP is typically used for HDFS level back up jobs. It can be used > > for > > >> HBase but can be quite tricky. I would recommend using Export, > > CopyTable, > > >> or Replication. These are tools designed for HBase backup. What is > the > > >> end goal? > > >> > > >> On Mon, Mar 4, 2013 at 7:00 AM, Manish Bhoge < > > [email protected]>wrote: > > >> > > >>> Export and distcp has different application. Use discp when you need > to > > >>> move data across clusters. Do you want to export table data outside > > your > > >>> cluster? If not then export table is better. > > >>> > > >>> Sent from HTC via Rocket! excuse typo. > > >>> > > >>> > > >> > > >> > > >> -- > > >> Kevin O'Dell > > >> Customer Operations Engineer, Cloudera > > >> > > > > > > > > > > > > -- > > > --- Get your facts first, then you can distort them as you please.-- > > > > >
