Batch job being executed on server

[steven888]

Hello,

I noticed there is a Windows batch program to delete and recreate a folder on daily basis running on the server.

This script is required as I back up my data to disk and it will first delete the previous backup before it starts a new backup

to ensure adequate disk space. I know the batch program is running because I can see the folder being created everyday at certain time.

However, when I check under Control Panel - Scheduled Task, I do not see the batch job being scheduled.

I have an external backup software but according to the person in charge, it is not calling this script.

How can I find out who trigger this batch program to run?

Thanks!

[jaclaz]

... and it will first delete the previous backup before it starts a new backup

to ensure adequate disk space.

If I may one of the strangest behaviour for a backup script I have ever seen, what happens if your PC crashes after the old backup has been deleted and before the new backup has been created?

What happens if you run AT or SCHSTASKS?

http://ss64.com/nt/at.html

http://ss64.com/nt/schtasks.html

If you know the name of the batch id run, you can anyway search the registry or the disk for it.

jaclaz

[Tripredacus]

I hope you mean that the "oldest" backup is deleted, not the "old" backup. That would make more sense.

Typically anything you see in schtasks *should* show up in Task Scheduler unless the task was created with an account that has different permissions than the one you are logged in as. Also, couldn't these tasks be assigned via AD or a remote system? For example, I know with Windows Server Backup, you can remotely manage the backup of other domain servers but I do not know if it would create tasks on the client or not.

[steven888]

Thanks everyone for the feedback.

Basically my backup strategy is to first copy the data to a local folder and later in the evening, another job will transfer the contents to a tape.

The deletion of the folder will only happen the next day before the new backup starts.

Anyway I managed to trace the execution of the batch job - it was started by an external OS command from SAP.