Back to bug 1318580

Who When What Removed Added
Yedidyah Bar David 2016-03-22 10:05:10 UTC Status NEW ASSIGNED
Sandro Bonazzola 2016-03-25 15:52:31 UTC Link ID oVirt gerrit 55046
Status ASSIGNED POST
Sat6QE Jenkins 2016-03-28 20:15:54 UTC Status POST MODIFIED
Mike McCune 2016-03-28 22:28:36 UTC Status MODIFIED POST
Pavel Stehlik 2016-04-01 09:39:11 UTC QA Contact pstehlik lsvaty
Flags testing_ack? testing_ack+
Yedidyah Bar David 2016-04-07 05:45:36 UTC CC jbelka
Moran Goldboim 2016-04-07 12:51:43 UTC CC mgoldboi
Flags planning_ack? planning_ack+
Red Hat Bugzilla Rules Engine 2016-04-07 12:51:48 UTC Flags ovirt-4.0.0? ovirt-4.0.0+
Yedidyah Bar David 2016-04-12 10:23:14 UTC CC sbonazzo
Flags needinfo?(sbonazzo)
Yedidyah Bar David 2016-04-12 11:34:48 UTC Flags needinfo?(sbonazzo)
Yedidyah Bar David 2016-04-12 13:55:37 UTC Link ID oVirt gerrit 56033
Blocks 1323201
Yedidyah Bar David 2016-04-12 13:56:01 UTC Blocks 1323201
Depends On 1323201
Yedidyah Bar David 2016-04-18 07:06:00 UTC Status POST MODIFIED
Doc Text Feature:

Allow engine-backup of version 4.0 to restore backups taken on 3.6.

Reason:

engine 4.0 does not support el6. Users that want to upgrade from 3.6 on el6 to 4.0 on el7 have to do this by backing up the engine on 3.6/el6 and restore on 4.0/el7.

Result:

Using this flow, it's possible to migrate a 3.6/el6 setup to 4.0/el7:

On the existing engine machine run:
1. engine-backup --mode=backup --file=engine-3.6.bck --log=backup.log

On a new el7 machine:
2. Install engine 4.0, including dwh if it was set up on 3.6.
3. Copy engine-3.6.bck to the el7 machine
4. engine-backup --mode=restore --file=engine-3.6.bck --log=restore.log --provision-db --no-restore-permissions
5. engine-setup

Check engine-backup documentation for other options, including using remote databases, extra grants/permissions, etc.

Notes:

1. As of writing this doc-text, Reports is not built for 4.0. If/when it will be, need to update.
2. You (doc team) probably want to add relevant material to the main docs.

See also:
https://bugzilla.redhat.com/show_bug.cgi?id=1323201
https://bugzilla.redhat.com/show_bug.cgi?id=1319457
Jiri Belka 2016-04-25 16:46:57 UTC Link ID oVirt gerrit 56272
CC didi
Flags needinfo?(didi)
Yedidyah Bar David 2016-05-01 06:50:18 UTC Flags needinfo?(didi)
Sandro Bonazzola 2016-05-02 08:05:35 UTC Depends On 1332088
Yedidyah Bar David 2016-05-03 09:21:56 UTC Blocks 1332463
Yaniv Kaul 2016-05-08 10:42:36 UTC Severity unspecified high
Lukas Svaty 2016-05-17 14:37:32 UTC Flags testing_plan_complete?
Sandro Bonazzola 2016-05-19 09:16:20 UTC Status MODIFIED ON_QA
Target Release --- 4.0.0
Target Milestone ovirt-4.0.0-alpha ovirt-4.0.0-beta
Jiri Belka 2016-06-01 09:50:28 UTC Status ON_QA VERIFIED
QA Contact lsvaty jbelka
Pavel Novotny 2016-06-01 10:13:47 UTC Flags testing_plan_complete? testing_plan_complete+
Lucy Bopf 2016-06-30 05:26:02 UTC Blocks 1351435
Sandro Bonazzola 2016-07-05 07:51:43 UTC Status VERIFIED CLOSED
Resolution --- CURRENTRELEASE
Last Closed 2016-07-05 03:51:43 UTC
Megan Lewis 2016-08-15 03:55:10 UTC CC melewis
Doc Text Feature:

Allow engine-backup of version 4.0 to restore backups taken on 3.6.

Reason:

engine 4.0 does not support el6. Users that want to upgrade from 3.6 on el6 to 4.0 on el7 have to do this by backing up the engine on 3.6/el6 and restore on 4.0/el7.

Result:

Using this flow, it's possible to migrate a 3.6/el6 setup to 4.0/el7:

On the existing engine machine run:
1. engine-backup --mode=backup --file=engine-3.6.bck --log=backup.log

On a new el7 machine:
2. Install engine 4.0, including dwh if it was set up on 3.6.
3. Copy engine-3.6.bck to the el7 machine
4. engine-backup --mode=restore --file=engine-3.6.bck --log=restore.log --provision-db --no-restore-permissions
5. engine-setup

Check engine-backup documentation for other options, including using remote databases, extra grants/permissions, etc.

Notes:

1. As of writing this doc-text, Reports is not built for 4.0. If/when it will be, need to update.
2. You (doc team) probably want to add relevant material to the main docs.

See also:
https://bugzilla.redhat.com/show_bug.cgi?id=1323201
https://bugzilla.redhat.com/show_bug.cgi?id=1319457
With this update, Red Hat Virtualization 4.0 can now restore backups taken of Red Hat Enterprise Virtualization 3.6. Red Hat Virtualization 4.0 does not support Red Hat Enterprise Linux 6 and, previously, this meant that users could not upgrade from Red Hat Enterprise Virtualization 3.6. Now, users can back up their Red Hat Enterprise Virtualization 3.6 and restore it on Red Hat Virtualization 4.0.

To backup Red Hat Enterprise Virtualization 3.6 run, engine-backup --mode=backup --file=engine-3.6.bck --log=backup.log. Other options for engine-backup, including remote databases, can be found in the engine-backup documentation, https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.6/html-single/Administration_Guide/index.html#sect-Backing_Up_and_Restoring_the_Red_Hat_Enterprise_Virtualization_Manager

To migrate to Red Hat Virtualization 4.0, install Red Hat Virtualization 4.0 then copy engine-3.6.bck to the Red Hat Enterprise Linux machine. Run engine-backup --mode=restore --file=engine-3.6.bck --log=restore.log --provision-db --no-restore-permissions to restore the backup then run engine-setup.

Back to bug 1318580