Improved Backup Interface

[rsmontero]

Description
Improve Backup interface to add additional functionality including:

• Retention time. How long or how many backups are kept. Automatically clean older backups
• Adapt restore interface to manage multiple backups
• Adapt one-shot backups to add a new entry in the backup list
• Add a new quota to limit the number of backups or number of VMs with backups
• Adapt Sunstone interface to previous modifications
• Allow backups to be performed live if possible (e.g. configurable per VM or hypervisor)

Use case
Improve backup experience

Interface Changes
VM metadata needs to be changed to accommodate more backups. Possible new Quota. Possible new API operations.

Additional Context
NaN

Progress Status

• Branch created
• Code committed to development branch
• Testing - QA
• Documentation
• Release notes - resolved issues, compatibility, known issues
• Code committed to upstream release/hotfix branches
• Documentation committed to upstream release/hotfix branches

[rene-bayer]

Further improvements:

• It should be possible, that a user can configure and control the backup on its own
• add the possibility to do "dirty" backups (don't poweroff the vm for snapshoting)

[abbbi]

Please think about third party backup vendors,.. It would be really good to have sort of an backup API available that could be used by external software components to create off-site backups, store them on Tape, etc. Recent Libvirt/QEMU versions already support incremental backup via NBD. RHEV and other HV solutions already provide an API interface for third party vendors.

[atodorov-storpool]

👍 second to both additions
Also, the "backend" (a.k.a. the private marketplace) drivers should be opened for external drivers too. The current three ones are hard-coded on too many places leading to difficult if not impossible to create an additional one.

[loizo-hk]

Off-site backup is very important for our Disaster Recovery plan.

We are working on pull mod, the backup server gets the data from the production server. If our production server is infected by a ransomware or hacked or destroyed, we absolutely need to keep it back alive quickly from a trusted source. The private marketplace is not sufficient for us.

A real backup interface with snapshot date and a local dedicated datastore with all the vm information (name / id / disk / xml files) and the possibility to decide if we want a full or incremental backup and the retention delay (every day snapshot + weekly full backup or blockcommit for example) could be really great.

And please the most important thing allow us to use a datastore and not only the private marketplace.

[FrederickBor]

Sunstone PRs:

• Code:

  • https://github.com/OpenNebula/one-ee/pull/2313
  • https://github.com/OpenNebula/one-ee/pull/2317
  • https://github.com/OpenNebula/one-ee/pull/2325
  • https://github.com/OpenNebula/one-ee/pull/2330
  • https://github.com/OpenNebula/one-ee/pull/2337
  • https://github.com/OpenNebula/one-ee/pull/2341
  • https://github.com/OpenNebula/one-ee/pull/2346
  • https://github.com/OpenNebula/one-ee/pull/2347
  • https://github.com/OpenNebula/one-ee/pull/2348
  • https://github.com/OpenNebula/one-ee/pull/2353
  • https://github.com/OpenNebula/one-ee/pull/2355
  • https://github.com/OpenNebula/one-ee/pull/2371
  • https://github.com/OpenNebula/one-ee/pull/2391

• Test: https://github.com/OpenNebula/development/pull/2148

[abbbi]

hi,

is there any documentation available on how to use the new API as a third party backup vendor? Thanks

[dann1]

hi,

is there any documentation available on how to use the new API as a third party backup vendor? Thanks

You can take a look at the backup driver devel documentation and create your own driver considering the arguments and the outputs.