HBase-Backup | Utility to backup and restore HBase tables | Continuous Backup library

by oclc Java Version: Current License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | HBase-Backup Summary

HBase-Backup is a Java library typically used in Backup Recovery, Continuous Backup applications. HBase-Backup has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub.

This backup utility is based around HBASE-4618. We took the features we liked from the documents and implemented some generic tools that would work for us. This package comes equipped with three utilities: a backup tool to get snapshots of HFiles, an import/restore tool, and a tool to frequently copy HLogs. There is a fourth tool we use, but did not develop it ourselves so we have not included it in the our package. It's WALPlayer, and it is described in HBASE-5604. WALPlayer is in the 0.94.0RC version of HBase so we back ported the code to work with HBase 0.92.1, the current version we are using. It is important to point out that these tools, like any other HBase backup options at the moment, are relatively new. We are continually testing them and looking for any issues. We encourage people looking for backup solutions to try it out and send any feedback. To get more details about these tools, please take a look at the wiki page.

Support

Quality

Security

License

Reuse

Support

HBase-Backup has a low active ecosystem.

It has 14 star(s) with 9 fork(s). There are 11 watchers for this library.

It had no major release in the last 6 months.

HBase-Backup has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of HBase-Backup is current.

Quality

HBase-Backup has 0 bugs and 0 code smells.

Security

HBase-Backup has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

HBase-Backup code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

HBase-Backup is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

HBase-Backup releases are not available. You will need to build from source code and install.

Build file is available. You can build the component from source.

HBase-Backup saves you 1047 person hours of effort in developing the same functionality from scratch.

It has 2375 lines of code, 118 functions and 10 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed HBase-Backup and discovered the below as its top functions. This is intended to give you an instant insight into HBase-Backup implemented functionality, and help decide if they suit your requirements.

Main entry point
Performs a major copy of the given HBase HBase
Method to verify the tables
Returns the command line options supported
Initialize the cluster
Checks if the given table is valid for the given table
Get a list of all tables available in this backup directory
Returns the tableinfo path
Flush a region
Returns the original path of the given file
Copy a file from source path to destination cluster
Get a list of files for the given region
Get list of files to copy
Setup mapper
Overrides the list of FileStatus objects
Initialize the reader
Read key value
Get the oldest file start time
Cleanup file
Get the root table object
Get HRegionInfo object from byte array

Get all kandi verified functions for this library.

HBase-Backup Key Features

No Key Features are available at this moment for HBase-Backup.

HBase-Backup Examples and Code Snippets

No Code Snippets are available at this moment for HBase-Backup.

Community Discussions

Trending Discussions on Continuous Backup

How to disable azure cosmos db continious backup

Consistency of Continuous backup of Azure Cosmos DB

Mongo atlas recommends cloud provider snaphots for backup - Is it effective?

QUESTION

How to disable azure cosmos db continious backup

Asked 2022-Feb-22 at 10:59

I enabled the Azure cosmos DB continuous backup for one of my Cosmos DBs.
How can I disable it? It just says you have successfully enrolled in continuous backup.

...

ANSWER

Answered 2022-Feb-22 at 10:59

I am not sure if you have seen this message in the portal when you created the account/also mentioned in the doc

"You will not be able to switch between the backup policies after the account has been created"

since you need to select either "Periodic" or "Continuous" at the creation of Cosmos Account, it becomes mandatory.

Update:

You will not see the above in portal anymore, you can Switch from "Periodic" to "Continous" on an existing account and that cannot be reverted. You can read more here.

Source https://stackoverflow.com/questions/69347197

QUESTION

Consistency of Continuous backup of Azure Cosmos DB

Asked 2021-Nov-25 at 17:15

What would be the consistency of the continuous backup of the write region if the database is using bounded staleness consistency? Will it be equivalent to strong consistent data assuming no failovers happened?

Thanks Guru

...

ANSWER

Answered 2021-Nov-25 at 17:15

Backups made from any secondary region will have data consistency defined by the guarantees provided by the consistency level chosen. In the case of strong consistency, all secondary region backups will have completely consistent data.

Bounded staleness will have data that may have stale or inconsistent data inside the defined staleness window (minimum 300 seconds or 100k writes). Outside of that staleness window the data will be consistent.

Data for the weaker consistency levels will have no guarantees for consistency from backups in secondary regions.

Source https://stackoverflow.com/questions/70099953

QUESTION

Mongo atlas recommends cloud provider snaphots for backup - Is it effective?

Asked 2020-May-19 at 10:12

MongoDB has deprecated the continuous back up of data. It has recommended using CPS (Cloud provider snapshots). As far as I understood, snapshots isn't really going to be effective compared to continuous backup coz, if system breaks, then we can only be able to restore the data till the previous snapshot which isn't gonna make the database up-to-date or close to it atleast.

Am I missing something here in my understanding?

...

ANSWER

Answered 2020-May-19 at 10:12

Cloud provider snapshots can be combined with point in time restore to give the recovery point objective you require. With oplog based restores you can get granularity of one second.

Source https://stackoverflow.com/questions/61886736

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install HBase-Backup

You can download it from GitHub.
You can use HBase-Backup like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the HBase-Backup component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: