ntbackup destroyd AD

[Petr Sedlak]

Hi,

I have this problem:
It somehow happened that during the backup procedure (using ntbackup,
Windows 2000 Server) the Active Directory got destroyed. It was working - in
the way that everyone could log in - but some accounts just couldn't be
changed (passowrd, name, etc.) because it said the AD was corrupted.
Recovering from the backup tape helped for a while but then the same thing
happend. So I had to build the AD manualy from teh scratch. This problem
happened twice (second time even after applying the ntbackup.exe patch) now
it works but I feel rather uncomfortable about that... It said there could
be some kind of hardware problem but I tested All harddrives (RAID5) as well
as tape drive and there was no error.

Has anybody experienced anything similar?
Does anybody know what could possibly be the problem?
I don't understand why it happened - ntbackup should just read from the disk
and write to tape - how can it afect in any manner data on the hard drive?
The backup is configured as Sytem State backup in ntbackup. Is there any
other and better way how to backup AD (apart from using BDC) either by
better configuration of ntbackup or by using other backup software?

Thanks

 

[Lanwench [MVP - Exchange]]

I've never seen NTBackup do anything to AD....what did you see in your
system event logs when this happened?

 

[Petr Sedlak]

From that moment there was enormous number of errors in system log saying:
"The SAM database was unable to lockout the account of Administrator due to
a resource error, such as a hard disk write failure (the specific error code
is in the error data) . Accounts are locked after a certain number of bad
passwords are provided so please consider resetting the password of the
account mentioned above."

And in directory service log:
"NTDS (584) NTDSA: The database page read from the file
"C:\WINDOWS\NTDS\ntds.dit" at offset 401408 (0x0000000000062000) for 8192
(0x00002000) bytes failed verification due to a page checksum mismatch. The
expected checksum was 3893727725 (0xe81591ed) and the actual checksum was
3893727661 (0xe81591ad). The read operation will fail with error -1018
(0xfffffc06). If this condition persists then please restore the database
from a previous backup. This problem is likely due to faulty hardware.
Please contact your hardware vendor for further assistance diagnosing the
problem."



"Lanwench [MVP - Exchange]"

 

[Enkidu]

The messages all appear to point the finger at the hardware. What sort
of RAID do you have? Hardware or software? If you have hardware RAID,
is it correctly configured? Do you have the latest drivers?

Cheers,

Cliff

From that moment there was enormous number of errors in system log saying:
"The SAM database was unable to lockout the account of Administrator due to
a resource error, such as a hard disk write failure (the specific error code
is in the error data) . Accounts are locked after a certain number of bad
passwords are provided so please consider resetting the password of the
account mentioned above."

And in directory service log:
"NTDS (584) NTDSA: The database page read from the file
"C:\WINDOWS\NTDS\ntds.dit" at offset 401408 (0x0000000000062000) for 8192
(0x00002000) bytes failed verification due to a page checksum mismatch. The
expected checksum was 3893727725 (0xe81591ed) and the actual checksum was
3893727661 (0xe81591ad). The read operation will fail with error -1018
(0xfffffc06). If this condition persists then please restore the database
from a previous backup. This problem is likely due to faulty hardware.
Please contact your hardware vendor for further assistance diagnosing the
problem."



"Lanwench [MVP - Exchange]"

I've never seen NTBackup do anything to AD....what did you see in your
system event logs when this happened?

 

[Petr Sedlak]

Yes, that's what I thought as well but everything semms to be O.K. In
addition there was always problem only with AD not with other data. We have
hardware RAID (Intel) which is running in more than 20 other servers at our
customers with the same firmware and drivers. But I think that is the last
thing where I can do something - so I'll probably update the RAID card
firmware and see what happens.

The messages all appear to point the finger at the hardware. What sort
of RAID do you have? Hardware or software? If you have hardware RAID,
is it correctly configured? Do you have the latest drivers?

Cheers,

Cliff

From that moment there was enormous number of errors in system log saying:
"The SAM database was unable to lockout the account of Administrator due to
a resource error, such as a hard disk write failure (the specific error code
is in the error data) . Accounts are locked after a certain number of bad
passwords are provided so please consider resetting the password of the
account mentioned above."

And in directory service log:
"NTDS (584) NTDSA: The database page read from the file
"C:\WINDOWS\NTDS\ntds.dit" at offset 401408 (0x0000000000062000) for 8192
(0x00002000) bytes failed verification due to a page checksum mismatch. The
expected checksum was 3893727725 (0xe81591ed) and the actual checksum was
3893727661 (0xe81591ad). The read operation will fail with error -1018
(0xfffffc06). If this condition persists then please restore the database
from a previous backup. This problem is likely due to faulty hardware.
Please contact your hardware vendor for further assistance diagnosing the
problem."



"Lanwench [MVP - Exchange]"
<[email protected]> pí¹e v diskusním
pøíspìvku news:O7%[email protected]...

I've never seen NTBackup do anything to AD....what did you see in your
system event logs when this happened?

Petr Sedlak wrote:
Hi,

I have this problem:
It somehow happened that during the backup procedure (using ntbackup,
Windows 2000 Server) the Active Directory got destroyed. It was
working - in the way that everyone could log in - but some accounts
just couldn't be changed (passowrd, name, etc.) because it said the
AD was corrupted. Recovering from the backup tape helped for a while
but then the same thing happend. So I had to build the AD manualy
from teh scratch. This problem happened twice (second time even after
applying the ntbackup.exe patch) now it works but I feel rather
uncomfortable about that... It said there could be some kind of
hardware problem but I tested All harddrives (RAID5) as well as tape
drive and there was no error.

Has anybody experienced anything similar?
Does anybody know what could possibly be the problem?
I don't understand why it happened - ntbackup should just read from
the disk and write to tape - how can it afect in any manner data on
the hard drive? The backup is configured as Sytem State backup in
ntbackup. Is there any other and better way how to backup AD (apart
from using BDC) either by better configuration of ntbackup or by
using other backup software?

Thanks