LMS 3.1: Backup done, but process still running

Unanswered Question
Aug 26th, 2009
User Badges:

I started a manual backup yesterday afternoon, planning to upgrade the CM and DFM modules. Today, I saw that the backup had been created but nothing in the dbbackup.log file (0 byte in size). I tried to run backup again and got an error message. I checked the dbbackup.log again -- this time the file is 2527057 bytes long and at the end of it I see this:

[Tue Aug 25 19:49:46 2009] Backing up database dfmInvDb:SQL Anywhere Command File Hiding Utility Version

SQL Anywhere Backup Utility Version

(1073 of 1070 pages, 100% complete)

Database backup completed

SQL Anywhere Command File Hiding Utility Version

[Wed Aug 26 14:51:54 2009] ERROR(247): F:/CW-Backup/backup.LOCK file exists

Most probably another backup process is running

[Wed Aug 26 14:51:54 2009] Backup failed: 2009/08/26 14:51:54


email=[email protected]


So it seems to me that the database backup has been completed yesterday but the processes are still running -- I checked and found these:

$ ps xa -W | grep db

23572 0 0 23572 ? 0 19:49:47 E:\PROGRA~1\CSCOpx\objects\db\win32\dbvalid.exe

17604 0 0 17604 ? 0 19:49:47 E:\PROGRA~1\CSCOpx\objects\db\win32\dbeng10.exe

5280 0 0 5280 ? 0 19:49:48 E:\PROGRA~1\CSCOpx\objects\db\win32\dbsupport.exe

Any idea why? How do I remedy this? Can I just kill those processes?

Thanks in advance for helping.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Joe Clarke Wed, 08/26/2009 - 11:45
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

This is something we're seeing a lot of lately. Basically, the DFM INV database gets corrupt periodically. This is due to a bug in Sybase, and is fixed with the version of Adaptive Server Anywhere shipping in LMS 3.2.

To temporarily solve this, you need to either restore LMS from a known good backup, or reinitialize the dfmInv database:

NMSROOT\bin\perl NMSROOT\bin\dbRestoreOrig.pl dsn=dfmInv dmprefix=INV

To recover from the hung backup, shutdown Daemon Manager, then kill off the remaining database processes. At that point, you can either run the restore, or reinitialize the INV database.


This Discussion