LMS 3.0.1 backup failure

Answered Question
Aug 27th, 2008

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?

Attachment: 
I have this problem too.
0 votes
Correct Answer by Joe Clarke about 8 years 3 months ago

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

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Joe Clarke Wed, 08/27/2008 - 19:53

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?

Correct Answer
Joe Clarke Thu, 08/28/2008 - 08:44

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

mburrell5 Thu, 08/28/2008 - 16:05

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

Joe Clarke Thu, 08/28/2008 - 16:47

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

mburrell5 Thu, 08/28/2008 - 16:53

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

Actions

This Discussion