Bug 1005554

Summary:	backup/restore to support legacy backup
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Alon Bar-Lev <alonbl>
Component:	ovirt-engine-setup	Assignee:	Yedidyah Bar David <didi>
Status:	CLOSED WONTFIX	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	acathrow, bazulay, emesika, iheim, istein, Rhev-m-bugs, yeylon
Target Milestone:	---	Keywords:	Triaged
Target Release:	3.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	integration
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-10-20 14:22:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Alon Bar-Lev 2013-09-08 10:23:39 UTC

ovirt-engine-3.3 introduces formal utility for backup/restore, engine-backup.

This utility should be used as an interface for users to perform all backup/restore activities.

There is a requirement to restore previous version database into current version. If that requirement is valid, the engine-backup utility should support that mode of operation.

One problem is that the legacy backup file contains database creation commands, while in engine-3.3 we expect to restore into existing database.

First we should understand why restoring previous minor backup is required, for that we need PM.

Comment 1 Alon Bar-Lev 2013-09-08 10:25:53 UTC

Hello Andrew,

Is there a requirement to restore 3.2 backup into 3.3 environment?

Won't it better to install 3.2, restore database and then upgrade?

Thanks,
Alon

Comment 2 Andrew Cathrow 2013-10-20 14:22:23 UTC

(In reply to Alon Bar-Lev from comment #1)
> Hello Andrew,
> 
> Is there a requirement to restore 3.2 backup into 3.3 environment?
> 
> Won't it better to install 3.2, restore database and then upgrade?
> 
> Thanks,
> Alon

Agree, closing