On 23 Dec 2016, at 01:18, Vincent Sheffer wrote:

I’m trying to do automated incremental backups following these instructions:

https://www.monetdb.org/Documentation/UserGuide/FastDumpRestore

My question is whether why isn’t it enough to just stop the DB?

monetdbd will automatically start the DB, when it receives a client request to connect to DB, if DB is not started already. Therefore, you also need to lock the DB, so that no one else can (accidentally) start the DB, while you are backing-up the binary files.

Is the waiting for open sessions a courtesy or is it required that no statements are executing prior to shutdown? Is it similar for the shutdown command? It gives people in a session time to exit or something?

Again, these are to be automated at a time of night that queries should not be being executed.

Bottom line question: is it enough to stop and lock a database to ensure the binary backup will have no errors that prevent the backup from being restored or are the other steps required?

Basically yes (unless the database already contains corrupted data that haven’t been noticed). For data you really don’t want to loose, it’s advisable to also create SQL dump as back up once in a while. Jennie

Thanks, Vince

The information transmitted, including any attachments, is intended only for the individual or entity to which it is addressed, and may contain confidential and/or privileged information. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by individuals or entities other than the intended recipient is prohibited, and all liability arising therefrom is disclaimed. If you have received this communication in error, please delete the information from any computer and notify the sender. _______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list