Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
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.
0 
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
0
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.
0
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)
0
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?
0
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
0
All the signs the scheduled job is not running under an account with the correct privledges.
As a test run it under the admin account to see if it works.
0
I am logged in as admin and everything is running under the admin account.
I checked the event log on the computer running the backup, and it has (in order that they occur):
1. Event ID 7035, Service Control Manager, Removable Storage Service was successfully sent a start control
2. Event ID 7036, Service Control Manager, Removable Storage Service entered the running state
3. Event ID 98, Removable Storage Service, RSM was stopped
4. Event ID 7036, Service Control Manager, Removable storage service entered the stopped state
These all happen close together. This give anyone any ideas?
The mapped drive is connecting using authorization details of the local admin on that computer. Everything on the server is done under local admin account.
I have successfully had this backup running before, and nothing has changed. I just deleted the old schedule and created a new one with different settings (e.g. run at different time, append instead of replace).
0
have you confirmed both accounts use the same password?
again, all the signs of scheduled account issues.
0
I do not suggest having the backups try to write to a drive letter.
Instead of telling the backup to write to "S:\Backups\Daily.bkf", have it write to a UNC path, "\\Server\Backups\Daily.bkf" (as an example).
Assume that I already did an Internet search.
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
