LMS 3.1 Backup job Failing

Question

Hello,
We have LMS 3.1 installed and the backup is failing with the following message
[Tue Feb  8 09:20:26 2011]  ERROR(247): E:/Backup_3/backup.LOCK file exists
Most probably another backup process is running
[Tue Feb  8 09:20:26 2011]  Backup failed: 2011/02/08 09:20:26
I tried to do the following, but it didn't work:
1- Run again the backup job, but specify a new backup directory folder (ex: E:/Backup_4/). --> Did not work
2- - Stop the Deamon Manager service using: net stop crmdmgtd --> Did not work
     - Delete the backup.LOCK file from the E:/Backup_3/ folder
     - Restart the Deamon manager service using: net start crmdmgtd
     - Run the backup job again using the new Folder destination.
Please Advise,
Regards,

Answer 1

I am currently working on a same issue with LMS 3.1 on windows;
After stopping dmgtd have you been able to delete the backup.lock or have you restarted the server?
In my case I was not able to delete the file and it turned out dbvalid.exe blocked this. The backup seems to run without any problems. When the backup is done dbvalid.exe trys to verify the backup database files. This validation fails and dbvalid starts dbsupport.exe to get some detail information on the failure and trys to send them to Sybase support. You should find (several ?) crash files here: %ALLUSERSPROFILE%\Application Data\SQL Anywhere 12\diagnostics. dbsupport.exe seems to be started interactively and thus hangs up waiting for some user input...
In the crash file I see dfmInv mentioned as the database which did not pass dbvalid. I assume I will end up reinitializing the dfm databases to recover - but let's wait and see. I found some hints that there could be a bug with dbvalid.exe form Sybase- not sure if this is the culprit or a real DB error. What I found really strange is the cli of dbsupport.exe (see the option -gui at the end... )
D:\PROGRA~1\CSCOpx\objects\db\win32\dbsupport.exe" -crash "C:\Documents and Settings\All Users\Application Data\SQL Anywhere 10\diagnostics\SA10_20110215_040218_4348.crash_log" -crashpn "dbeng10" -crashsn "dbvdfmInvEng" -gui
Also, I would quickly backout the last know good backup from the backup directory - just in case... (the one before the failure raised the first time)