On Tue, Feb 7, 2017 at 6:05 PM, Beckman, Daniel < Daniel.Beckman@ingramcontent.com> wrote:
We’re been using oVirtBackup with our oVirt 4.0.5 environment and it’s worked well. It’s not the most efficient ( first creates a snapshot, then clone, then backup) but we can live with it.
Has anyone tested oVirtBackup with oVirt 4.1? Does it still work? I want to know before we upgrade. I’d like to eventually use the new v4 API but I haven’t seen a lot of documentation on how it works in practice.
Thanks,
Daniel
*From: *<users-bounces@ovirt.org> on behalf of Nathanaël Blanchet < blanchet@abes.fr> *Date: *Monday, January 30, 2017 at 3:44 AM *To: *"users@ovirt.org" <users@ovirt.org> *Subject: *Re: [ovirt-users] oVirt VM backup and restore
Hello,
- With ovirt <= 4.1 and ovirtsdk3 : https://github.com/wefixit-AT/ oVirtBackup
This workflow works fine but will be soon deprecated.
- With ovirt > 4.0, jhernandez has recently posted a new python script based on the new v4 API : https://github.com/oVirt/ ovirt-engine-sdk/blob/master/sdk/examples/vm_backup.py <https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/vm_backup.py>
I personnally didn't try it, maybe someone could give a feedback.
I'm running some tests in a 4.1 testenvironment. At the moment testing on a Oracle Linux 7.3 VM - using oVirtBackup from master (version is on 3rd of July 2016) $ ./backup.py -c config_test.cfg Mar 08 17:37:08: Start backup for: Oracle7 Mar 08 17:37:09: Snapshot creation started ... Mar 08 17:38:23: Snapshot created Mar 08 17:38:33: Clone into VM started ... Mar 08 17:40:31: Cloning finished Mar 08 17:40:32: Snapshot deletion started ... Mar 08 17:41:53: Snapshots deleted Mar 08 17:41:54: Export started ... Mar 08 17:43:56: Exporting finished Mar 08 17:43:57: Delete cloned VM started ... Mar 08 17:44:01: Cloned VM deleted Mar 08 17:44:01: Duration: 6:54 minutes Mar 08 17:44:01: VM exported as Oracle7_BACKUP_20170308_173708 Mar 08 17:44:01: Backup done for: Oracle7 Mar 08 17:44:01: All backups done NOTE: during the snapshot creation I see in web admin console the VM in paused state and also not responsive in both console and ssh session. After a couple of seconds it comes back and as a confirmation I see this in its messages: Mar 8 17:38:57 T-ORACLE73 chronyd[616]: System clock wrong by 19.077230 seconds, adjustment started Is this expected? Not yet used the vm_backup.py, I;m trying to get sdk4 on Fedora 25 before (see the other thread I opened)... Gianluca