Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
811
Views
0
Helpful
6
Replies

LMS 3.0.1 backup failure

Go to solution
mburrell5
Level 1
Level 1

‎08-27-2008 04:48 PM

Am preparing to upgrade from LMS 3.0.1 to 3.1. At present the backup process fails due to a lock file issue. There is no lock file present now. It is obviouslt related to the backup process itself. I have attached the dbbackup.log file. Any ideas?

Labels:
13064-dbbackup.log
0 Helpful
1 Accepted Solution

Accepted Solutions

Go to solution
Joe Clarke
Cisco Employee
Cisco Employee
In response to mburrell5

‎08-28-2008 08:44 AM

The problem is not the transaction log. It may be the database. Try this. Set the Daemon Manager service to Manual, then reboot. When the server restarts, run the backup.pl script from the command line:

NMSROOT\bin\perl NMSROOT\bin\backup.pl ...

If this does not work, you can try reinitializing the ipm database:

NMSROOT\bin\perl NMSROOT\bin\dbRestoreOrig.pl dsn=ipm dmprefix=Ipm

View solution in original post

0 Helpful
6 Replies 6

Go to solution
Joe Clarke
Cisco Employee
Cisco Employee

‎08-27-2008 07:53 PM

The problem appears to be with the IPM database. It is either corrupt, or the transaction log is damaged. With all of LMS shutdown, what are the list of contents under NMSROOT\databases\ipm?

0 Helpful

Go to solution
mburrell5
Level 1
Level 1
In response to Joe Clarke

‎08-27-2008 09:29 PM

Attached is print screen of the folder contents. Do you need to drill down further

157 KB
0 Helpful

Go to solution
Joe Clarke
Cisco Employee
Cisco Employee
In response to mburrell5

‎08-28-2008 08:44 AM

The problem is not the transaction log. It may be the database. Try this. Set the Daemon Manager service to Manual, then reboot. When the server restarts, run the backup.pl script from the command line:

NMSROOT\bin\perl NMSROOT\bin\backup.pl ...

If this does not work, you can try reinitializing the ipm database:

NMSROOT\bin\perl NMSROOT\bin\dbRestoreOrig.pl dsn=ipm dmprefix=Ipm

0 Helpful

Go to solution
mburrell5
Level 1
Level 1
In response to Joe Clarke

‎08-28-2008 04:05 PM

Tried the first half of your suggestion - ran the backup.pl script and it works - a full backup was done. What does this mean?

0 Helpful

Go to solution
Joe Clarke
Cisco Employee
Cisco Employee
In response to mburrell5

‎08-28-2008 04:47 PM

Something must have not shutdown properly before, keeping the IPM database open.

0 Helpful

Go to solution
mburrell5
Level 1
Level 1
In response to Joe Clarke

‎08-28-2008 04:53 PM

Thanks for your help, will see how the regular scheduled backup goes

0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents