Regular backups in order to recover from data corruption. Always a good practice.
Useful as I had a production db 24/7 for almost 1 year (using 1.3.176) and Windows updates made the database crash a few times. As for the txt done by the recover, I guess it's just a debug log of the recovery mechanism. I cannot confirm, I'm not part of the h2 dev team. On Tuesday, May 9, 2017 at 10:42:50 AM UTC+2, hendrik wrote: > > > > On Monday, May 8, 2017 at 2:02:04 PM UTC+2, Christian MICHON wrote: >> >> Yes you can use the 1.4 jar to export the script. I've done this already. >> >> I would advice to use the default settings per version. 1.3 uses page >> store, 1.4 the newer store. Do not tweak the defaults settings except the >> cache size. >> >> Try to keep also regular backups using SCRIPT TO. >> > > Well, backups are always a good idea... Do you recommend this for a > particular reason? > Thing is, I'm using H2 as embedded database for my product. It's going to > be shipped to thousands of users... > > >> Good luck with your migration. >> > > Thank you! > > And while I have your attention: > > org.h2.tools.Recover produces two files: a sql file and a .mv.txt file. > > What is the .mv.txt file good for? I couldn't find any documentation. > -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
