rsnapshot | Docker Container Backup Solution using rsnapshot | Continuous Deployment library

by blacklabelops-legacy Shell Version: 1.4.2 License: No License

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

kandi X-RAY | rsnapshot Summary

rsnapshot is a Shell library typically used in Devops, Continuous Deployment, Docker applications. rsnapshot has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.

This is a side-car container for creating and managing container backups using rsnapshot. This container can backup any arbitrary amount of containers and directories. Just hook up some containers and define your backup volumes. Rsnapshot is a wrapper around rsync and rsnapshot is strong when it comes to manage The rotation of daily, weekly and monthly snapshots. This image is a the base container with rsnapshot functionality dockerized and parameterized. The cron scheduled backup container can be found here: blacklabelops/rsnapshotd.

Support

Quality

Security

License

Reuse

Support

rsnapshot has a low active ecosystem.

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

It had no major release in the last 12 months.

There are 0 open issues and 4 have been closed. On average issues are closed in 115 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of rsnapshot is 1.4.2

Quality

rsnapshot has 0 bugs and 0 code smells.

Security

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

rsnapshot code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

rsnapshot does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

rsnapshot releases are available to install and integrate.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of rsnapshot

Get all kandi verified functions for this library.

rsnapshot Key Features

No Key Features are available at this moment for rsnapshot.

rsnapshot Examples and Code Snippets

No Code Snippets are available at this moment for rsnapshot.

Community Discussions

Trending Discussions on rsnapshot

btrfs send / receive on incremental folders that rotate

Hardening authorized_keys used in rsync backup

QUESTION

btrfs send / receive on incremental folders that rotate

Asked 2021-Sep-28 at 06:36

I am using incremental backups using rsnapshot combined with a custom cmd_cp and cmd_rm to make use of btrfs snapshots, this procudes multiple daily btrfs subvolumes:

...

ANSWER

Answered 2021-Sep-28 at 06:36

I solved it! I created a bash script that syncs all snapshots with a date in the name to the remote server. The date is subtracted from btrfs subvolume show.

So daily.0 can become 2021-09-20-08-44-46 on the remote.

I sync backwards. daily.30 first. daily.0 last. This way I can pass the proper parent to btrfs send. E.g.: btrfs send -p daily.30 daily.29.

If the date named snapshot exists on the remote, I check with btrfs subvolume show whether it was properly synced. If not, I delete the remote subvolume/snapshot and re-sync. If it was already synced, I will skip the sync. A proper synced subvolume/snapshot has a Received UUID and readonly flag.

After syncing I compare all snapshot names of the remote to what was just synced. The difference will deleted (thus old snapshots).

I might share the code in the future when it's all been stable for a long run. For now I hope the above information will help others!

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

QUESTION

Hardening authorized_keys used in rsync backup

Asked 2021-Jul-15 at 08:36

I'm trying to make a rootfs backup from ServerA on to ServerB.
The connection is one way and is initialized from ServerB using rsnapshot.
I have made a backup account on ServerA and enabled paswordless sudo only for rsync

What I'm trying to accomplish:

Change the authorized_keys file on ServerA, so only the rsync command can be used via ssh.

On ServerB - /etc/rsnapshot.conf is setup to run rsync with the following args:

rsync_long_args --rsync-path="sudo rsync" --delete --numeric-ids --relative --delete-excluded

I have tried the following on ServerA:

from="ServerB",command="sudo rsync *" ssh-ed25519 SSH-KEY

But rsnapshot keeps crashing and giving IO error codes for rsync.

What am I missing here?

...

ANSWER

Answered 2021-Jul-15 at 08:36

!! Problem Solved !!

Found out about rrsync --- /usr/share/doc/rsync/scripts/rrsync, copy it to wherever.

ServerA:authorized_keys --- command="sudo /usr/local/bin/rrsync -ro /backup"

Since I'm keeping a copy of the backups on ServerA, I might as well rsync from them instead of using rsnapshot on ServerB. (This was my initial idea, but it doesn't work since there are duplicate files because of links that rsnapshot creates, I ended up having rsnapshot running both on ServerA and ServerB, to save backups from ServerA to a localDir on ServerA and also make remote snapshots from ServerA to ServerB.)

Also changed the sudoers file on ServerA:

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

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

Vulnerabilities

No vulnerabilities reported

Install rsnapshot

You can download it from GitHub.

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: