I'm sorry I misinterpreted your original post. You weren't clear regarding what action of yours was failing. Your broader screenshot shows that you did get mailboxes catalogued, and now you have told us that the action that failed is expanding the mailbox.
NetBackup performs many steps in this operation. There can be different reasons for it to fail. Problems with nbfsd or permissions are not the only possibilities. We need to start with the logs and see which step failed.
First, I have some preliminary questions:
1. What versions of NetBackup and Exchange do you have, and what Exchange-related EEBs do you have installed, if any?
2. If you make the left panel of the BAR GUI wide enough to see the full mailbox names, are the aliases correct? You don't need to post a screenshot, just check that if you expect "Joe Smith [jsmith]" you don't have something weird inside the brackets.
Now to the logs.
1. Do you get an ncflbc log on one of your Exchange servers? If no, check the bpdbm log as described below. If yes, continue here.
2. Turn up logging on the client where you get the ncflbc log.
If nblbc executes on the same client where you are running the Backup, Archive, and Restore (BAR) application, select File / NetBackup Client Properties from the menu. On the Troubleshooting tab of the pop-up window, set the General logging level to 2 and the Verbose level to 5.
If your ncflbc log appears on a different Exchange server, go to the NetBackup console on the master server, and set the two logging levels for that client under client host properties.
3. Start with a fresh BAR GUI session. (Close it and reopen it.) Repeat the step that fails.
4. Look in the ncflbc log for error details. It may be ending with exit status 103. Look upstream for the failure that leads to that status.
NCF components use Veritas Unified Logging, which is hard to read in its raw form. Run vxlogview to format it for reading. Since we don't need pid / tid info, you can leave out the -d option, as follows:
>cd <install location>\NetBackup\bin
>vxlogview -i 351 >..\logs\ncflbc\nblbc.txt
If in step 1, you cannot find an ncflbc log on any client, check the bpdbm log. For this you need logging at level 3 or more on the master server.
2a. Look for ImageListFiles::executeQuery.
This method is called every time you expand a node in the BAR GUI. It logs its input as "pattern =". Advance through these entries until the pattern is your mailbox name. This is the bpdbm execution that returns your "database system error" status 220. If you are not getting an ncflbc log anywhere, look here for the reason.
