|
it
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Cannot backup system state since Server SP1 - Event ID 8019Backup reports the following error, and application log records EventID 8019.
This was working fine prior to SP1, however I now have 6 servers that cannot backup system state. "NTDS" has reported an error 0x800423f0. This is part of System State. The backup cannot continue. There is more to the solution than meets the eye
Check your scheduled Jobs, they must reference a bks file in the form "@c:\pathname\filename.bks" If your job is in the form C:\WINDOWS\system32\ntbackup.exe backup systemstate /n "Monday... you need to change it to C:\WINDOWS\system32\ntbackup.exe backup "@c:\pathname\filename.bks" /n "Monday When you apply the changes, you will probably need to add the job password again. Next Use NTBACKUP to load that bks selection file, and in the selections, as well as SYSTEM State ticked, a file on the same drive as your ADLOGs must be ticked, optionally tick a dummy file on all drives. If you were not using a selections file before, you need to save thse selections and go back to step 1 above to reference this file - note the "@" is ESSENTIAL, or you will just backup the bks file. Next Test run your sheduled Job I note that the Job type should be normal or copy e.g." /m normal" in the scheduled job command line, otherwise if the file is not changed since the last archive the attribute will not be set and this MAY cause the file to be ignored and the System state to fail as well as no shadow was created- I am not sure. |
|||||||||||||||||||||||