From: Jonathan R. <big...@ho...> - 2011-10-07 10:26:04
|
>>The reason I ask, is we just had a crash of our database in Korea, ~25GB of data. Consistency check (run from the GUI) ran for about 14 hours during which the database was off-line. The message I'm getting here is that there is no before/after image logging like in a conventional SQL database, where I place my log files on a separate disk and recover by copying back the blocks from incomplete transactions. Am I correct in this assumption? Jonathan Date: Thu, 6 Oct 2011 12:21:56 -0400 From: hi...@sp... To: exi...@li... Subject: Re: [Exist-open] How to run consistency check manually? Am I reading this correctly - is it possible to run the consistency check as a system task while the database instance is "live"? The reason I ask, is we just had a crash of our database in Korea, ~25GB of data. Consistency check (run from the GUI) ran for about 14 hours during which the database was off-line. In this case, we'd have to run off-line anyway as part of recovery, but it would be nice to know that we can run consistency check from time to time without taking the database down, when it takes so long to run. Does anyone have any ideas/experience in dealing with recovery of "large" databases like this? We have been down 14 hours for the consistency check, and are now running a re-index which I anticipate will take a similar amount of time to complete. Last time I re-loaded a full dataset, it took a similar amount of time. Would it be possible to copy the contents of the eXist data directory every (say) 6 hours, and when a crash occurs fall back to them? Is there a way to ensure that when I do the copy the database is in a consistent state? I have to come up with a better recovery plan, any advice would be welcome. Anthony On Wed, Oct 5, 2011 at 4:19 PM, kyung88 <gin...@gm...> wrote: Hi Anton, The Xquery scripts worked. So, we can trigger consistancy check any time without binding to schedule. java -jar start.jar org.exist.backup.ExportGUI To run above command, has to stop eXist instance. So, it only can be used during emergency. Thanks. Gina -- View this message in context: http://exist.2174344.n4.nabble.com/How-to-run-consistency-check-manually-tp3860159p3876030.html Sent from the exist-open mailing list archive at Nabble.com. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Exist-open mailing list Exi...@li... https://lists.sourceforge.net/lists/listinfo/exist-open ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Exist-open mailing list Exi...@li... https://lists.sourceforge.net/lists/listinfo/exist-open |