Hi,

My question is:

does anyone know how DBBackup -l will behave if it can't
write an update to the back up copy of the Transaction Log
on a remote machine, e.g. because of disk full or disk
failure?

the background is:

We're proposing to use DBBACKUP -l to create a live backup
of a transaction log on a remote server to aid disaster
recovery and to monitor the connection between the server
hosting the database and the server hosting the backup copy
of the transaction log so that we can alert sys=admin if
this connection is lost.

Our customer has raised the question though which is, 'if a
write to the backup of the transaction log fails will the
sys-admin still be notified because the connection will be
lost?'.

Whilst ensuring free disk space and handling disk failures
are sys-admin and server design issues, it would help me if
I could answer the customer's question.

Thanks,

Keith

This is with SQLAnywhere 7.0.4 on Windows NT4

Apologies for missing this from my first post.

K
<KeithAB> wrote

The question I have revolves around the error dragging the engine down. If
a 'mirror' log has an issue it drags the engine down with it so if a 'live'
log has an issue would it drag the engine down as well?

Darren Cameron

"Keith Alexander-Buckley" <Keith.Buckley (AT) automationPartnership (DOT) com> wrote in
message news:3fd89d96$1 (AT) forums-1-dub (DOT) ..

We believe not, that's why we're intending to do things this way rather than
use a mirror.

K

"Troy Coombs" <coombst (AT) quorumis (DOT) com> wrote