What LMS 4.1 on Windows ProcessName is responsible for the DB Backup?

[waljohnson]

The DBBackup has failed and doesn't complete so the Lock remains even after Canceling the scheduled backup and the perl script still owns the lock file. Really don't want to shutdown all the processes/reboot the server..                  

[Vinod Arya]

In LMS no single process would show you for backup. As Backup is a perl script you would see perl running in Task Manager when Backup in initiated. When it is started, so that other backup doesnt conflict, it keeps a lock file, which ideally it should remove when backup is completed - successful or not. But sometime it may stay there in case of any issues.

You should find that lock file in $NMSROOT. You can simply manually delete that lock file. It wont require to restart any service. After that you can try to re-run the backup.

Try backup from CLI :

NMSROOT\bin\perl   NMSROOT\bin\backup.pl <directory>

example if LMS is installed in c:\program files\CSCOpx:

c:\progra~1\CSCOpx\bin\per   c:\progra~1\CSCOpx\backup.pl c:\LMS_Backup

If it is failing share NMSROOT\log\dbbackup.log for us to see the reason.

-Thanks

[waljohnson]

The backup.lock file is open in Perl so I can't delete it and there are two perl.exe processes running which I didn't want to just stop one or both using Task Manager.

Below is an excerpt from the end of the dbbackup.log file:

VALIDATE TABLE "DBA"."SysServicesEnum"

VALIDATE TABLE "DBA"."SystemComponent"

VALIDATE TABLE "DBA"."SYSLOG_20130303"

Primary key for "SYSLOG_20130303" has missing index entries

Primary key for "SYSLOG_20130303" has missing index entries

Primary key for "SYSLOG_20130303" has missing index entries

Primary key for "SYSLOG_20130303" has missing index entries

Primary key for "SYSLOG_20130303" has missing index entries

Primary key for "SYSLOG_20130303" has missing index entries

Primary key for "SYSLOG_20130303" has missing index entries

Primary key for "SYSLOG_20130303" has missing index entries

Primary key for "SYSLOG_20130303" has missing index entries

Primary key for "SYSLOG_20130303" has missing index entries

Primary key for "SYSLOG_20130303" has missing index entries

Primary key for "SYSLOG_20130303" has missing index entries

Primary key for "SYSLOG_20130303" has missing index entries

Primary key for "SYSLOG_20130303" has missing index entries

Primary key for "SYSLOG_20130303" has missing index entries

.

.

.

Primary key for "SYSLOG_20130303" has missing index entries

Primary key for "SYSLOG_20130303" has missing index entries

Primary key for "SYSLOG_20130303" has missing index entries

Primary key for "SYSLOG_20130303" has missing index entries

Primary key for "SYSLOG_20130303" has mis

Is there a way to remove "SYSLOG_20130303" from the DB?

[Joe_george]

You can remove this from the RME DB by using he SQL query. You can access DB by http://:1741/dbreader/dbreader.html.

But ideally it advised not to play with DB without TAC guidance. I think you should open a TAC case to solve this issue, they can even find a way if possible to fix w/o dropping this table.

Joe

CCNA | NMS Admin

[waljohnson]

Thanks Joe and I do intend on opening a TAC case.

Is the information on the dbreader url in the online LMS documentation, I only see a oneliner in the Admin - Understanding Admin Tasks documentation?

DBreader Access

You can run the DBReader utility from a Cisco Prime client to access the database and troubleshoot database issues.