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

Itamar Heim iheim at redhat.com
Wed Mar 5 09:21:00 UTC 2014


On 03/05/2014 10:50 AM, Sven Kieske wrote:
> Hi,
>
> forwarding this mail to the users list:
>
> Does somebody do engine(DB) backups and restores
> without the content of the audit_log table?
>
> This one can grow quite large if you are using
> REST like it's meant to be (stateless, so
> a single login/logout event for every REST-Call).
>
> This can quickly accumulate 100.000 events and more.
>
> Does anybody got any experience with restoring
> engine without these logs?
>
> I'm talking about disaster recovery, so I want
> just to backup the necessary data to make the engine
> run.

mostly answered on original thread.
you can reduce REST API login events by using session via API/SDK.
you can change how long audit_log is kept via AuditLogAgingThreshold 
config key (number in days)
unless something changed which i missed, audit log entries are not 
needed for restore. table is needed of course

>
>
> -------- Original-Nachricht --------
> Betreff: [Engine-devel] Tweaking backup/restore of engine
> Datum: Mon, 3 Mar 2014 16:25:39 +0000
> Von: Sven Kieske <S.Kieske at mittwald.de>
> An: engine-devel at ovirt.org <engine-devel at ovirt.org>
>
> 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 at 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 at 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".
>
> I also recall that there shouldn't occur multiple login events any
> more since ovirt 3.3. but it still seems to be the case.
>
> I also do not understand how you would manage a stored authentication
> via REST as REST is stateless.
>
> I would appreciate any feedback or thoughts on this topic.
>




More information about the Users mailing list