Hello all, We use H2 (1.4.200) extensively in production environments. Our backup mechanism consists of:
- stopping the process - backing up a directory tree including hundreds/thousands of H2 databases - starting the process Bringing the process down is because of the fact that the H2 databases can not be backed up on the file system level when they are still open. For some of the environments the down-time is becoming an issue and we are thinking of using the H2 "BACKUP TO xxx" to push out all backups from inside the process itself and subsequently backing up the rest of the files. Is there any risk in using the BACKUP command with databases being in (heavy) use? Any increased chance of database corruption? Will it dramatically slow down database access? If any of the H2 experts could reflect on this that would be great. And if anyone can share any experience in this area that would be great also. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/b4e6a5c8-1696-43e1-a384-74fc2af22b3fn%40googlegroups.com.
