Bug 1291165

Summary: [RFE] backup mode for a domain (temporarily disallow running VMs from a specific domain, as it's being backed up)
Product: [oVirt] ovirt-engine Reporter: Allon Mureinik <amureini>
Component: RFEsAssignee: Shubbham Dubey <sdubey504>
Status: CLOSED CURRENTRELEASE QA Contact: Elad <ebenahar>
Severity: medium Docs Contact:
Priority: low    
Version: 4.0.0CC: amureini, bugs, mkalinin, mlipchuk, ratamir, sabose, sasundar, sdubey504, ylavi
Target Milestone: ovirt-4.2.1Keywords: FutureFeature
Target Release: ---Flags: rule-engine: ovirt-4.2+
ratamir: testing_plan_complete?
ylavi: planning_ack+
amureini: devel_ack+
ratamir: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Feature: Configuring a storage domain as backup storage domain, so user can backup VMs and Templates while the storage domain is attached to oVirt Reason: Export storage domain is a dedicated storage domain which is used to store and restore VMs and Templates. The drawback of Export storage domain is its two stage process. Transferring a VM required first copying it into the export storage domain and then into other storage domain to start using them. Since in background transfer from one domain to other take place using normal copy or dd utility (in case of disks) this process take a large time for a complete transfer. Result: For a better backup experience we decided to create a whole dedicated storage domain to be used only for backup which obviously will call as backup storage domain.
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-22 10:00:47 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: 1502559, 1541769    
Bug Blocks: 1291168, 1411323, 1508270, 1548850    

Description Allon Mureinik 2015-12-14 08:22:15 UTC
Description of problem:
With the ability to attach/detach a data domain, it can virtually replace an export domain.

The missing piece is a "backup-mode" flag to allow the user to prevent running VMs on the copies he intends for a backup.

Comment 1 Allon Mureinik 2017-06-12 07:47:31 UTC
Actually, this is being worked on as part of oVirt's participation in GSOC.

Comment 2 Yaniv Lavi 2017-08-13 11:04:21 UTC
A nice follow up would be to allow to attach this domain a number of DCs and RHV managers to enable easier template sharing with OVA/templates. Should we open an RFE for this?

Comment 3 Allon Mureinik 2017-08-13 11:31:47 UTC
(In reply to Yaniv Lavi (Dary) from comment #2)
> A nice follow up would be to allow to attach this domain a number of DCs and
> RHV managers to enable easier template sharing with OVA/templates. Should we
> open an RFE for this?

I'd like to point out that this isn't *that* easy.
Nothing in this feature changes the locking implementation, so there's quite a bit of extra work to add the improvement you're requesting. Let's have a separate RFE for it so we can design/scope/prioritize there.

Comment 7 Maor 2017-10-15 08:42:59 UTC
Shubham,

Can you please open a separate bug for the fix in https://gerrit.ovirt.org/#/c/81290/
and block this bug on the new opened bug.
I think that once that will be done we can move this bug to ON_QA

Comment 8 Raz Tamir 2017-10-15 08:46:22 UTC
Maor,

Can you please provide more information about this RFE?
Is there any feature page for it?

Comment 9 Maor 2017-10-15 09:17:50 UTC
You can take a look at the feature page here:
https://github.com/oVirt/ovirt-site/pull/1003

Comment 10 Elad 2018-02-19 12:33:04 UTC
Feature functionality works properly, the following operations are blocked:
- VM start, with an attached disk on a backup domain 
- Setting a domain to backup while it has disks attached to running VMs
- Live storage migration to a backup domain (as bug #1541769 is now fixed and verified)


Used:
rhvm-4.2.2-0.1.el7.noarch

Comment 11 Sandro Bonazzola 2018-02-22 10:00:47 UTC
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.1 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.