Hi, I have several use-case like this. In my own experience best results were obtained using " SCRIPT ... GZIP " because:
1) snapshot files sql.gz (in my use-cases) are 300% to 400% smaller than zip backup db files. 2) snapshot content is an sql script that can be ported to other dbms and can be used for human recovery/debug if something goes wrong. 3) can be used to create a new and compact database on target system. 4) Script command can produce a transactionally consistent snapshot when database is in use. See: http://www.h2database.com/html/tutorial.html#upgrade_backup_restore regards, Dario El 06/04/11 19:57, timbo escribió: > We are using H2 in embedded mode, and have an unusual requirement to > copy snapshots of an open DB file periodically. Is the following > procedure safe (won't lose/corrupt data in the master or snapshot DB > file)? > > 1) SET EXCLUSIVE 1 > 2) CHECKPOINT SYNC > 3) Copy DB file > 4) SET EXCLUSIVE 0 > 5) Continue using database > > This would seem to be much faster than shutting down, copying and > opening the db. > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
