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?
Solved! Go to Solution.
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
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?
08-27-2008 09:29 PM
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
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?
08-28-2008 04:47 PM
Something must have not shutdown properly before, keeping the IPM database open.
08-28-2008 04:53 PM
Thanks for your help, will see how the regular scheduled backup goes
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide