1) backup database directory 'c:\Monday\' wait before start
wait after end transaction log truncate

2) backup database directory 'c:\logs\18\' wait after end
transaction log only

They look OK.

However... I've had bad experiences with the "wait" clauses, the
symptom being "wait forever" because some steenking connection remains
in progress. I'm of the opinion a backup should never ever wait,
backups are important. I also avoid truncate, choose rename instead,
then you keep everything... disk space is cheap, recovering your
sanity can be expensive.

Although it doesn't use the BACKUP statement (with VERY good reasons,
IMO), and it only does full backups, you might be interested in the
multi-generational technique shown in this blog entry...
http://sqlanywhere.blogspot.com/2009...revisited.html

Someday, I'll post a generic command file that includes incremental
log-only backups... someday

Breck



On 8 Dec 2009 14:04:19 -0800, Tom Mangano wrote:

--
Breck Carter - Blog: http://sqlanywhere.blogspot.com/

SQLA questions and answers: http://sqla.stackexchange.com

RisingRoad helps SQL Anywhere developers make better databases
http://www.risingroad.com/
Breck.Carter at gmail

Breck Carter [TeamSybase] wrote:

Fully agreed - it's just nasty if your nightly backup hangs (i.e. is
waiting)...
Yeah, Breck, incremental development of incremental backup solutions -
seems appropriate

Volker