Hi I have a scheduled backup running on a server that backs up to a network drive. For some reason the backup never runs, but the scheduled task says it was. Any idea why this is? Whenever I remote desktop to work on the server I just close it I don't log out (so the network drive stays mapped). I have had it working before but when I reconfigured the backup to change some settings it just doesn't work. Any help appreciated Thanks

I don't know, what backup program you're using but normally the backup program generates log files. Have you checked those log files to figure out what's going wrong? Also check the systems error logs.

Thanks for that. Sorry I forgot to mention I'm just using the Backup Utility that comes with Windows. I checked the event log, and there is a message at the start of the backup saying removable media entered running state, then 30 seconds later one saying it entered the stopped state. Would this be referring to the network drive? The network drive is mapped to an external HDD connected to another computer. If so, any idea how to stop this from happening? Thanks

So could it be, that you (the backup program) has to authenticate to the other computer? Create another small backup job for the same harddisk and schedule this to beginn in a few minutes. Lets see what happens.

I don't think so as I have successfully run this backup before (if I run the command in the task scheduler it works fine)

I thought it stops after 30 seconds? So if the job gets started and there is no error message in the backup log, I think you backup only files that have been changed. So I mean where the achive attribute is set. Could it be, that the files haven't been changed since the last backup means achive attribute is not set?

Nope there are definately changed files because I have created new ones for tests. The backup file doesn't even get created. I don't think it runs for 30 seconds, that was just a removable media event log message. If I manually run it then it works fine, but it doesn't appear to be running at all with the scheduled task, even though it says the task was run