VmBackup | XenServer simple backup script | Continuous Backup library

by NAUbackup Python Version: Current License: No License

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

kandi X-RAY | VmBackup Summary

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

Copyright (C) 2019 Northern Arizona University. Title: NAUbackup / VmBackup - a XenServer vm-export and vdi-export Backup Script. Package Contents: README.md (this file), VmBackup.py, example.cfg.

Support

Quality

Security

License

Reuse

Support

VmBackup has a low active ecosystem.

It has 220 star(s) with 61 fork(s). There are 34 watchers for this library.

It had no major release in the last 6 months.

There are 29 open issues and 52 have been closed. On average issues are closed in 97 days. There are 4 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of VmBackup is current.

Quality

VmBackup has 0 bugs and 152 code smells.

Security

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

VmBackup code analysis shows 0 unresolved vulnerabilities.

There are 2 security hotspots that need review.

License

VmBackup 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

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

VmBackup 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.

VmBackup saves you 469 person hours of effort in developing the same functionality from scratch.

It has 1106 lines of code, 53 functions and 1 files.

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

Top functions reviewed by kandi - BETA

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

Run vmBackup .
Gather VM metadata .
Removes duplicates from duplicate entries .
Send an email .
Save key and value to config file .
Generate usage config file .
Check if configuration is valid .
Add vms to exclude list
Print configuration information .
Print usage examples .

Get all kandi verified functions for this library.

VmBackup Key Features

No Key Features are available at this moment for VmBackup.

VmBackup Examples and Code Snippets

No Code Snippets are available at this moment for VmBackup.

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 VmBackup

VmBackup will require lots of file storage. Set up a storage server with an exported VM backup share. By default VmBackup.py uses /snapshots, which can be modified. Frequently NFS is used for the storage server, with many installation and configuration sources available on the web. An optional SMB/CIFS method can be enabled through comments in the script.
For all of the XenServers in a given pool, mount the new /snapshots share.
Finish creating a share directory structure that meets your needs. Here are the VmBackup.py default subdirectories which can be changed: /snapshots/BACKUPS - this is for all VM backups /snapshots/NAUbackup - this is for the VmBackup.py script, any config files, and the status.log summary file. /snapshots/NAUbackup/logs - this is for redirecting your cronjob VmBackup.py output.
Download VmBackup.py, example.cfg, README.md to your execution location, such as /snapshots/NAUbackup
Inspect and customize the comments in page one of the VmBackup.py code. Here are some of the changes you may want to configure:
Find text HARD CODED DEFAULTS - these values are in effect anytime you run VmBackup.py with a command line vm-selector. Many of these code defaults can also be overridden in the config-file.
Find text OPTIONAL - if you want an automatic email to be sent at end of VmBackup then follow the instructions for the label MAIL_ENABLE.
Install the XenServer Software Development Kit from www.citrix.com/downloads - download the XenServer and copy file XenAPI.py into the same directory where VmBackup.py exists. To verfy XenApi, execute VmBackup with a valid password and some simple vm-name. Example: ./VmBackup.py password vm-name preview Note: if password has any special characters, then escape with back slash: ./VmBackup.py pass$word vm-name
Follow some VmBackup usage examples in the next section and try some examples with your VMs. Initially use the preview option, followed by a non-preview execution to actually see the VM export process. If you have a test XenServer environment, then utilize this for test verification. Note that if multiple definitions of VMs and/or VDIs are put into the configuration file, the last valid definition will take precedence over any earlier detected definitions. In addition, excludes will take precedence over any backup definitions.
VM Recovery testing is an important part of the setup, see later section. Become familiar with the /snapshots/BACKUPS/vm-name directory structure and file contents, also in later section. After backing up some VMs then restore them on a test system and verify VM functionality.
Plan your backup strategy, such as weekly, bi-monthly, monthly frequencies. How many copies of each backup do you want to keep? How long do your backup configurations take to execute and does this fit in with your XenServer processing priorities?
Execute your plan which typically involves setting up a XenServer crontab schedule, see later section.

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: