I have several clients whom I have configured Zip Backup to CD to run as part of a scheduled nightly backup job. This scheduled job is a batch file, so I am invoking Zip Backup to CD from the command line.
The issue that is occurring is when a backup job doesn't complete properly this is somehow flagged so that the next night when Zip Backup to CD runs, it pauses to tell the user that the previous backup did not complete and prompts the user to either continue that job or cancel it.
This isn't convenient since most of these scheduled backup jobs run at 1:00AM when no one is around. Is it possible to force Zip Backup to CD to ignore the completion status from the last run so that it simply runs the specified backup job, and doesn't prompt the user to either continue or cancel that previous backup?
Or, can you tell me what parameter in the config file is getting set so that it knows that the last job did not complete correctly? I can then write a perl script that would reset that parameter so that it appears that last run completed successfully and this will no longer be an issue.