[Engine-devel] Backing up the DB
Hi all, I have a working development environment for ovirt-engine and I want to verify someone else's gerrit change. Is there a documented proceedure for backing up the engine db so that, after checking out the new code and updating the db schema, I can revert to my old code and DB (schema and data). Thanks! -- Adam Litke <agl@us.ibm.com> IBM Linux Technology Center
Hi Adam, ----- Original Message -----
From: "Adam Litke" <agl@us.ibm.com> To: engine-devel@ovirt.org Sent: Monday, April 2, 2012 3:20:58 PM Subject: [Engine-devel] Backing up the DB
Hi all,
I have a working development environment for ovirt-engine and I want to verify someone else's gerrit change. Is there a documented proceedure for backing up
Not really documented, but at least I do this frequently You have to expect some problems as the hosts still have the old state, so I would recommend to - disable both ssl and host install http://www.ovirt.org/wiki/OVirt_-_disable_SSL_in_VDSM - you may also need to restart your hosts to flush the state (mounts, VM's, etc) the engine pushed it to after db restore And then you can just use the usual postgresql utilities.
the engine db so that, after checking out the new code and updating the db schema, I can revert to my old code and DB (schema and data). Thanks!
-- Adam Litke <agl@us.ibm.com> IBM Linux Technology Center
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
This is a multi-part message in MIME format. --------------050901030201090108020804 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, On 04/02/2012 09:20 AM, Adam Litke wrote:
Hi all,
I have a working development environment for ovirt-engine and I want to verify someone else's gerrit change. Is there a documented proceedure for backing up the engine db so that, after checking out the new code and updating the db schema, I can revert to my old code and DB (schema and data). Thanks!
Usually I use this tool to backup/restore db: https://github.com/dougsland/misc-rhev/blob/master/rhevm-db-tool.py However, since it's "rhevm" db tool.. need manually change the db name to "engine", I will rename it to engine-db-tool and update the code to 'engine' soon.. -- Cheers Douglas --------------050901030201090108020804 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> Hi,<br> <br> On 04/02/2012 09:20 AM, Adam Litke wrote: <blockquote cite="mid:20120402132058.GG11957@aglitke.ibm.com" type="cite"> <pre wrap="">Hi all, I have a working development environment for ovirt-engine and I want to verify someone else's gerrit change. Is there a documented proceedure for backing up the engine db so that, after checking out the new code and updating the db schema, I can revert to my old code and DB (schema and data). Thanks! </pre> </blockquote> Usually I use this tool to backup/restore db:<br> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> <a href="https://github.com/dougsland/misc-rhev/blob/master/rhevm-db-tool.py">https://github.com/dougsland/misc-rhev/blob/master/rhevm-db-tool.py</a><br> <br> However, since it's "rhevm" db tool.. need manually change the db name to "engine",<br> I will rename it to engine-db-tool and update the code to 'engine' soon..<br> <br> <pre class="moz-signature" cols="72">-- Cheers Douglas</pre> </body> </html> --------------050901030201090108020804--
----- Original Message -----
From: "Douglas Landgraf" <dougsland@redhat.com> To: "Adam Litke" <agl@us.ibm.com> Cc: engine-devel@ovirt.org, "Douglas Landgraf" <dlandgra@redhat.com> Sent: Monday, April 2, 2012 6:19:23 PM Subject: Re: [Engine-devel] Backing up the DB
Hi,
On 04/02/2012 09:20 AM, Adam Litke wrote:
Hi all,
I have a working development environment for ovirt-engine and I want to verify someone else's gerrit change. Is there a documented proceedure for backing up the engine db so that, after checking out the new code and updating the db schema, I can revert to my old code and DB (schema and data).
You can use pg_dump for backup and psql for restore : backup: pg_dump -C -E UTF8 --column-inserts --disable-dollar-quoting --disable-triggers -U postgres --format=p -f <backupfile> <dbname> restore: psql -U postgres -f <backupfile> template1
Thanks! Usually I use this tool to backup/restore db: https://github.com/dougsland/misc-rhev/blob/master/rhevm-db-tool.py
However, since it's "rhevm" db tool.. need manually change the db name to "engine", I will rename it to engine-db-tool and update the code to 'engine' soon..
-- Cheers Douglas _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
On 03/04/12 12:05, Eli Mesika wrote:
----- Original Message -----
From: "Douglas Landgraf" <dougsland@redhat.com> To: "Adam Litke" <agl@us.ibm.com> Cc: engine-devel@ovirt.org, "Douglas Landgraf" <dlandgra@redhat.com> Sent: Monday, April 2, 2012 6:19:23 PM Subject: Re: [Engine-devel] Backing up the DB
Hi,
On 04/02/2012 09:20 AM, Adam Litke wrote:
Hi all,
I have a working development environment for ovirt-engine and I want to verify someone else's gerrit change. Is there a documented proceedure for backing up the engine db so that, after checking out the new code and updating the db schema, I can revert to my old code and DB (schema and data).
You can use pg_dump for backup and psql for restore :
backup: pg_dump -C -E UTF8 --column-inserts --disable-dollar-quoting --disable-triggers -U postgres --format=p -f <backupfile> <dbname>
restore: psql -U postgres -f <backupfile> template1
Eli, Can we have a script for backup and restore DB in the repo? I see we have backup_db.sql any use of it? Thanks, Livnat
Thanks! Usually I use this tool to backup/restore db: https://github.com/dougsland/misc-rhev/blob/master/rhevm-db-tool.py
However, since it's "rhevm" db tool.. need manually change the db name to "engine", I will rename it to engine-db-tool and update the code to 'engine' soon..
-- Cheers Douglas _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
This is a multi-part message in MIME format. --------------050900000407040807010508 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 04/03/2012 05:10 AM, Livnat Peer wrote:
On 03/04/12 12:05, Eli Mesika wrote:
----- Original Message -----
From: "Douglas Landgraf"<dougsland@redhat.com> To: "Adam Litke"<agl@us.ibm.com> Cc: engine-devel@ovirt.org, "Douglas Landgraf"<dlandgra@redhat.com> Sent: Monday, April 2, 2012 6:19:23 PM Subject: Re: [Engine-devel] Backing up the DB
Hi,
On 04/02/2012 09:20 AM, Adam Litke wrote:
Hi all,
I have a working development environment for ovirt-engine and I want to verify someone else's gerrit change. Is there a documented proceedure for backing up the engine db so that, after checking out the new code and updating the db schema, I can revert to my old code and DB (schema and data). You can use pg_dump for backup and psql for restore :
backup: pg_dump -C -E UTF8 --column-inserts --disable-dollar-quoting --disable-triggers -U postgres --format=p -f<backupfile> <dbname>
restore: psql -U postgres -f<backupfile> template1
Eli, Can we have a script for backup and restore DB in the repo?
I see we have backup_db.sql any use of it?
If you guys are interested, I have updated the tool to work with systemctl/enginedb and tested under Fedora 16: Here my use: # mkdir /engine-backup-db # chmod +x engine-db-tool.py backup manually ============= ./engine-db-tool.py --backup --path=/engine-db-backup Stopping jboss-as service... Backuping database: /engine-db-backup/dump_RHEVDB_BACKUP_2012-04-03-15:05.sql Starting jboss-as service... Done restore manually ============= # ./engine-db-tool.py --restore --path=/engine-db-backup/dump_RHEVDB_BACKUP_2012-04-03-15:05.sql Stopping jboss-as service... Restoring database: /engine-db-backup/dump_RHEVDB_BACKUP_2012-04-03-15:05.sql Starting jboss-as service... Done Crontab ======= # crontab -e (adding to my crontab user) # Every day 18:00 backup db 00 18 * * * /path-to/engine-db-tool.py --backup --path=/engine-backup-db Download: https://raw.github.com/dougsland/misc-rhev/master/engine-db-tool.py Thanks! -- Cheers Douglas --------------050900000407040807010508 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> On 04/03/2012 05:10 AM, Livnat Peer wrote: <blockquote cite="mid:4F7ABEA1.6030409@redhat.com" type="cite"> <pre wrap="">On 03/04/12 12:05, Eli Mesika wrote: </pre> <blockquote type="cite"> <pre wrap=""> ----- Original Message ----- </pre> <blockquote type="cite"> <pre wrap="">From: "Douglas Landgraf" <a class="moz-txt-link-rfc2396E" href="mailto:dougsland@redhat.com"><dougsland@redhat.com></a> To: "Adam Litke" <a class="moz-txt-link-rfc2396E" href="mailto:agl@us.ibm.com"><agl@us.ibm.com></a> Cc: <a class="moz-txt-link-abbreviated" href="mailto:engine-devel@ovirt.org">engine-devel@ovirt.org</a>, "Douglas Landgraf" <a class="moz-txt-link-rfc2396E" href="mailto:dlandgra@redhat.com"><dlandgra@redhat.com></a> Sent: Monday, April 2, 2012 6:19:23 PM Subject: Re: [Engine-devel] Backing up the DB Hi, On 04/02/2012 09:20 AM, Adam Litke wrote: Hi all, I have a working development environment for ovirt-engine and I want to verify someone else's gerrit change. Is there a documented proceedure for backing up the engine db so that, after checking out the new code and updating the db schema, I can revert to my old code and DB (schema and data). </pre> </blockquote> <pre wrap=""> You can use pg_dump for backup and psql for restore : backup: pg_dump -C -E UTF8 --column-inserts --disable-dollar-quoting --disable-triggers -U postgres --format=p -f <backupfile> <dbname> restore: psql -U postgres -f <backupfile> template1 </pre> </blockquote> <pre wrap=""> Eli, Can we have a script for backup and restore DB in the repo? I see we have backup_db.sql any use of it? </pre> </blockquote> If you guys are interested, I have updated the tool to work with systemctl/enginedb and tested under Fedora 16:<br> <br> Here my use:<br> <br> # mkdir /engine-backup-db<br> # chmod +x engine-db-tool.py<br> <br> backup manually<br> =============<br> ./engine-db-tool.py --backup --path=/engine-db-backup<br> Stopping jboss-as service...<br> Backuping database: /engine-db-backup/dump_RHEVDB_BACKUP_2012-04-03-15:05.sql<br> Starting jboss-as service...<br> Done<br> <br> <br> restore manually<br> =============<br> # ./engine-db-tool.py --restore --path=/engine-db-backup/dump_RHEVDB_BACKUP_2012-04-03-15:05.sql<br> Stopping jboss-as service...<br> Restoring database: /engine-db-backup/dump_RHEVDB_BACKUP_2012-04-03-15:05.sql<br> Starting jboss-as service...<br> Done<br> <br> <br> Crontab<br> =======<br> # crontab -e (adding to my crontab user)<br> <br> # Every day 18:00 backup db<br> 00 18 * * * /path-to/engine-db-tool.py --backup --path=/engine-backup-db<br> <br> <br> Download: <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> <a href="https://raw.github.com/dougsland/misc-rhev/master/engine-db-tool.py">https://raw.github.com/dougsland/misc-rhev/master/engine-db-tool.py</a><br> <br> Thanks!<br> <br> <pre class="moz-signature" cols="72">-- Cheers Douglas</pre> </body> </html> --------------050900000407040807010508--
On 04/03/2012 11:10 PM, Douglas Landgraf wrote:
On 04/03/2012 05:10 AM, Livnat Peer wrote:
On 03/04/12 12:05, Eli Mesika wrote:
Eli - maybe we can take the script of Douglas and add it to the git repo?
----- Original Message -----
From: "Douglas Landgraf" <dougsland@redhat.com> To: "Adam Litke" <agl@us.ibm.com> Cc: engine-devel@ovirt.org, "Douglas Landgraf" <dlandgra@redhat.com> Sent: Monday, April 2, 2012 6:19:23 PM Subject: Re: [Engine-devel] Backing up the DB
Hi,
On 04/02/2012 09:20 AM, Adam Litke wrote:
Hi all,
I have a working development environment for ovirt-engine and I want to verify someone else's gerrit change. Is there a documented proceedure for backing up the engine db so that, after checking out the new code and updating the db schema, I can revert to my old code and DB (schema and data). You can use pg_dump for backup and psql for restore :
backup: pg_dump -C -E UTF8 --column-inserts --disable-dollar-quoting --disable-triggers -U postgres --format=p -f <backupfile> <dbname>
restore: psql -U postgres -f <backupfile> template1
Eli, Can we have a script for backup and restore DB in the repo?
I see we have backup_db.sql any use of it?
If you guys are interested, I have updated the tool to work with systemctl/enginedb and tested under Fedora 16:
Here my use:
# mkdir /engine-backup-db # chmod +x engine-db-tool.py
backup manually ============= ./engine-db-tool.py --backup --path=/engine-db-backup Stopping jboss-as service... Backuping database: /engine-db-backup/dump_RHEVDB_BACKUP_2012-04-03-15:05.sql Starting jboss-as service... Done
restore manually ============= # ./engine-db-tool.py --restore --path=/engine-db-backup/dump_RHEVDB_BACKUP_2012-04-03-15:05.sql Stopping jboss-as service... Restoring database: /engine-db-backup/dump_RHEVDB_BACKUP_2012-04-03-15:05.sql Starting jboss-as service... Done
Crontab ======= # crontab -e (adding to my crontab user)
# Every day 18:00 backup db 00 18 * * * /path-to/engine-db-tool.py --backup --path=/engine-backup-db
Download: https://raw.github.com/dougsland/misc-rhev/master/engine-db-tool.py
Thanks!
-- Cheers Douglas
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
On 04/04/2012 09:16 AM, Yair Zaslavsky wrote:
On 04/03/2012 11:10 PM, Douglas Landgraf wrote:
On 04/03/2012 05:10 AM, Livnat Peer wrote:
On 03/04/12 12:05, Eli Mesika wrote:
Eli - maybe we can take the script of Douglas and add it to the git repo? Actually, I'll correct myself - I think we should produce a bash version of it. What do you think?
----- Original Message -----
From: "Douglas Landgraf" <dougsland@redhat.com> To: "Adam Litke" <agl@us.ibm.com> Cc: engine-devel@ovirt.org, "Douglas Landgraf" <dlandgra@redhat.com> Sent: Monday, April 2, 2012 6:19:23 PM Subject: Re: [Engine-devel] Backing up the DB
Hi,
On 04/02/2012 09:20 AM, Adam Litke wrote:
Hi all,
I have a working development environment for ovirt-engine and I want to verify someone else's gerrit change. Is there a documented proceedure for backing up the engine db so that, after checking out the new code and updating the db schema, I can revert to my old code and DB (schema and data). You can use pg_dump for backup and psql for restore :
backup: pg_dump -C -E UTF8 --column-inserts --disable-dollar-quoting --disable-triggers -U postgres --format=p -f <backupfile> <dbname>
restore: psql -U postgres -f <backupfile> template1
Eli, Can we have a script for backup and restore DB in the repo?
I see we have backup_db.sql any use of it?
If you guys are interested, I have updated the tool to work with systemctl/enginedb and tested under Fedora 16:
Here my use:
# mkdir /engine-backup-db # chmod +x engine-db-tool.py
backup manually ============= ./engine-db-tool.py --backup --path=/engine-db-backup Stopping jboss-as service... Backuping database: /engine-db-backup/dump_RHEVDB_BACKUP_2012-04-03-15:05.sql Starting jboss-as service... Done
restore manually ============= # ./engine-db-tool.py --restore --path=/engine-db-backup/dump_RHEVDB_BACKUP_2012-04-03-15:05.sql Stopping jboss-as service... Restoring database: /engine-db-backup/dump_RHEVDB_BACKUP_2012-04-03-15:05.sql Starting jboss-as service... Done
Crontab ======= # crontab -e (adding to my crontab user)
# Every day 18:00 backup db 00 18 * * * /path-to/engine-db-tool.py --backup --path=/engine-backup-db
Download: https://raw.github.com/dougsland/misc-rhev/master/engine-db-tool.py
Thanks!
-- Cheers Douglas
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
This is a multi-part message in MIME format. --------------050600000904030202070900 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 04/04/2012 02:18 AM, Yair Zaslavsky wrote:
On 04/04/2012 09:16 AM, Yair Zaslavsky wrote:
On 04/03/2012 11:10 PM, Douglas Landgraf wrote:
On 04/03/2012 05:10 AM, Livnat Peer wrote:
On 03/04/12 12:05, Eli Mesika wrote: Eli - maybe we can take the script of Douglas and add it to the git repo? Actually, I'll correct myself - I think we should produce a bash version of it. What do you think? IMHO, it's not required to convert to bash since we have others oVirt tools already in python. Anyway, I have documented all steps here (with or without tool): http://ovirt.org/w/index.php?title=Backup_engine_db
Would be nice to have such tool available when we install a ovirt engine system. Thanks! -- Cheers Douglas --------------050600000904030202070900 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> On 04/04/2012 02:18 AM, Yair Zaslavsky wrote: <blockquote cite="mid:4F7BE798.8090705@redhat.com" type="cite"> <pre wrap="">On 04/04/2012 09:16 AM, Yair Zaslavsky wrote: </pre> <blockquote type="cite"> <pre wrap="">On 04/03/2012 11:10 PM, Douglas Landgraf wrote: </pre> <blockquote type="cite"> <pre wrap="">On 04/03/2012 05:10 AM, Livnat Peer wrote: </pre> <blockquote type="cite"> <pre wrap="">On 03/04/12 12:05, Eli Mesika wrote: </pre> </blockquote> </blockquote> <pre wrap=""> Eli - maybe we can take the script of Douglas and add it to the git repo? </pre> </blockquote> <pre wrap="">Actually, I'll correct myself - I think we should produce a bash version of it. What do you think? </pre> </blockquote> IMHO, it's not required to convert to bash since we have others oVirt tools already in python.<br> Anyway, I have documented all steps here (with or without tool): <br> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> <a href="http://ovirt.org/w/index.php?title=Backup_engine_db">http://ovirt.org/w/index.php?title=Backup_engine_db</a><br> <br> Would be nice to have such tool available when we install a ovirt engine system.<br> <br> Thanks!<br> <pre class="moz-signature" cols="72">-- Cheers Douglas</pre> </body> </html> --------------050600000904030202070900--
--=_0a51f86f-12ba-4242-8783-c7d1b382b2fc Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit We already have the backup code in python - under engine-cleanup What about using the same code-base? or adding --backup-db-only to engine-cleaup? ----- Original Message -----
On 04/04/2012 02:18 AM, Yair Zaslavsky wrote:
On 04/04/2012 09:16 AM, Yair Zaslavsky wrote:
On 04/03/2012 11:10 PM, Douglas Landgraf wrote:
On 04/03/2012 05:10 AM, Livnat Peer wrote:
On 03/04/12 12:05, Eli Mesika wrote:
Eli - maybe we can take the script of Douglas and add it to the git repo?
Actually, I'll correct myself - I think we should produce a bash version
of it. What do you think?
IMHO, it's not required to convert to bash since we have others oVirt tools already in python. Anyway, I have documented all steps here (with or without tool): http://ovirt.org/w/index.php?title=Backup_engine_db
Would be nice to have such tool available when we install a ovirt engine system.
Thanks! -- Cheers Douglas _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
--=_0a51f86f-12ba-4242-8783-c7d1b382b2fc Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Times New Roman; font-size: 12pt; color: #000000'>We already have the backup code in python - under engine-cleanup <div>What about using the same code-base?</div><div>or adding --backup-db-only to engine-cleaup?<br><br><hr id="zwchr"><blockquote style="border-left:2px solid rgb(16, 16, 255);margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"> On 04/04/2012 02:18 AM, Yair Zaslavsky wrote: <blockquote cite="mid:4F7BE798.8090705@redhat.com"> <pre>On 04/04/2012 09:16 AM, Yair Zaslavsky wrote: </pre> <blockquote> <pre>On 04/03/2012 11:10 PM, Douglas Landgraf wrote: </pre> <blockquote> <pre>On 04/03/2012 05:10 AM, Livnat Peer wrote: </pre> <blockquote> <pre>On 03/04/12 12:05, Eli Mesika wrote: </pre> </blockquote> </blockquote> <pre>Eli - maybe we can take the script of Douglas and add it to the git repo? </pre> </blockquote> <pre>Actually, I'll correct myself - I think we should produce a bash version of it. What do you think? </pre> </blockquote> IMHO, it's not required to convert to bash since we have others oVirt tools already in python.<br> Anyway, I have documented all steps here (with or without tool): <br> <a href="http://ovirt.org/w/index.php?title=Backup_engine_db" target="_blank">http://ovirt.org/w/index.php?title=Backup_engine_db</a><br> <br> Would be nice to have such tool available when we install a ovirt engine system.<br> <br> Thanks!<br> <pre class="moz-signature">-- Cheers Douglas</pre> <br>_______________________________________________<br>Engine-devel mailing list<br>Engine-devel@ovirt.org<br>http://lists.ovirt.org/mailman/listinfo/engine-devel<br></blockquote><br></div></div></body></html> --=_0a51f86f-12ba-4242-8783-c7d1b382b2fc--
This is a multi-part message in MIME format. --------------030002010003060600050001 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi, On 04/05/2012 04:27 AM, Ofer Schreiber wrote:
We already have the backup code in python - under engine-cleanup What about using the same code-base? or adding --backup-db-only to engine-cleaup?
From my point of view, it's ok. If we are going to use engine-cleanup, let's keep in mind the restore mode too. For while, I will use engine-db-tool that's already ready. -- Cheers Douglas --------------030002010003060600050001 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit <html> <head> <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> Hi,<br> <br> On 04/05/2012 04:27 AM, Ofer Schreiber wrote: <blockquote cite="mid:8e265a23-419d-417e-9a11-a7547f9f6c91@zmail14.collab.prod.int.phx2.redhat.com" type="cite"> <style type="text/css">p { margin: 0; }</style> <div style="font-family: Times New Roman; font-size: 12pt; color: rgb(0, 0, 0);">We already have the backup code in python - under engine-cleanup <div>What about using the same code-base?</div> <div>or adding --backup-db-only to engine-cleaup?<br> </div> </div> </blockquote> <br> From my point of view, it's ok. If we are going to use engine-cleanup, let's keep in mind the restore mode too.<br> For while, I will use engine-db-tool that's already ready.<br> <br> <pre class="moz-signature" cols="72">-- Cheers Douglas</pre> </body> </html> --------------030002010003060600050001--
----- Original Message -----
From: "Douglas Landgraf" <dougsland@redhat.com> To: "Ofer Schreiber" <oschreib@redhat.com> Cc: engine-devel@ovirt.org Sent: Thursday, April 5, 2012 10:57:15 PM Subject: Re: [Engine-devel] Backing up the DB
Hi,
On 04/05/2012 04:27 AM, Ofer Schreiber wrote:
We already have the backup code in python - under engine-cleanup What about using the same code-base? or adding --backup-db-only to engine-cleaup?
I think that we should do simple bash wrapper scripts for backup/restore that calls pg_dump/pg_restore , put those scripts in dbscripts where all db stuff is located and print a message that other options are available using the original pg_dump/pg_restore
From my point of view, it's ok. If we are going to use engine-cleanup, let's keep in mind the restore mode too. For while, I will use engine-db-tool that's already ready.
-- Cheers Douglas _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
On 04/06/2012 04:51 AM, Eli Mesika wrote:
----- Original Message -----
From: "Douglas Landgraf" <dougsland@redhat.com> To: "Ofer Schreiber" <oschreib@redhat.com> Cc: engine-devel@ovirt.org Sent: Thursday, April 5, 2012 10:57:15 PM Subject: Re: [Engine-devel] Backing up the DB
Hi,
On 04/05/2012 04:27 AM, Ofer Schreiber wrote:
We already have the backup code in python - under engine-cleanup What about using the same code-base? or adding --backup-db-only to engine-cleaup?
I think that we should do simple bash wrapper scripts for backup/restore that calls pg_dump/pg_restore , put those scripts in dbscripts where all db stuff is located and print a message that other options are available using the original pg_dump/pg_restore
+1 - the scripts should use the options for pg_dump as specified in the script provided by Douglas (the py version)
From my point of view, it's ok. If we are going to use engine-cleanup, let's keep in mind the restore mode too. For while, I will use engine-db-tool that's already ready.
-- Cheers Douglas _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
participants (7)
-
Adam Litke -
Douglas Landgraf -
Eli Mesika -
Laszlo Hornyak -
Livnat Peer -
Ofer Schreiber -
Yair Zaslavsky