I have an application that uses BACKUP to copy the database to tablets
for offline use. It fails and produces a corrupt database about once a
year. It probably does 3000 or so copies a year. But like you, I'm not
sure if it is in the backup code or the copy code and I can't reproduce
it in a test.
My only suggestion (which I am meaning to implement myself one day), is
to do a test after the backup and copy to make sure the database can be
opened. Basically a verification stage of the backup. After then you can
be guaranteed that you have a valid backup.
On 4/09/2014 1:34 AM, Kam wrote:
Here's the code:
String sqlStatement = "BACKUP TO ?";
try (Connection connection = getConnection())
{
try (PreparedStatement preparedStatement =
connection.prepareStatement(sqlStatement))
{
preparedStatement.setString(1, fileName);
preparedStatement.executeUpdate();
if (isDebugEnabled)
{
logger.debug("BACKUP TO result
completed");
}
}
}
--
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 [email protected]
<mailto:[email protected]>.
To post to this group, send email to [email protected]
<mailto:[email protected]>.
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.
