Bug 1005554 - backup/restore to support legacy backup
Summary: backup/restore to support legacy backup
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-setup
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.3.0
Assignee: Yedidyah Bar David
QA Contact: Pavel Stehlik
URL:
Whiteboard: integration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-08 10:23 UTC by Alon Bar-Lev
Modified: 2015-09-22 13:09 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-20 14:22:23 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.