> as part of the RC1->RC2 migration I wanted to start with a full backup.
> I triggered the backup through the dashboard but the UI became unresponsive and showed a spinning pointer for minutes. I could not find anything related in the log and no ZIP files
> on the filesystem!?
Normally this means a backup has been triggered immediately. The first step of the backup is a complete consistency check of the database. This may indeed take a longer time, depending on the size of the db.
In 2.2 we actually made the consistency check faster because we found it took much too long for databases containing a large number of documents. Even for data sets containing a large number of resources, the consistency check should now complete within a few minutes. The export itself should have become significantly faster as well.
If you need a faster way to backup on RC1 for migrating to RC2, take the database offline and run the export gui from the command line:
java -jar start.jar -Xmx1024m org.exist.backup.ExportGUI
Selecting the "Direct Access" option in the GUI before clicking on "Check & Export" should considerably speed up the process.
Get latest updates about Open Source Projects, Conferences and News.