You can use a live backup to provide a redundant copy of the transaction log. This copy can be used to restart a secondary system in case the primary system running the database server becomes unusable. A live backup runs continuously, terminating only if the server shuts down. If you suffer a system failure, the backed up transaction log can be used for a rapid restart of the system. However, depending on the load that the server is processing, the live backup may lag behind and may not contain all committed transactions.
You should normally run the dbbackup utility from the secondary computer.
If the primary computer becomes unusable, you can restart your database using the secondary computer. The database file and the transaction log hold the information needed to restart.
For more information about live backups, see Protecting against total computer failure.
You carry out a live backup of the transaction log by using the dbbackup utility with the -l option.
Set up a secondary computer from which you can run the database if the online computer fails. For example, ensure that you have SQL Anywhere installed on the secondary computer.
Periodically, perform a full backup to the secondary computer.
dbbackup -c "UID=DBA;PWD=sql;ENG=testsrv;DBN=test;LINKS=tcpip" c:\backup
Run a live backup of the transaction log to the secondary computer.
dbbackup -l path\file-name.log -c "connection-string"
Regularly run the dbbackup utility from the secondary computer.
If the primary computer becomes unusable, the database can be restarted using the secondary computer. The database file and the transaction log hold the required information needed for a restart.