Has anyone encountered this problem?  I assume that TSM also uses the same
native Win2K API?

If not, then maybe this should be a heads up?


http://www.wininformant.com/Articles/Index.cfm?ArticleID=21351

The AD Backup Bug: Monster in the Closet?
As we all know, making reliable backups is one of the most important tasks
a network administrator faces daily. With that in mind, I want to share
some rather disturbing information I've come across--information that
directly affects those of you who run Windows 2000 networks based on
Active Directory (AD).
At a recent conference, I spoke to a senior engineer for Aelita, an
independent software vendor (ISV) that produces Win2K and Windows NT
administration and migration tools. During that conversation, the engineer
asked whether I had encountered or heard about a major bug related to
backing up AD. I told him I had run into a few puzzling situations on my
lab network when I ran AD backups and subsequently had problems restoring
them, but I hadn't heard about any specific bugs related to the problem.
The engineer told me that during Aelita's development of ERDisk for Active
Directory (ERDisk/AD), the company's new AD backup product, engineers
discovered that roughly half of all AD backups resulted in corrupt backup
copies that, if restored, caused the directory services on the restored
domain controller to be unstartable. Upon further investigation, they
discovered that the bug wasn't unique to Aelita's software and seemed to
involve a bug in the native API Win2K provides for performing AD backups
and restores. Thus, this problem affects all software that uses this
native API, which includes Win2K's built-in NT Backup utility and most, if
not all, third-party backup software (e.g., Computer
Associates's--CA's--ARCserve, VERITAS's BackupExec, and Aelita's
ERDisk/AD).