virtnbdbackup | Backup utility for Libvirt / qemu / kvm | Continuous Backup library

by abbbi Python Version: v1.9.26 License: GPL-3.0

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

kandi X-RAY | virtnbdbackup Summary

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

Existing backup solutions or scripts for libvirt/kvm usually depend on the external snapshot feature to create backups, sometimes even require to shutdown or pause the virtual machine. Recent additions to both the libvirt and qemu projects have introduced new capabilities that allow to create online (full and incremental) backups, by using so called dirty bitmaps (or changed block tracking). virtnbdbackup uses these features to create online full and incremental or differencial backups. virtnbdrestore can be used to re-construct the complete image from the thin provisioned backups. virtnbdmap can be used to map an thin provisioned backup image into a block device on-the-fly, for easy single file restore or even instant boot from an backup image.

Support

Quality

Security

License

Reuse

Support

virtnbdbackup has a low active ecosystem.

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

It had no major release in the last 12 months.

There are 7 open issues and 88 have been closed. On average issues are closed in 1 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of virtnbdbackup is v1.9.26

Quality

virtnbdbackup has 1 bugs (0 blocker, 0 critical, 0 major, 1 minor) and 223 code smells.

Security

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

virtnbdbackup code analysis shows 0 unresolved vulnerabilities.

There are 3 security hotspots that need review.

License

virtnbdbackup is licensed under the GPL-3.0 License. This license is Strong Copyleft.

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

Reuse

virtnbdbackup releases are available to install and integrate.

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

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

It has 1922 lines of code, 86 functions and 27 files.

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

Top functions reviewed by kandi - BETA

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

Start a remote remote backup
Execute a remote command
Add TLS credentials
Returns the name of the tf1
Start a backup job
Indent an XML node
Create the domainbackup XML
Returns a list of domain disks
Get the list of files from the disk
Get the domain settings
Start a qemu - nbd server
Check if this node has incremental backups enabled
Configure the logger
Returns the list of extent objects in the network
Create a qemu - img
Backup the checkpoint
Wait for NBD server to connect to the NBD server
Remove excluded disks from a domain config
Start a remote Nbd server
Read a chunk of data from an nbd file
Adjust the domain name from vm config
Refine the checkpoint list
Connect to libvirt
Write a single block to the writer
Start Nbdkit process
Remove all checkpoint files from persistent storage

Get all kandi verified functions for this library.

virtnbdbackup Key Features

No Key Features are available at this moment for virtnbdbackup.

virtnbdbackup Examples and Code Snippets

Backup Examples

Python

Lines of Code : 17

License : Strong Copyleft (GPL-3.0)

Copy

virtnbdbackup -d vm1 -l full -o /tmp/backupset

virtnbdbackup -d vm1 -l inc -o /tmp/backupset

/tmp/backupset/
├── backup.full.05102021161752.log
├── backup.inc.05102021161813.log
├── backup.inc.05102021161814.log
├── checkpoints
│   ├── vi

Backup concurrency,Pipe data to other hosts

Python

Lines of Code : 13

License : Strong Copyleft (GPL-3.0)

Copy

 # mkdir backup-weekly; cd backup-weekly
 # virtnbdbackup -d vm1 -l full -o - | ssh root@remotehost 'cat > backup-full.zip'
 # [..]
 # INFO outputhelper - __init__: Writing zip file stream to stdout
 # [..]
 # INFO virtnbdbackup - main: Finished

Restore examples,Dumping backup information

Python

Lines of Code : 11

License : Strong Copyleft (GPL-3.0)

Copy

virtnbdrestore -i /tmp/backupset/ -a dump -o /tmp/restore 
INFO:root:Dumping saveset meta information
{'checkpointName': 'virtnbdbackup',
 'dataSize': 704643072,
 'date': '2020-11-15T20:50:36.448938',
 'diskName': 'sda',
 'incremental': False,
 'pare

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 virtnbdbackup

You can download it from GitHub.
You can use virtnbdbackup like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.

Support

libvirt/qemu supports dirty bitmaps, required for incremental backups only with qcow(v3) based disk images. If you are using older image versions, you can only create copy backups, or consider converting the images to a newer format using qemu-img. By default virtnbdbackup will exclude all disks with format raw. This behavior can be changed if option --raw is specified, raw disks will then be included during a full backup. This of course means that no thin provisioned backup is created for these particular disks. During restore, these files can be copied "as is" from the backup folder and must not be processed using virtnbdrestore.

Find more information at: