Skip to content

NAS Backup: Incremental backups support #685

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
abh1sar wants to merge 1 commit into
base: 4.22
Choose a base branch
from
Open

NAS Backup: Incremental backups support #685

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 24 additions & 2 deletions source/adminguide/nas_plugin.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,10 +27,12 @@ instances to any shared storage (NAS). It is based on `libvirt push backup mode
to take full instance backups (qcow2) and requires libvirt-7.2.0 and QEMU-4.2,
or high versions on the KVM hosts.

Currently, only backup of VMs from the NFS, CEPH, File-based Shared Mountpoint
Currently, only backup of VMs from the NFS, CEPH, Linstor, File-based Shared Mountpoint
and Local Storage based Primary Storage are tested to work. All other Primary Storages
are not tested, backups on them may not work.

Since ACS 4.22, **Incremental Backups** are supported on NFS, Shared Mountpoint and Local Storage.

The NAS B&R plugin requires admin to first add backup repositories which are
network-attached storage (shared storage). It supports NFS, CIFS/Samba and CephFS.

Expand Down Expand Up @@ -99,6 +101,26 @@ For the "External ID", please specify the name of the previously created backup

After this has been done, you can go to any Instance view and there will be buttons available for either ad-hoc backup or a scheduled backup of the VM

Incremental Backups
--------------------
Incremental Backups work by using libvirt checkpoints and qcow2 bitmaps to track and backup only the changed blocks since the last backup. The backup chain is flattened out and copied during restore.

Some caveats:

* Supported only on NFS, Shared Moutpoint and Local Storage.
* Stopped VM backups are always full.
* Backup after VM migration is full.
* Backup after restore is full.

Use these settings to configure incremental Backups:

================================= ========================
Configuration Value
================================= ========================
nas.backup.incremental.enabled true (default false)
nas.backup.full.every (default 10)
================================= ========================

Quiesce (Filesystem Freeze and Thaw)
------------------------------------

Expand Down Expand Up @@ -144,7 +166,7 @@ For stopped instances, `qemu-img` is used to convert and export full-disk backup
in qcow2 format to the backup repository.

For restore operations, the KVM instance must be stopped in CloudStack.
Currently, only volume(s) restoration is supported only to NFS, CEPH, File-based Shared Mountpoint
Currently, only volume(s) restoration is supported only to NFS, CEPH, Linstor, File-based Shared Mountpoint
and Local Storage based primary storage pools, and restored volumes are fully backed disks (i.e.
not using any backing template file).

Expand Down
Loading