Proxmox-Encrypted-Remote-Backup | Encrypt and upload Proxmox VM backups to rclone remotes | Continuous Backup library

by farthinder Python Version: Current License: Apache-2.0

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

kandi X-RAY | Proxmox-Encrypted-Remote-Backup Summary

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

Proxmox Encrypted Remote Backup (PERB) is a vzdump hook script written in Python. Once the Backup job has finished successfully the script gathers the backed up files (.vma and .log) and puts them in encrypted tar files and then uploads it to an rclone remote destination (currently Google Drive is tested and supported).

Support

Quality

Security

License

Reuse

Support

Proxmox-Encrypted-Remote-Backup has a low active ecosystem.

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

It had no major release in the last 6 months.

There are 2 open issues and 3 have been closed. On average issues are closed in 186 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of Proxmox-Encrypted-Remote-Backup is current.

Quality

Proxmox-Encrypted-Remote-Backup has 0 bugs and 86 code smells.

Security

Proxmox-Encrypted-Remote-Backup has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

Proxmox-Encrypted-Remote-Backup code analysis shows 0 unresolved vulnerabilities.

There are 1 security hotspots that need review.

License

Proxmox-Encrypted-Remote-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

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

Proxmox-Encrypted-Remote-Backup 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.

It has 510 lines of code, 17 functions and 5 files.

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

Top functions reviewed by kandi - BETA

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

Encrypt and uploads files
Encrypt files
Transfer a single file to remote root
Verify the uploaded file
Checks if gpg source is installed
Encrypt files using GPGEncrypt
Uploads file to remote root
Removes old backups from the job folder
Delete old files older than tcl
Return a list of files from the given phase
Get the old jobinfo from the job file

Get all kandi verified functions for this library.

Proxmox-Encrypted-Remote-Backup Key Features

No Key Features are available at this moment for Proxmox-Encrypted-Remote-Backup.

Proxmox-Encrypted-Remote-Backup Examples and Code Snippets

No Code Snippets are available at this moment for Proxmox-Encrypted-Remote-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 Proxmox-Encrypted-Remote-Backup

Create a folder to keep the python files: /opt/scripting/encryptedRemoteBackup/
Put the files there: GpgEncrypt.py ProxmoxEncryptedBackup.py ProxmoxEncryptedBackupSettings.py ProxmoxEventHandler.py Rclone.py
Make ProxmoxEncryptedBackup.py executable chmod o+x ProxmoxEncryptedBackup.py
Update ProxmoxEncryptedBackupSettings.py Se example file for sample settings and documentation
Edit /etc/pve/vzdump.cron Add to relevant jobs: --script /opt/scripting/encryptedRemoteBackup/ProxmoxEncryptedBackup.py
Run the backup job and check the task output and log file

Support

G Suite only allows for about 750GB upload per dayPERB is only tested with G Suite, but should function with most rclone remotes, however if they dont support MD5 hashing PERB will need to be updated to handle that.$gpgOutputDirectory should if possible not be set to the same storage as the Proxmox backup as this will severley slowdown encryption. PERB will be reading and writing to the same storage.Check the logs at $logFile and the Proxmox Tasks in the web gui.

Find more information at: