I suggest you take a look at the Sybase ASE System Administration
Guide - available at Sybase's website for some suggestions on backup and
> We're going to have a ASE NT server in the field and need to make it as
> self-sufficient as possible. One issue is preventing the transaction
> logs from filling and, essentially, shutting down the system. We've
> identified two options, which are listed below. We'd appreciate any
> suggestions for other methods or reasons to consider one over the other.
> 1. Mirror the entire database to a different physical disk on a separate
> controller and set sp_dboption <dbname>, "trunc log on chkpt", true.
> (Does this obviate the need for data dumps?)
Mirroring protects against media failure on either your primary or
secondary device. This is not the same as, nor a replacement for, doing
backups or data dumps. You should schedule regular (nightly? weekly?)
database dumps. You can go with "trunc log on chkpt" combined with
thresholding if you don't care about recoverability between full dumps.
> 2. Set a threshold on each transaction log that will initiate a dump of
> the offending log.
This is ok if you don't care about recoverability between full dumps -
I realize that you want minimal maintenance for this server. Unless you
don't care at all if this server is recoverable upon failure, you should
have some means to rebuild the server.