dbbackup.exe oddity

[justin_willey]

The v16 docs give a sample command line of:

dbbackup -l path-on-secondary-computer\\filename.log -c "connection-string"

but when I try this format I get a usage error. I find that I have to put the folder for the live log file at the end of the command line:

dbbackup -l path-on-secondary-computer\\filename.log -c "connection-string" path-on-secondary-computer

Oddly, if I do something like this

dbbackup -l c:\\temp\\MyLogFile.log  -c "ENG=SA16;DBN=v16test;UID=DBA;PWD=****" c:\\nottemp

it works fine despite the contradictory paths - putting the file MyLogFile.log in the folder c:\\nottemp

v16.0.0.2018

[Breck_Carter]

The docs specify

   dbbackup -l filename ... target-directory

so it appears to be ignoring your first directory

   dbbackup -l ignore-this-directory\\filename ... target-directory

This wouldn't be the first time SQL Anywhere has ignored extra "noise" 🙂

[justin_willey]

Thanks Breck, I should have been clearer 🙂 My (minor) moan is that the docs are inconsistent:

http://dcx.sybase.com/index.html#sa160/en/dbadmin/dbbackup.html

says

dbbackup -l filename ... target-directory

but

http://dcx.sybase.com/index.html#sa160/en/dbadmin/da-backup-dbs-4978684.html

says

dbbackup -l path-on-secondary-computer\\filename.log -c "connection-string"

[Breck_Carter]

Many of the examples have never been tested, alas.

[Breck_Carter]

@Graham... the second answer appeared when I edited the first one.