It was my mistake in describing. we do use the BACKUP command and then
since it produces a zip file, we create a new zip file and copy inputStream
to another outputStream to create a new zip file (with some configs related
to the DB) and then give that zip file to the customers to use as their
backup.
Maybe the issue happens while writing the zip file to another file or maybe
it's during backup. We've yet to encounter why.
On Monday, September 8, 2014 9:33:43 AM UTC-7, Thomas Mueller wrote:
>
> Hi,
>
> OK, now I'm not sure if you use the "backup" statement or not, because at
> the beginning you wrote you don't ("We have a feature that backs up the
> H2 DB file and zips it via java. the DB is in use when we back it up (all
> it does is copy the h2 file)").
>
> If you use the "backup" statement, then the database shouldn't get
> corrupt. If it does, then that would be a bug. I think we would need a
> reproducible test case. If you can reproduce the issue with a new database,
> could you try with H2 version 1.4.x? Version 1.4 should be more stable in
> this area, because recovery is much simpler (but version 1.4 is still beta).
>
> Regards,
> Thomas
>
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to h2-database+unsubscr...@googlegroups.com.
To post to this group, send email to h2-database@googlegroups.com.
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.
