Re: [Engine-devel] Tweaking backup/restore of engine

From: "Yedidyah Bar David" <didi(a)redhat.com&gt; To: "Eli Mesika" <emesika(a)redhat.com&gt; Cc: "Sven Kieske" <S.Kieske(a)mittwald.de&gt;, engine-devel(a)ovirt.org Sent: Wednesday, March 5, 2014 5:02:40 PM Subject: Re: [Engine-devel] Tweaking backup/restore of engine ----- Original Message ----- > From: "Eli Mesika" <emesika(a)redhat.com&gt; > To: "Sven Kieske" <S.Kieske(a)mittwald.de&gt; > Cc: engine-devel(a)ovirt.org > Sent: Wednesday, March 5, 2014 4:50:42 PM > Subject: Re: [Engine-devel] Tweaking backup/restore of engine > > > > ----- Original Message ----- > > From: "Sven Kieske" <S.Kieske(a)mittwald.de&gt; > > To: engine-devel(a)ovirt.org > > Sent: Monday, March 3, 2014 6:25:39 PM > > Subject: [Engine-devel] Tweaking backup/restore of engine > > > > Hi, > > > > currently all events are stored in the table audit_log > > which all gets saved when you use the engine-backup > > shell script. > > > > > > the event log is full of these login lines (engine 3.3.2): > > > > 25652 fdfc627c-d875-11e0-90f0-83df133b58cc admin@internal > > 00000000-0000-0000-0000-000000000000 \N \N \N \N \N 2014-01-20 > > 06:39:17.222+01 USER_VDC_LOGIN 30 0 User admin@internal > > logged in. f \N \N 00000000-0000-0000-0000-000000000000 \N \N \N > > \N 00000000-0000-0000-0000-000000000000 \N oVirt -1 30 f \N > > > > this makes the log and db grow very large when you use the REST-API > > to query ovirt for various data. > > > > Is this necessary for a working restore? > > It would be cool if we could tweak the engine-backup > > tool to just dump necessary tables so you don't have > > to restore events from the past no one is interested > > in. > > > > How does ovirt react, if I do not restore the content of the audit_log > > table? > > > > If this works (restore without audit_log) I would prefer to have > > this code upstream in ovirt git so I don't have to maintain > > my own backupscript. > > > > Would it be possible to extend the existing backupscript > > with a switch to not backup logs? > > Currently it's just "all" or "just db". > > Hi Sven > > engine-backup is calling eventually a postgres utility named pg_dump > this utility supports the following flag : > > --exclude-table-data=TABLE do NOT dump data for the named table(s) Oh, didn't notice that one. Added in 9.2, so not for el6. > > > I think that a RFE for adding support for this flag in engine-backup will > easily solve your problem Perhaps better to allow passing arbitrary options to pg_dump. Or something like that.

-- Didi