Bug 1891470

Summary: [CBT][RFE] Support cold VM incremental backup
Product: [oVirt] ovirt-engine Reporter: Eyal Shenitzky <eshenitz>
Component: BLL.StorageAssignee: Eyal Shenitzky <eshenitz>
Status: CLOSED CURRENTRELEASE QA Contact: Ilan Zuckerman <izuckerm>
Severity: high Docs Contact:
Priority: unspecified    
Version: futureCC: bugs, eshames, nsoffer, pchavva, pkrempa, sfishbai, tnisan, yuriy.khokhlov, Yury.Panchenko
Target Milestone: ovirt-4.4.5Keywords: FutureFeature
Target Release: ---Flags: pm-rhel: ovirt-4.4?
izuckerm: testing_plan_complete+
pm-rhel: planning_ack?
tnisan: devel_ack+
pm-rhel: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Feature: Support VM backup when the VM is not running Reason: Backup vendors and users should have the option to backup their VMs even when they are not running. Result: Backup of VMs that are not running is now supported, the same API that used for backup running VMs is used so it is transparent for the backup vendor or the user what is the status of the VM. The process of 'cold' backup is different, when a cold backup is taken there is no need to redefine the previous checkpoints and to create scratch disks for each disk that participate in the backup because the VM is down and there will be no writing to the disks during the backup. The backup operation is done without Libvirt. A checkpoint created in the Engine DB in the same way as for 'live' backup but in the host, there is no checkpoint creation. Instead, a new bitmap is added for each disk. The created bitmap will be exposed using the NBD server when the image will be downloaded using imageio. When the VM is started with "cold" backup checkpoints, the system will redefine the checkpoints in Libvirt. Once a 'cold' checkpoint is redefined, there is no difference between the 'cold' checkpoint and checkpoint created during live backup.
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-03-18 15:14:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1901830, 1901835, 1904486    
Bug Blocks:    

Description Eyal Shenitzky 2020-10-26 11:40:22 UTC
Description of problem:

Currently, VM backup (full/incremental) can be taken only when the VM is running.
Backup of a powered-off VM is also needed since the backup application that uses incremental backup API cannot tell what is the status of the VM when performing a backup operation.

The engine should supply the option to perform full/incremental VM backup for running and non-running VMs under the same API so it will be transparent to the backup application


Version-Release number of selected component (if applicable):
4.4.4_master

How reproducible:


Steps to Reproduce:
1. Create a VM with disks that supported incremental backup
2. Try to create a full/incremental backup to the VM while it is powered-off

Actual results:
Operation is blocked

Expected results:
Full or incremental VM backup should be allowed when using new incremental backup API

Additional info:

Comment 1 Eyal Shenitzky 2020-11-02 15:50:02 UTC
*** Bug 1892670 has been marked as a duplicate of this bug. ***

Comment 2 Ilan Zuckerman 2021-03-09 07:30:37 UTC
Verified on rhv-release-4.4.5-7-001.noarch
According the test plan:
RHEVM-27575
RHEVM-27576

Comment 3 Sandro Bonazzola 2021-03-18 15:14:38 UTC
This bugzilla is included in oVirt 4.4.5 release, published on March 18th 2021.

Since the problem described in this bug report should be resolved in oVirt 4.4.5 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.

Comment 4 Sandro Bonazzola 2021-03-22 12:55:40 UTC
This bugzilla is included in oVirt 4.4.5 release, published on March 18th 2021.

Since the problem described in this bug report should be resolved in oVirt 4.4.5 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.