From: Michael W. <wes...@ja...> - 2021-03-11 23:50:12
|
Hi Sava, My emergency backup script is: #!/bin/sh cd ~/exist bin/run.sh org.exist.backup.ExportMain -x -d ~/backup/full-$1 I run this before removing any of the files in the DATA directory. There are corrupt files, usually put into __lost_and_found__ in the generated backup, so I know what to look for in the daily backups. Hope this helps. Take care. 2021年3月12日(金) 4:46 Sava Jurisic <sju...@mr...>: > Hi All, > > > > I have been searching the mailing lists for sometime now and I just don’t > see the answers. > > > > We have been using eXistDB from inception … so BIG thanks to everyone for > great product. > > > > Currently, using exist 4.7.1 in Windows environment (Server / 10Pro /7 Pro) > > > > Overall, it is very stable with little to none issues. > > > > However, every now and then, Windows system “dies” (sometime it is power > outage, sometime it is a user action like tripping over power cord, …etc). > > > > When this happens, most of the time eXistDB will corrupt. > > > > Good news, 80-90% of the time, self recovery works J > > > > Bed news – the rest of the time, we are stuck and we 100% rely on daily > backups (which is OK) > > > > Problem is, if system crashes mid-day, there is no backup. > > ------------------------------- > > So, we have been using Consistency-Check tool and sometimes it works. > > > > We have tried using one of Wolfgang’s recommendations to clear all *.log > files under DATA and execute “java -jar start.jar > org.exist.backup.ExportMain -z -x “ … but this would return “ERROR: Failed > to open database: null” > > -------------------------------- > > > > I am running out of ideas but we would need to have this resolved. > > > > ANY feedback will be MUCH appreciated! > > > > Thanks, > > Sava > > > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > -- Michael Westbay Writer/System Administrator http://www.japanesebaseball.com/ |