M
Michael Meyers-Jouan
To reply to me, please remove *nospam* from the E-mail
address.
Recently, Windows Update installed a fix that affected
the Background Intelligent Transfer Service (BITS). At
that point, ntbackup.exe stopped finding files to back up.
When I looked at the list of excluded files (Tools,
Options, Excluded Files tab), the first entry on the list
specified all files ("*") in the root folder ("C:\"), and
all sub-folders. This entry was labeled "BITS_metadata".
Attempts to delete the entry from within ntbackup failed.
While this entry was present, of course, any attempt to
run ntbackup caused the program to run and exit almost
immediately, generating a log file indicating that it
successfully backed up 0 files.
Somewhere along the lines, my attempts to fix this caused
something to change, and that exclude entry disappeared.
It was replaced by an entry that specified all files
("*") in one specific folder ("C:\Documents and
Settings\All Users\Application
Data\Microsoft\Network\Downloader\"). Once this change
showed up, ntbackup resumed normal operation.
A search of the Microsoft Knowledge Base turned up 839090:
You receive a "The process cannot access the file" error
message when you open a report file of a backup that was
completed while the Background Intelligent Service (BITS)
runs
This article describes a problem that occurs when there
is NO "BITS_metadata" entry in the exclude files for
ntbackup. However, I couldn't find anything in the
Knowledge Base that describes a situation in which the
entry excludes ALL files.
Has anybody else encountered this? Does anybody have any
idea what might have caused it?
address.
Recently, Windows Update installed a fix that affected
the Background Intelligent Transfer Service (BITS). At
that point, ntbackup.exe stopped finding files to back up.
When I looked at the list of excluded files (Tools,
Options, Excluded Files tab), the first entry on the list
specified all files ("*") in the root folder ("C:\"), and
all sub-folders. This entry was labeled "BITS_metadata".
Attempts to delete the entry from within ntbackup failed.
While this entry was present, of course, any attempt to
run ntbackup caused the program to run and exit almost
immediately, generating a log file indicating that it
successfully backed up 0 files.
Somewhere along the lines, my attempts to fix this caused
something to change, and that exclude entry disappeared.
It was replaced by an entry that specified all files
("*") in one specific folder ("C:\Documents and
Settings\All Users\Application
Data\Microsoft\Network\Downloader\"). Once this change
showed up, ntbackup resumed normal operation.
A search of the Microsoft Knowledge Base turned up 839090:
You receive a "The process cannot access the file" error
message when you open a report file of a backup that was
completed while the Background Intelligent Service (BITS)
runs
This article describes a problem that occurs when there
is NO "BITS_metadata" entry in the exclude files for
ntbackup. However, I couldn't find anything in the
Knowledge Base that describes a situation in which the
entry excludes ALL files.
Has anybody else encountered this? Does anybody have any
idea what might have caused it?