NetBackup for Microsoft Exchange Server GRT backup fails to catalog database mailboxes if users mixed between parent/child domains

NetBackup for Microsoft Exchange Server GRT backup fails to catalog database mailboxes if users mixed between parent/child domains

Article: 100043063
Last Published: 2020-03-27
Ratings: 5 0
Product(s): NetBackup

Problem

NetBackup for Microsoft Exchange Server GRT backup fails to catalog database mailboxes if users mixed between parent/child domains

 

Cause

This issue can arise when there are multiple mailboxes owned by users that are part of a primary domain or child domain within one specific database. The Netbackup Exchange Agent can be seen to catalog one group or the other, but the result leaves the Customer unable to browse (ncflbc) for the remaining mailboxes within the Database. There are no errors seen in backup or restore but certain mailboxes will be missing for the GRT restores.

The customer may be able to invoke the Exchange Powershell Console and compare the different outputs:

a) > get-Mailbox -database <database name>

This will show the users that will part of a particular domain (default Primary Domain Users)

b) > get-Mailbox -database <database name> -IgnoreDefaultScope

This will show ALL mailboxes within the database, whether part of a primary domain or child domain tree.

 

In 8.2, the Registry entry below must be applied (No EEB is required)

1. Set the following value in the Windows Registry for each Exchange server that acts as a NetBackup client:

Key: HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\BEDS\Engine\Exchange
Value Type: DWORD
Value Name: PowerShellOptions
Value: 0

2. Restart the NetBackup Discovery Framework service on each client.
3. Wait for the "exchange.dat" and "exchange.xml" files for every client to be updated on the Master Server in the NetBackup\db\discovery folder.
4. Run a fresh new Backup and then proceed to Browse the new image & verify that all the mailboxes are shown.

 

In 8.1.2 EEB is required & the Registry entry below must be applied

If these symptoms are encountered, please contact Veritas Technical Support, referencing this article ID and Etrack 3969148 to obtain a fix for this issue.

1. Install EEB from 3969148

2. Set the following value in the Windows Registry for each Exchange server that acts as a NetBackup client:

Key: HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\BEDS\Engine\Exchange
Value Type: DWORD
Value Name: PowerShellOptions
Value: 0

3. Restart the NetBackup Discovery Framework service on each client.
4. Wait for the "exchange.dat" and "exchange.xml" files for every client to be updated on the Master Server in the NetBackup\db\discovery folder.
5. Run a fresh new Backup and then proceed to Browse the new image & verify that all the mailboxes are shown.

 

In 8.1.1 an EEB is required

If these symptoms are encountered, please contact Veritas Technical Support, referencing this article ID and Etrack 3953626 to obtain a fix for this issue.

 

Solution

Currently in the 8.2 release, monad initialization defaults to *not* ViewEntireForest unless the configuration in the Registry overrides it. In future GA releases, a code change is being implemented to the default behavior. This will allow the successful browsing and restores of the mailboxes.


 

References

Etrack : 3983907 Etrack : 3953626 Etrack : 3969148

Was this content helpful?