5:49 p.m.
Hi,
Actually it's very simple as described in the docs.
Just stop the engine, make a backup, copy it over, place it back and
start it. You can do this in a several of ways.
ISO domains is which I would remove and recreate again. ISO domains
are actually dumb domains, so nothing can go wrong.
Did it some time ago because I needed more performance.
VDSM can run without the engine, it doesn't need it as the egine
monitors and does the commands, so when it's not there... VM's just
run (until you make them die yourself :))
I would give it 15-30 min/
Cheers,
Matt
2014-11-07 18:36 GMT+01:00 Daniel Helgenberger <daniel.helgenberger(a)m-box.de>:
Daniel Helgenberger
m box bewegtbild GmbH
ACKERSTR. 19 P: +49/30/2408781-22
D-10115 BERLIN F: +49/30/2408781-10
www.m-box.de
www.monkeymen.tv
Geschäftsführer: Martin Retschitzegger / Michaela Göllner
Handeslregister: Amtsgericht Charlottenburg / HRB 112767
On 07.11.2014, at 15:24, Koen Vanoppen <vanoppen.koen(a)gmail.com> wrote:
Hi,
We had a consulting partner who did the same for our company. This is his
procedure and worked great:
How to migrate ovirt management engine
Packages
Ensure you have the same packages & versions installed on the destination
hostas on the source, using 'rpm -qa | grep ovirt'. Make sure versions are
100%identical.
Default setup
Run 'engine-setup' on the destination host after installing the packages.
Use
the following configuration:
1. Backup existing configuration
2. On the source host, do:
You might want your consultant take a look on [1]...
Steps a-3d:
engine-backup mode=backup --file=~/ovirt-engine-source --log=backup.log
a. service ovirt-engine stop
b. service ovirt-engine-dwhd stop
c. mkdir ~/backup
d. tar -C /etc/pki/ovirt-engine -czpf ~/backup/ovirt-engine-pki.tar.gz .
e. tar -C /etc/ovirt-engine -czpf ~/backup/ovirt-engine-conf.tar.gz .
f. cd /usr/share/ovirt-engine/dbscripts
g. ./backup.sh
h. mv engine_*.sql ~/backup/engine.sql
3. You may also want to backup dwh & reports:
a. cd /usr/share/ovirt-engine/bin/
b. ./engine-backup.sh --mode=backup --scope=db --db-user=engine
--db-password=XXX --file=/usr/tmp/rhevm-backups/engine-backup
--log=/tmp/engine-backup.log
c. ./engine-backup.sh --mode=backup --scope=dwhdb --db-user=engine
--db-password=XXX --file=/usr/tmp/rhevm-backups/dwh-backup
--log=/tmp/engine-backup.log
d. ./engine-backup.sh --mode=backup --scope=reportsdb --db-user=engine
--db-password=XXX --file=/usr/tmp/rhevm-backups/reports-backup
--log=/tmp/engine-backup.log
4. Download these backup files, and copy them to the destination host.
Restore configuration
1. On the destination host, do:
Again, steps a-h, basically
engine-setup
engine-cleanup
engine-backup mode=restore --file=~/ovirt-engine-source --log=backup.log
also, I would run a second
engine-setup
After that, you should be good to go..
Of course, depending on your previous engine setup this could be a little
more complicated. Still, quite strait forward.
[1] http://www.ovirt.org/Ovirt-engine-backup
a. service ovirt-engine stop
b. service ovirt-engine-dwhd stop
c. cd backup
d. tar -C /etc/pki/ovirt-engine -xzpf ovirt-engine-pki.tar.gz
e. tar -C /etc/ovirt-engine -xzpf ovirt-engine-conf.tar.gz
f. tar -xvjf engine-backup
g. tar -xvjf dwh-backup
h. tar -xvjf reports-backup
Restore Database
1. On the destination host do:
a. su - postgres -c "psql -d template1 -c 'drop database engine;'"
b. su - postgres -c "psql -d template1 -c 'create database engine owner
engine;'"
c. su - postgres
d. psql
e. \c engine
f. \i /path/to/backup/engine.sql
NOTE: in case you have issues logging in to the database, add the following
line to the pg_hba.conf file:
host all engine 127.0.0.1/32 trust
2. Fix engine password:
a. su - postgres
b. psql
c. alter user engine with password 'XXXXXXX';
Change ovirt hostname
On the destination host, run:
/usr/share/ovirt-engine/setup/bin/ovirt-engine-rename
NB:
Restoring the dwh/reports database is similar to steps 5-7, but omitted from
this document due to problems starting the reporting service.
2014-11-07 10:28 GMT+01:00 Sven Kieske <s.kieske(a)mittwald.de>:
>
>
>
> On 07/11/14 10:10, Ml Ml wrote:
> > anyone? :)
> >
> > Or are you only doing backups, no restore? :-P
>
> gladly I just had to test disaster recovery and not actually
> perform it (yet) :D
>
> To be honest: I never have restored ovirt-engine with running vdsm
> hosts connected to it, sounds like a lot of fun, I see if I can
> grab some time and try this out myself :)
>
> By your description I guess you have nfs/iso domain on your engine host?
> why don't you just seperate it, so no need for remounts
> if your engine is destroyed.
>
> HTH
>
> --
> Mit freundlichen Grüßen / Regards
>
> Sven Kieske
>
> Systemadministrator
> Mittwald CM Service GmbH & Co. KG
> Königsberger Straße 6
> 32339 Espelkamp
> T: +49-5772-293-100
> F: +49-5772-293-333
> https://www.mittwald.de
> Geschäftsführer: Robert Meyer
> St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
> Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad
> Oeynhausen
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users