|
I've been trying to set up and test to see how this live backup thing works and have been having trouble getting to backup utility to run to monitor the log. I type the following in a command window: dbbackup -l c:\backup\blog.log -c "uid=dba;pwd=mypswd;eng=mydb;dbn=mydb;links=tcpip" And all that happens is I get back the usage message. I am able to get a regular full backup to run. |
|
I am using SA 12 so it may not be exactly your case but can you try using the full path for dbbackup and the -y redirection? For instance: "C:\Program Files\SQL Anywhere 12\bin32\dbbackup" -c "UID=xxx;PWD=yyyy;DBN=mydbn;ENG=myeng;LINKS=tcpip;" -y "R:\APPS\DATABASE" |
dbbackup -c "uid=dba;pwd=mypswd;eng=mydb;dbn=mydb;links=tcpip" -l c:\backup\blog.log c:\backup Works for me in V10. |
|
Instead of the command line, you can set up events in Sybase Central with a schedule. The BACKUP statement cannot be used to start a live backup, only dbbackup can do that.
(28 Apr '12, 18:03)
Breck Carter
|
btw I'm using SQL Anywhere 11
Should be ...-l c:backupblog.log ...
Do you have several instances of SQL Anywhere installed (including very old versions like v5/v6), and may it be that an older dbbackup version may be called incidentally, as it appears earlier in the PATH environment variable? - If so, specifying the SQL Anywhere program path (as Derli has suggested) should resolve the issue.