It seems: The Exchange 5.5 version of the dll needs to be in the path for NTBackup to support Exchange 5.5
The Exchange 2k version of the dll lives in exchange\bin and needs a key in the registry for NTBackup to support Exchange 2k. If you have both the 5.5 dll in the path and the 2k dll in the registry NTbackup shows both "Microsoft Exchange" and "Microsoft Exchange Server" targets in the backup selection list. If you select a 2k exchange store to backup NTBackup seems to use the 5.5 dll to access it, skips the target and returns unrestorable/corrupt database errors. If you rename the 5.5 dll, one of the exchange targets disappears from NTbackup and it works. Cheers, Marty -----Original Message----- From: STEVE BROOK [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 31, 2001 10:34 PM To: MS-Exchange Admin Issues Subject: RE: [Fixed] RE: Exchange 2000 Backup permissions? Sorry, I must have missed part of this thread (or deleted it). What is the deal with the Exchange Client dll from version 5.5? what is it doing to stop the backups? I have just done a migration to 2000 and am having problems getting a decent backup -----Original Message----- From: Marty Richards [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 31, 2001 7:12 AM To: MS-Exchange Admin Issues Subject: [Fixed] RE: Exchange 2000 Backup permissions? Cool. The problem was an exchange 5.5 dll called edbbcli.dll in the winnt\system32 directory. Renamed this and the backup is running now... well, NTBackup is, I haven't tried veritas yet. Cheers, Marty List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
