System State Backup fails with file in use error

  • Thread starter Thread starter T0GGLe
  • Start date Start date
T

T0GGLe

Hi,

every time i try to back up active directory on a DC in our
enterprise, the backup process falls over on the same locked folder
each and every time and I don't know what to do about it.
I run the windows backup tool, select system state backup, backup to
file, then hit backup now.
The process runs through fine then hits the following directory :-

c:\winnt\sysvol\domain\do_not_remove_ntfrs_preinstall_directory

and then drops out an estimated 200Mb short of the total. Therefore I
do not have a full system state backup. I'm using Microsoft's own
fcuking tool and I do not have a full system state backup!!!! How
annoying is that????? And they wonder why we get annoyed with their
software?!!?

Does anyone have any idea what i can do please? I do have access
rights to that directory as I can browse to that folder and have added
in my user as having rights to that folder...just in case i put
everyone full control on it just to see if that would work but no.

OS is 2003

Thx.
 
c:\winnt\sysvol\domain\do_not_remove_ntfrs_preinstall_directory

Ok, that dir/file is related to (bookkeeping for) the File
Replication Service so it looks like you may have
some sort of FRS (failure to replicate?) problem but
I have never seen that stop a System State Backup.

Have you tried typing something like this into Google:

[ do_not_remove_ntfrs_preinstall_directory "System State" ]

Maybe adding a few quoted words from the exact error dialog
message.
 
That was a cracking search Herb, I must have got mine wrong before
when i searched so thx.

http://support.microsoft.com/?id=822132

Above is the link to the MS page for the info re this problem,
unfortunately though i have to contact MS for a fix for this.

I will update this post to let people know the final resolution to
this problem.
 
That was a cracking search Herb, I must have got mine wrong before
when i searched so thx.

http://support.microsoft.com/?id=822132

Above is the link to the MS page for the info re this problem,
unfortunately though i have to contact MS for a fix for this.

I will update this post to let people know the final resolution to
this problem.
Click to expand...

Ok just to let you people know the solution/update to this. The link
above is to the correct MS article and the solution is to phone MS to
get the hotfix from them. If the hotfix sorts the problem for you then
you won't be charged, however if it doesn't and your problem requires
further assistance then you may well be. It did seem to fix the
problem for me though. The server will require a reboot after you have
installed the hotfix.
 
Good job on updating this when you found the fix, man.

(I have been of "news" for about 10 days and so late responding,
sorry.)
 
Back
Top