Let's see if I can remember... your primary database resides on computer A, and you take a one-time full backup of the .db and .log files and copy them over to computer B... but don't do anything with them yet. Then, you start dbbackup -l running on computer B, connected over the interweb or whatever to the primary database on computer A. The dbbackup utility will then immediately copy over all the transaction log entries that were created since the full backup was taken, so it may be busy for a little while. Then it sits there, running forever, reading log entries and writing them to a local .log file on computer B.

Let's see if I can remember... your primary database resides on computer A, and you take a one-time full backup of the .db and .log files and copy them over to computer B... but don't do anything with them yet. Then, you start dbbackup -l running on computer B, connected over the interweb or whatever to the primary database on computer A. The dbbackup utility will then immediately copy over all the transaction log entries that were created since the full backup was taken, so it may be busy for a little while. Then it sits there, running forever, reading log entries and writing them to a local .log file on computer B.

I tried this option before, but the problem I saw is that the database on machine B only can recovery when the primary server stops. In standby servers, the database recovers whethever transaction log gets in the folder... it minimizes the time for recovery, because is almost up-to-date.

So, I am considerating the Mirror Server as my choice.
Do you have any document with step-by-step to build the Mirror Server on SQL Anywhere 12.0.1?

I don't think you can only "go live" with the database on machine B when the database server on machine A stops. You should be able to stop the "DBBACKUP -l" process and then reapply the log on the database on machine B. (But of course you might then loose further changes from A...)

The official docs for 12.0.1 do contain some tutorials on HA, cf. this doc page. - Have you tried these?

And Breck has a great tutorial on his blog on HA with v11. However, as the statements to config the servers have changed in v12, it might not be that appropriate for you.

I would update the tutorial if I could figure out the declarative versions of all the features formerly available only through command line options. The Old School stuff still works, and the New School stuff is... just... so... confusing... but that's what my tutorials are for, aren't they? Sigh :)

If running a live dbbackup does not satisfy your requirements then perhaps you should look at the High Availability option, aka database mirroring.

When using database mirroring the transaction log contents get copied to the mirror server either synchronously or asynchronously (i.e. configurable) and gets applied to the mirror copy of the database. When the primary server fails the mirror copy automatically takes over as the new primary thus minimizing downtime.

Just to add: with SA12 HA is not available for the Workgroup Editition, at least the Standard Edition is required. We tripped over that the first time we wanted to set it up. But using the Developer Edition will enable you to test all options.

I tried this option before, but the problem I saw is that the database on machine B only can recovery when the primary server stops. In standby servers, the database recovers whethever transaction log gets in the folder... it minimizes the time for recovery, because is almost up-to-date.

So, I am considerating the Mirror Server as my choice.
Do you have any document with step-by-step to build the Mirror Server on SQL Anywhere 12.0.1?