Granular Restore on Exchange 2007 Issue

[CoreyR]

We just configured GRT for our Exchange 2007 SP2 RU5 CCR environment using NetBackup 7.1.  When I try to restore a mailbox folder for a user, the restore starts fine and begins restoring items, then I see a message logged on the Exchange server:

Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9646
Date:  11/29/2011
Time:  10:57:53 AM
User:  N/A
Computer: EXCHMBSERVER1
Description:
Mapi session "/o=***/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=bricklevel" exceeded the maximum of 250 objects of type "objtMessage".

At that point all other items fail to restore with the message logged on the NBU Status Console:

ERR - unable to create object for restore: {Mailbox Item Path}, rai error = 17

[Marianne]

Seems the SOURCE is MSExchangeIS .

NBU is failing because of that.

Google search of "Event Source: MSExchangeIS Event ID: 9646" finds Eventid.net, Exchange forum,  and Microsoft KB articles, such as this one: http://support.microsoft.com/kb/830836 and http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=6.5.6940.0&EvtID=9646&EvtSrc=MSExchangeIS&LCID=1033  and http://forums.msexchange.org/m_200046300/mpage_1/key_/tm.htm#200046300

[CoreyR]

I agree, but for some reason, the netbackup service account I'm using for the restore is exceeding the object limit and causing the error which should not be happening.  The restore works fine and if I choose under 250 messages to restore it succeeds.  Once I go over the 250 message count, the restore errors out.  So why is this limit being reached on the restore.  I have over 6,000 users on my email system and the only time I see this message is when I try to do a granular restore.

[Marianne]

PLEASE have a look at those links that I've posted. It is an Exchange limit, not NBU...

[CoreyR]

Is it normal to hit this limit when doing a granular restore though?  The articles all point to it being a client problem.  In this case, the granular restore is doing the restore using the MAPI interface, so it is the client in this case.