Export VM directly from a snapshot about ovirtbackup HOT 11 CLOSED

wait for oVirt community response .....

from ovirtbackup.

Dear all, can you explain to me about workflow one more time please?

So, I have 500 gb local_storage. I have a vm wich is 300 gb. I have connected export NFS domain storage.

Can I do a backup or not in this case?

If see the workflow it will be like this: Create snapshot from my 300 gb vm -> Clone into VM ????? - Will it fail because I need as least 300 gb free space in my local_storage? Thank for you responce to me.

from ovirtbackup.

Yes sadly you are true. In this case it is not possible because you need 100gb more free space + a little bit more because it can be that you can't delete the snapshot. During that huge backup a lot of changes will increase the snapshot file.

Maybe it is possible to move the data from the VM to the host and share the files to the VM via NFS or Samba to the VM.

For example:
VM: Disksize: 300GB -> 50GB operating system + 250GB Data
Move the 250GB Data to the host and share it to the VM. Then you have 50GB for the VM which can be backed up with your free space of 200GB on the storage

from ovirtbackup.

Big thank for you answer to me. I was wondering if you answer to the next question:

Is it possible to add a second data storage in a local_DC, and clone a vm to the new storage? It can be like this one in config.conf: like clone_domain_storage=. If possbile.

Best regards,
Victor.

from ovirtbackup.

What you can do instead of using an export domain, is create an NFS data domain instead, and clone VMs from the snapshot directly onto it. oVirt 3.5+ allows importing/connecting data domains from other DCs if you need mobility, and the RTO will be lower because these backups can be started right away from NFS instead of going through a long import first

from ovirtbackup.

@dyasny: Thats a good idea. I will test it when I have some spare time to work on my open source projects.

from ovirtbackup.

Hi,
keep both possibilities of backup domain ( NFS-export & NFS-data ) , pls.
thx.regs.Pa.

On 10.2.2016 11:57, WeFixIT wrote:

@dyasny https://github.com/dyasny: Thats a good idea. I will test it
when I have some spare time to work on my open source projects.

—
Reply to this email directly or view it on GitHub
#7 (comment).

from ovirtbackup.

@dyasny: Where should this option be? I have oVirt 3.6 with the latest updates but I see no option to export a snapshot to a NFS data domain or any option to selection another export destination

from ovirtbackup.

When you clone a VM from snapshot, you can choose where the VM's disks will be placed. It's not export as such, it's just a cloning of a VM with the destination storage domain selected as the NFS domain where you store backups.

from ovirtbackup.

Ah, I forget to add a disk to my test VM ;-)
The only problem we get here is that the VM is displayed in the VM list.
Do you have an idea how to remove it from the list?

Now it looks we can use the temporary NFS as buffer for the main storage domain. After cloning the VM can be exported to the export domain and then removed from the temporary NFS share. Then the VM list will be clean again.

Update: How is the idea to make a template of the VM?

from ovirtbackup.

The only problem we get here is that the VM is displayed in the VM list.

Well, that's normal. I'd tag it as a backup, with date-time maybe.

Now it looks we can use the temporary NFS as buffer for the main storage domain. After cloning the
VM can be exported to the export domain and then removed from the temporary NFS share. Then
the VM list will be clean again.

You can even implement a nice staging/backup scheme this way - use the data SD as a staging location, and maybe rsync VM disks from there to a deduplicated storage. There you can utilize stuff like rsync or virt-diff to start playing with actual differential and incremental backups, libguestfs for file-level restores

Update: How is the idea to make a template of the VM?

I don't see much of a use for that, templates are, after all, intended to be stateless blobs for real machines to derive from, and backups are the very definition of statefulness

from ovirtbackup.