snapbtrex | small utility that keeps snapshots | Continuous Backup library

by yoshtec Python Version: Current License: BSD-2-Clause

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

kandi X-RAY | snapbtrex Summary

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

snapbtrex is a small utility that keeps snapshots of btrfs filesystems and optionally send it to a remote system. The script came originally from . This is an extended version which is capable of transferring snapshots to remote systems. You can run it regularly (for example in a small script in cron.hourly or in crontab), or once in a while, to maintain an "interesting" (see below) set of snapshots (backups). You may manually add or remove snapshots as you like, use snapbtrex.DATE_FORMAT (in GMT) as snapshot-name. It will keep at most --target-backups snapshots and ensure that --target-freespace is available on the file-system by selecting snapshots to remove. Using --keep-backups, you can ensure that at least some backups are kept, even if --target-freespace cannot be satisfied. snapbtrex will keep backups with exponentially increasing distance as you go back in time. It does this by selecting snapshots to remove as follows. The snapshots to remove is selected by "scoring" each space between snapshots, (newer, older). snapbtrex will remove the older of the two snapshots in the space that have the lowest score. The scoring mechanism integrates e^x from (now-newer) to (now-older) so, new pairs will have high value, even if they are tightly packed, while older pairs will have high value if they are far apart. Alternatively you can also keep only the latest snapshots via --keep-only-latest or set a maximum age for your snapshots with the --max-age parameter.

Support

Quality

Security

License

Reuse

Support

snapbtrex has a low active ecosystem.

It has 26 star(s) with 8 fork(s). There are 2 watchers for this library.

It had no major release in the last 6 months.

There are 0 open issues and 6 have been closed. On average issues are closed in 91 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of snapbtrex is current.

Quality

snapbtrex has 0 bugs and 0 code smells.

Security

snapbtrex has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

snapbtrex code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

snapbtrex is licensed under the BSD-2-Clause License. This license is Permissive.

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

Reuse

snapbtrex releases are not available. You will need to build from source code and install.

snapbtrex has no build file. You will be need to create the build yourself to build the component from source.

Installation instructions, examples and code snippets are available.

snapbtrex saves you 317 person hours of effort in developing the same functionality from scratch.

It has 762 lines of code, 54 functions and 1 files.

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

Top functions reviewed by kandi - BETA

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

Delete all directories in the repository
Return a timestamp
Return a sorted list of directories
Return sorted list of files in dirs
Transfer snapshots from remote host to target directory
Execute a subprocess
Link current snapshot
Trace the decorated function
Transfer snapshots from remote host to remote host
Sends snapshot to target path
Sync a single snapshot to target
Removes remote backups from remote host
Remove a snapshot from receiver
Delete all directories in target_dir
Remove a snapshot
Snapshot a subvolume
Sync a filesystem
Returns a list of remote directories
Calculate free space
List remote files
Execute a command
Unap a directory
List all directories in the directory
Return a list of directory names

Get all kandi verified functions for this library.

snapbtrex Key Features

No Key Features are available at this moment for snapbtrex.

snapbtrex Examples and Code Snippets

No Code Snippets are available at this moment for snapbtrex.

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 snapbtrex

snapbtrex uses the btrfs send and receive commands to transfer snapshots from a sending host to a receiving host via ssh. Using --ssh-port, you can specify the port on which such ssh connections will be attempted. Both hosts have to be prepared as in the setup instructions if you want to call the script via cronjob. You can always call snapbtrex as standalone script if you have appropriate rights. Specify your target host via --remote-host and the directory with the --remote-dir options. Both options have to be present. The target directory has to be located within a btrfs file system, and it has to be mounted via the root volume, or else btrfs might fail to receive snapshots.
For transfer backups with ssh within an automated script (cronjob) you have to prepare the systems with the following steps. 1. create user snapbtr on both systems. 2. generate ssh key on the sender and copy public key to receiving machine. 3. create a sudoers include file at the receiving machine (use sudo visudo).

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: