Hi Jonathan,
In the documentation for Sequoia, it describes using a table in the DB
for the log file. Is there any way to save this information to the disk?
If you are talking about the recovery log, it is stored in a dedicated
database instance, so it should be persisted on disk unless you are
using a in-memory database.
Is there more detailed documentation for setting up backups and
restores? Like how to set up the backups to happen at a regular
interval automatically? The admin guide shows a manual process for
backing up. I have to be able to automatically backup the DB, restore
backends after a failure, and purge the log file. My users cannot be
responsible for this management.
You can script the console and invoke the console through the crontab or
any automation mechanism. You can prepare the scripts for your users and
they can be invoked at will.
Also, how do I get a recovery log for each backend on a virtual
database? If I can’t back them up simultaneously, how can I restore
them? Does the log file record which backend corresponds to each
checkpoint?
There is one recovery log per virtual database per controller. The
controller keeps track of each checkpoint for each backend it manages
(in the backend table of the recovery log database). All backends
attached to the same controller share the same recovery log.
Hope this helps,
Emmanuel
--
Emmanuel Cecchet
FTO @ Frog Thinker
Open Source Development & Consulting
--
Web: http://www.frogthinker.org
email: [EMAIL PROTECTED]
Skype: emmanuel_cecchet
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
