6:05 p.m.
This is a multi-part message in MIME format.
--------------080409070709050803070307
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Hi all,
I 'd like to receive any usefull advices from the community about good
practice of backing up ovirt with the restraint of zero down time.
This involves :
* saving vms without shutting down (Restoring them can be done with a
halt). Is live snapshot enough for this? Is lvm or san snapshot
recommended?
* saving the postgres database (or only some of main tables). Can we
do it without stopping engine and the risk of a data corruption? Is
there a howto?
Thank you for your help.
--
Nathanaël Blanchet
Supervision réseau
Pôle exploitation et maintenance
Département des systèmes d'information
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5
Tél. 33 (0)4 67 54 84 55
Fax 33 (0)4 67 54 84 14
blanchet(a)abes.fr
--------------080409070709050803070307
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font size="-1">Hi all,<br>
<br>
I 'd like to receive any usefull advices from the community about
good practice of backing up ovirt with the restraint of zero down
time.<br>
This involves :<br>
</font>
<ul>
<li><font size="-1">saving vms without shutting down
(Restoring
them can be done with a halt). Is live snapshot enough for
this? Is lvm or san snapshot recommended?<br>
</font></li>
<li><font size="-1">saving the postgres database (or only some
of
main tables). Can we do it without stopping engine and the
risk of a data corruption? Is there a howto?</font></li>
</ul>
<p><font size="-1">Thank you for your
help.</font><br>
</p>
<pre class="moz-signature" cols="72">--
Nathanaël Blanchet
Supervision réseau
Pôle exploitation et maintenance
Département des systèmes d'information
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5
Tél. 33 (0)4 67 54 84 55
Fax 33 (0)4 67 54 84 14
<a class="moz-txt-link-abbreviated"
href="mailto:blanchet@abes.fr">blanchet@abes.fr</a> </pre>
</body>
</html>
--------------080409070709050803070307--
1 p.m.
----- Original Message -----
From: "Nathanaël Blanchet" <blanchet(a)abes.fr>
To: users(a)ovirt.org
Sent: Monday, December 23, 2013 5:05:01 PM
Subject: [Users] recommandations for saving backing up ovirt
Hi all,
I 'd like to receive any usefull advices from the community about good
practice of backing up ovirt with the restraint of zero down time.
This involves :
* saving vms without shutting down (Restoring them can be done with a
halt). Is live snapshot enough for this? Is lvm or san snapshot
recommended?
See http://www.ovirt.org/Features/Backup_API
* saving the postgres database (or only some of main tables). Can
we do
it without stopping engine and the risk of a data corruption? Is there a
howto?
For 3.3 you have share/ovirt-engine/bin/engine-backup.sh
for usage please run it with --help
You may do it without stopping the engine
Thank you for your help.
--
Nathanaël Blanchet
Supervision réseau
Pôle exploitation et maintenance
Département des systèmes d'information
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5
Tél. 33 (0)4 67 54 84 55
Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
7:28 p.m.
On 12/24/2013 12:00 PM, Eli Mesika wrote:
----- Original Message -----
> From: "Nathanaël Blanchet" <blanchet(a)abes.fr>
> To: users(a)ovirt.org
> Sent: Monday, December 23, 2013 5:05:01 PM
> Subject: [Users] recommandations for saving backing up ovirt
>
> Hi all,
>
> I 'd like to receive any usefull advices from the community about good
> practice of backing up ovirt with the restraint of zero down time.
> This involves :
>
>
> * saving vms without shutting down (Restoring them can be done with a
> halt). Is live snapshot enough for this? Is lvm or san snapshot
> recommended?
See http://www.ovirt.org/Features/Backup_API
using storage side snapshot could be interesting as well. ayal - thoughts?
> * saving the postgres database (or only some of main tables). Can we do
> it without stopping engine and the risk of a data corruption? Is there a
> howto?
For 3.3 you have share/ovirt-engine/bin/engine-backup.sh
for usage please run it with --help
You may do it without stopping the engine
>
>
> Thank you for your help.
> --
> Nathanaël Blanchet
>
> Supervision réseau
> Pôle exploitation et maintenance
> Département des systèmes d'information
> 227 avenue Professeur-Jean-Louis-Viala
> 34193 MONTPELLIER CEDEX 5
> Tél. 33 (0)4 67 54 84 55
> Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr
>
> _______________________________________________
> 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
7:36 p.m.
----- Original Message -----
Hi all,
I 'd like to receive any usefull advices from the community about good
practice of backing up ovirt with the restraint of zero down time.
This involves :
* saving vms without shutting down (Restoring them can be done with a
halt). Is live snapshot enough for this? Is lvm or san snapshot
recommended?
live snapshot gives you crash consistent points in time to return to, however, if you want
a 'backup' which is stored externally and can then be restored in a different
configuration etc then you'd need to utilize the backup API (live snapshot + attach
the snap to a virtual appliance and then back it up).
live snapshots also integrate with the qemu guest agent so if you've deployed this
then you can get better consistency (file systems would be quiesced on linux guests and on
windows guests this should cause VSS to quiesce your apps as well).
If your storage supports snapshots and your VMs contain a single disk (direct lun) then
you can snapshot the lun on the storage side and again get crash consistency.
If you could get this to work for you then performance wise this is probably the best
option.
If your backup solution is integrated with your storage then even better.
* saving the postgres database (or only some of main tables). Can
we do
it without stopping engine and the risk of a data corruption? Is there a
howto?
Thank you for your help.
--
Nathanaël Blanchet
Supervision réseau
Pôle exploitation et maintenance
Département des systèmes d'information
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5
Tél. 33 (0)4 67 54 84 55
Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
3978
days inactive
3986
days old
3 comments
4 participants
participants (4)
-
Ayal Baron -
Eli Mesika -
Itamar Heim -
Nathanaël Blanchet