Hi, > I can't use SCRIPT SQL statement because > it provides transactionally inconsistent backup in case of MVCC mode.
No, it shouldn't. Is that documented somewhere? Could you post the link? > According to H2 roadmap: > >>> MVCC: support transactionally consistent backups using SCRIPT > > As I know another way to backup H2 database online is to use BACKUP > SQL statement. As far as I understand the statement locks database > before coping db files. Could you please clarify how locking of > database is performed in this case? What will happen with new and > existing connections if BACKUP statement will lock the database? Will > these connections be rejected or will they wait until lock will be > removed? It's required for me to use backup method which doesn't > reject other connections (new or existing connections must wait until > backup is finished). > > Thank you, > Alex > > > > -- > 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. > > -- 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.
