Bug 1063843 - Unable to backup memory as part of Backup-Restore API
Summary: Unable to backup memory as part of Backup-Restore API
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: General
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Maor
QA Contact: Elad
URL:
Whiteboard:
Depends On: 1150239
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-11 14:06 UTC by Arik
Modified: 2022-03-25 14:20 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-02 08:09:12 UTC
oVirt Team: Storage
Embargoed:
sbonazzo: ovirt-4.3-

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-45450 0 None None None 2022-03-25 14:20:35 UTC

Description Arik 2014-02-11 14:06:10 UTC 
Description of problem:
Backup-Restore API allows us to back up & restore VM, but it backs up only the disks, there is no way to back up the memory that is saved as part of the Snapshot that was created for the backup. So it is impossible to backup VM and start it again with the exact same state it had when it is restored.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
Cannot back up VM using the Backup-Restore API and start it with the exact same state it had in the moment the backup snapshot was taken, after the VM is restored

Expected results:
It might be useful to be able to start the VM with the exact same state it had at the moment the backup snapshot was taken, after the VM is restored using the Backup-Restore API

Additional info:
Comment 1 Itamar Heim 2014-02-16 08:23:11 UTC 
Setting target release to current version for consideration and review. please
do not push non-RFE bugs to an undefined target release to make sure bugs are
reviewed for relevancy, fix, closure, etc.
Comment 2 Allon Mureinik 2014-12-29 08:21:26 UTC 
We need a proper way to treat memory volumes first.
Once the RFE described in bug 1150239 is handled, this should be revisited.
Comment 3 Allon Mureinik 2015-07-07 11:15:20 UTC 
Pushing out to 4.0.0, as we depend on bug 1150239.
Comment 4 Sandro Bonazzola 2015-09-04 08:58:23 UTC 
This is an automated message.
This Bugzilla report has been opened on a version which is not maintained anymore.
Please check if this bug is still relevant in oVirt 3.5.4.
If it's not relevant anymore, please close it (you may use EOL or CURRENT RELEASE resolution)
If it's an RFE please update the version to 4.0 if still relevant.
Comment 5 Sandro Bonazzola 2015-10-02 11:05:12 UTC 
This is an automated message.
This Bugzilla report has been opened on a version which is not maintained
anymore.
Please check if this bug is still relevant in oVirt 3.5.4 and reopen if still
an issue.
Comment 6 Allon Mureinik 2015-10-06 13:29:36 UTC 
Still a requirement.
Comment 7 Red Hat Bugzilla Rules Engine 2015-10-19 11:02:20 UTC 
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Comment 8 Yaniv Lavi 2017-02-07 15:12:03 UTC 
Can this be done with memory disk modeling in 4.0?
Comment 9 Arik 2017-02-08 13:08:51 UTC 
(In reply to Yaniv Dary from comment #8)
> Can this be done with memory disk modeling in 4.0?

Yes
Comment 10 Tal Nisan 2018-07-02 08:09:12 UTC 
Closing old bugs, please reopen if still needed, in any case patches are welcome.
Note You need to log in before you can comment on or make changes to this bug.