• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1192
  • Last Modified:

Windows Server Backup Fails "System Cannot Find File Specified"

Server 2008 R2 Standard SP1
DC, Exchange, DNS, DHCP

A few weeks ago my local backups began to fail on my DC. The error thrown is simply "The system cannot find the file specified" on my data partition. Windows partition, System Reserved partition both back up fine, most of the data drive backs up fine but about 75% of the way through it seems to fail.
0
TechGuy_007
Asked:
TechGuy_007
  • 7
  • 6
1 Solution
 
rindiCommented:
Run a chkdsk /f /r on the partition that fails (the server will probably need to reboot to do this, and depending on the size of the partition and the number of errors to fix, this can take a long time, so do this during "off" hours).
0
 
noxchoGlobal Support CoordinatorCommented:
If it does not show a specific file which it refers to then running CHKDSK on that system is recommended.
If CHKDSK does not fix the problem then try to take backup to different storage, sometime MS Backup behaves this way if storage has write/read issues.
0
 
TechGuy_007Author Commented:
Will try CHKDSK tonight and post results. Thank you for the help!
0
 
TechGuy_007Author Commented:
Chkdsk did not help, I reinstalled WSB yesterday and the backup did complete successfully last night. I will keep an eye on it for a few days and close this if reinstalling the  WSB feature ends up being the fix.
0
 
noxchoGlobal Support CoordinatorCommented:
So the reinstalling should normally clean up the logs and events plus generate new GUID storage. Did you try simply point it to different storage? That could have helped as well.
Frankly speaking I would recommend you using third party backup solution. They are more convenient and reliable than WSB. Yes, they cost money but at the end you understand that third party solution is worth of its price.
Symantec, Paragon, Acronis, Shadow Protect, Veeam etc.
0
 
TechGuy_007Author Commented:
So, after reinstalling, the backups worked for 4 days then failed again with the same error last night. I'm running chkdsk on the destination drives now. I'm already using two different destination drives that are switched each day, so I don't think it's an issue with those. Would like to avoid a 3rd party solution if possible, but the option is on the table.
0
 
noxchoGlobal Support CoordinatorCommented:
Try cleaning up the logs and events of WBS.
0
 
TechGuy_007Author Commented:
Just inside event viewer? I did that today, will post results tomorrow.
0
 
noxchoGlobal Support CoordinatorCommented:
Yes, the last result information is gathered by WSB from Event Viewer. Sounds lame - but it is so. I have had this experience where I had to clean up WSB Events in Event Viewer - Applications - Backup (if I remember it correctly now).
0
 
TechGuy_007Author Commented:
Yep, backup successful last night. So it's the logs in Event Viewer causing issues? Will that one cleanup do the trick, or will I have to do this as a matter of routine? Also - thank you for the help!
0
 
noxchoGlobal Support CoordinatorCommented:
As far as my experience says it works till the backup process breaks up due to some reason like drive disconnection or too much data in temp folder. Ones the problem is resolved you have to clean up the events again so that WSB stops its memory flashbacks about last broken process.
And you are welcome!
0
 
noxchoGlobal Support CoordinatorCommented:
Did the issue reoccur?
0
 
TechGuy_007Author Commented:
Gave up - been using Veeam for weeks with no issue. Working on switching all of my servers over now. WSB seemed to work so well for years; lately I've been having issues with it across many environments - mostly on 2008 / 2011 machines.
0
 
noxchoGlobal Support CoordinatorCommented:
Unfortunately for Microsoft the WSB is not the prio 1 in development.
1
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

  • 7
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now