rdiff-backup | Reverse differential backup tool , over a network | Continuous Backup library

by rdiff-backup Python Version: 2.4.0 License: GPL-2.0

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

kandi X-RAY | rdiff-backup Summary

rdiff-backup is a Python library typically used in Backup Recovery, Continuous Backup applications. rdiff-backup has no bugs, it has no vulnerabilities, it has build file available, it has a Strong Copyleft License and it has high support. You can install using 'pip install rdiff-backup' or download it from GitHub, PyPI.

website . docs . community.

Support

Quality

Security

License

Reuse

Support

rdiff-backup has a highly active ecosystem.

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

There were 3 major release(s) in the last 12 months.

There are 62 open issues and 348 have been closed. On average issues are closed in 94 days. There are no pull requests.

It has a negative sentiment in the developer community.

The latest version of rdiff-backup is 2.4.0

Quality

rdiff-backup has 0 bugs and 0 code smells.

Security

rdiff-backup has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

rdiff-backup code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

rdiff-backup is licensed under the GPL-2.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

rdiff-backup releases are available to install and integrate.

Deployable package is available in PyPI.

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

Installation instructions, examples and code snippets are available.

rdiff-backup saves you 7753 person hours of effort in developing the same functionality from scratch.

It has 21817 lines of code, 1899 functions and 123 files.

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

Top functions reviewed by kandi - BETA

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

Validate the remote connection
Validate API version
Return a str
Main entry point for rdiff - backups
Parse commandline options
Returns the topFS subtree of the tree
Prints a listing of topFS files
Set security level
Get the directory of this repository
Get mirror rp
Setup the repository
Convert an object to a string
Parse a location
Generate a time from a string
Generate rdiff pairs
Detect the win32 ACLs on the given directory
Remove file from repos
Get diffs
Get diffs for diffs
Verify a mirror repository
Parse command line options
Write the ACL to the given rp
Detect the case sensitive file system under rp
Determine whether to test EAS
Determine if the repo needs to be regressor
Collate multiple iterators

Get all kandi verified functions for this library.

rdiff-backup Key Features

No Key Features are available at this moment for rdiff-backup.

rdiff-backup Examples and Code Snippets

No Code Snippets are available at this moment for rdiff-backup.

Community Discussions

Trending Discussions on rdiff-backup

Bash Script - If always printing else

Rsync ignores folders ending in slashes

How to write process ID and get exit code of the next to last command

QUESTION

Bash Script - If always printing else

Asked 2018-Aug-03 at 17:11

I'm trying to make a script in bash to check if my rdiff-backup has run today, but my second if is not working.

...

ANSWER

Answered 2018-Aug-03 at 17:11

The problem is that your variable contains the date in addition to the exit code.

You can either get rid of the grep output with grep -q:

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

QUESTION

Rsync ignores folders ending in slashes

Asked 2018-Jun-27 at 08:29

I have this following content in a file named "/rsync/include.txt"

...

ANSWER

Answered 2018-Jun-27 at 08:29

General debugging info

The easiest way to see if your filter rules do what you want, is to use -vv (increase verbosity twice) in combination with -n (dry-run).

With double verbosity you will see which pattern caused which file to be ignored. You may grep the output to only see the relevant parts.

Example

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

QUESTION

How to write process ID and get exit code of the next to last command

Asked 2018-Mar-07 at 05:39

I want to run a command, write the process id instantly to a file when the command started and afterwards get the exit status of the command. This means, while the process id has to be written instantly, I want the exit status only when the initial command has finished.

The following statement will unfortunately run the command, write the process id instantly but it won't wait for the command to be finished. Furthermore I will only get the exit status of the echo command, not of the initial command

command in my case is rdiff-backup.

How do I need to modify the statement?

...

ANSWER

Answered 2017-Feb-01 at 19:56

You need to wait on the background process to get its exit status:

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

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

Vulnerabilities

No vulnerabilities reported

Install rdiff-backup

In older Linux distributions the rdiff-backup versions are of the 1.x series, which is not recommended for new installs anymore. Follow the instructions below to install the latest 2.x release of rdiff-backup.

Support

If you have everything installed properly, and it still doesn’t work, see the enclosed FAQ, the rdiff-backup web page and/or the rdiff-backup-users mailing list. We’re also happy to help if you create an issue to our GitHub repo. The most important is probably to explain what happened with which version of rdiff-backup, with which command parameters on which operating system version, and attach the output of rdiff-backup run with the very verbose option -v9. The FAQ in particular is an important reference, especially if you are using smbfs/CIFS, Windows, or have compiled by hand on Mac OS X.

Find more information at: