Jayesh Mistry
New Member
Hi All,
I am hoping that someone maybe able to assist me here.
We have a Progress db that has been backed up each and every night for that last 15 years or so with no issues.
We are moving the db from one server to another - this is currently in UAT. So the first task is to ensure the back works.
The scipt below is a snippet of the bat file that carries out the backup.
The bat file is run via Task Scheduler.
When that task is auto-fired all commands in the bat file run in reasonable time, but then hangs when it runs the PROBCKUP command.
When the same script is run in Task Scheduler manually - it runs ok - and that PROBKUP command takes 7 mins to run.
When the bat file is run manually - again it takes 7 mins to run.
I am confused as to why the auto firing of the task scheduler is hanging on that command only - there are other commands in the bat file - like shutdown the db (dbman -stop dbName and proshut dbName)... Stop/starting the admin service (net stop "AdminService11.7(64 bit) ) etc
I want to send any errors from the PROBKUP to the log file - how do I do that & what is the syntax? I have not seen anything that will allow me to error check this command
echo %date% %time% --- START Backup >> c:\Logs\processes_log.txt
......
echo %date% %time% --- PROBKUP db >> c:\Logs\processes_log.txt
cmd /c %DLC%\bin\probkup dbPath\dbName B:\Backups\Live\dbName.bk
echo %date% %time% --- ALL DONE >> c:\Logs\processes_log.txt
We are on Progress 11.7.19.
The Task is run by an admin account, which is active and no issues with that account
Other tasks on the new server are running without issues - under the same admin account.
Many Thanks in Advance for any asistance.
Jayesh.
I am hoping that someone maybe able to assist me here.
We have a Progress db that has been backed up each and every night for that last 15 years or so with no issues.
We are moving the db from one server to another - this is currently in UAT. So the first task is to ensure the back works.
The scipt below is a snippet of the bat file that carries out the backup.
The bat file is run via Task Scheduler.
When that task is auto-fired all commands in the bat file run in reasonable time, but then hangs when it runs the PROBCKUP command.
When the same script is run in Task Scheduler manually - it runs ok - and that PROBKUP command takes 7 mins to run.
When the bat file is run manually - again it takes 7 mins to run.
I am confused as to why the auto firing of the task scheduler is hanging on that command only - there are other commands in the bat file - like shutdown the db (dbman -stop dbName and proshut dbName)... Stop/starting the admin service (net stop "AdminService11.7(64 bit) ) etc
I want to send any errors from the PROBKUP to the log file - how do I do that & what is the syntax? I have not seen anything that will allow me to error check this command
echo %date% %time% --- START Backup >> c:\Logs\processes_log.txt
......
echo %date% %time% --- PROBKUP db >> c:\Logs\processes_log.txt
cmd /c %DLC%\bin\probkup dbPath\dbName B:\Backups\Live\dbName.bk
echo %date% %time% --- ALL DONE >> c:\Logs\processes_log.txt
We are on Progress 11.7.19.
The Task is run by an admin account, which is active and no issues with that account
Other tasks on the new server are running without issues - under the same admin account.
Many Thanks in Advance for any asistance.
Jayesh.