Could you please clarify, what would be the process of making backup of a running VM to an
existing backup storage domain?
I’m asking because it looks like the process is going to be quite the same:
1. Clone VM from a snapshot
2. Move the cloned VM to a backup storage domain
An ability of choosing destination storage for cloned VMs would increase backup
efficiency. On the other hand, an ability of exporting VM from a snapshot would increase
the efficiency in the same way even without creating new entity.
Indeed, Backup SDs would increase efficiency of disaster recovery. But the same would be
achieved by converting Export SDs to Data SDs using a small CLI utility.
On 01/10/2017, 15:32, "users-bounces(a)ovirt.org on behalf of Maor Lipchuk"
<users-bounces(a)ovirt.org on behalf of mlipchuk(a)redhat.com> wrote:
On Sun, Oct 1, 2017 at 2:50 PM, Nir Soffer <nsoffer(a)redhat.com> wrote:
Attaching and detaching data domain was not designed for backing up vms.
How would you use it for backup?
How do you ensure that a backup clone of a vm is not started by mistake,
changing the backup contents?
That is a good question.
We recently introduced a new feature called "backup storage domain"
which you can mark the storage domain as backup storage domain.
That can guarantee that no VMs will run with disks/leases reside on
the storage domain.
The feature should already exist in oVirt 4.2 (despite a bug that
should be handled with this patch https://gerrit.ovirt.org/#/c/81290/
You can find more information on this here:
Basically the OVF that is being saved in the export domain should be
similar to the same one that is being saved in the OVF_STORE disk in
the storage domain.
If the user manages replication on that storage domain it can be
re-used for backup purposes by importing it to a setup.
Actually it is much more efficient to use a data storage domain than
to use the copy operation to/from the export storage domain.
Users mailing list