Hi Aldo,
By looking at the checkpoint audit trail I can inferr that each time
backup_online() is run, it will create a checkpoint.
It also makes sense from an intuitive standpoint.
However, by looking at the docs, I found this snippet:
SQL> backup_context_clear ();
SQL> checkpoint;
SQL> backup_online ('virt-inc_dump_#', 150);
( from: http://docs.openlinksw.com/virtuoso/
databaseadmsrv.html#backup )
Note the explicit call to checkpoint.
What's the official answer?
It has implications when trying to restore from backup + audit trail (
to find the point in which they match ).
Actually backup_context_clear and backup_online both do an implicit
checkpoint and if CheckpointAuditTrail is enabled this already
switches to a new transaction log file.
The backup_context_clear () command should ONLY be used when you want
to start a complete new full backup of your database.
Repeated calls to
backup_online ('virt_inc_dump_#', 1000000);
insert more data in the database
delete some data from the database
backup_online ('virt_inc_dump_#', 1000000);
will only backup any changes.
This backup_online command can be put into the virtuoso scheduler, so
at regular intervals the incremental backup is updated and new backup
sequence files are created.
Since backup_online does an implicit checkpoint before temporarily
disabling further checkpointing while the backup is running, there is
no need to perform an explicit call to checkpoint.
However it does NO harm if you do.
Patrick
