From: Jianhua Wu <gom...@gm...> - 2011-02-13 11:10:01
|
I would say the backup module of the Exist really sucks! I use Tomcat as the web container, Exist is deployed as a WAR file here is my configuration for consistency check. <job type="system" name="check1" class="org.exist.storage.ConsistencyCheckTask" cron-trigger="0 45 18 * * *"> <parameter name="output" value="export/"/> <parameter name="backup" value="yes"/> <parameter name="incremental" value="no"/> <parameter name="incremental-check" value="no"/> <parameter name="max" value="2"/> </job> It worked "FINE" I clicked "trigger" on Exist's webpage console, and immediatelly, there was a zip file link there. then I had the default data directory changed from "WEB-INF/data" to "../../exist-data", restart Tomcat, the Exist works. But the backup schedule does not. Note I have created "export" subfolder under "exist-data" folder. Then I click button "trigger" from the webpage console, it appears that the backup job executed successfully, but it never shows a zip file link on the webpage. Then I moved to the exist-data/export, and I saw the backup copy was there. What weird is that though I had the backup directory changed to "../../exist-data/export", the backup that I created before I made a change to the conf.xml is still there, but the new backup copy does not show up. Which means that the backup page is not updated by the new configuraiton in the conf.xml file. It appears that there is something wrong with the design of the internal backup mechanism. I don't know who is/are the people inside the Exist development team that I should contact, if you happen to know how to resolve this issue, or knows who should I contact, please inform me. Thanks -- View this message in context: http://exist.2174344.n4.nabble.com/Scheduled-Backup-does-not-run-tp3298068p3303568.html Sent from the exist-open mailing list archive at Nabble.com. |