It's "dbbackup.log" in NMSROOT\CSCOpx\log\ (on Windows) or /var/adm/CSCOpx/log/ (on Solaris). The "casuser" must have cron access on Solaris to be able to utilize the scheduled backup feature.
It sounds like your LMS is on Windows? Does casuser have access to Windows AT service/facility? That appears to be the only prerequisite to schedule the backup. You may want to check Windows' Event Viewer for any security warning when your attempt fails.
Another thread with the similar issue to yours just got bumped up. I think the hints and tips sprinkled throughout there may be useful to resolving your issue, such as checking stdout.log for errors, particularly concerning casuser access to cmd.exe:
Hmmm, I thought two posters there said they couldn't schedule. Oh well, could you post your NMSROOT/MDC/tomcat/logs/stdout.log after a failed scheduling of backup, anyway?
according to the return code (retVal=143) I would say your schedule fails while executing the following command :
cmd.exe /c crontab.cmd
with crontab.cmd being lokated in NMSROOT\bin
and cmd.exe should be set in %ComSpec% variable of the OS;
open a DOS box and run it from there, - it should just tell that it is looking for the at command and return the table with the scheduled jobs, like this:
E:\PROGRA~1\CSCOpx>cmd.exe /c crontab.cmd
E:\PROGRA~1\CSCOpx>IF EXIST E:\WINDOWS\System32\at.exe set atcommand=E:\WINDOWS\System32\at.exe
Status ID Day Time Command Line
1 Each Su 12:00 AM E:\PROGRA~1\CSCOpx\conf\backupsch.bat
if it fails have a look if at.exe exists in the system32 folder and casuser has full access to it:
(this is tested in crontab.cmd)
@jclarke or anybody who is interested in it... (NMSROT\cgi-bin\dbadmin\pdbadmin\schCommon.pl)
- in "schCommon.pl" the line 46 is a match like this :
until ($line =~ /---/ || $line == "");
It seems that they just want to get the array of scheduled tasks in @lines and get rid of the command lines (see output above). But because there is a blank line after each line there is a match with the first item in @lines (a blank line). So @lines contains the same as before just not the first blank line...
Can this also cause any problems when scheduling backups?