Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NSR 6.2 backing up Exchange 2003: svmain(908): begin_mb_item_backup()

Status
Not open for further replies.

libove

MIS
Apr 9, 2002
56
US
I have Legato Networker v6.2 installed on a Windows Server 2003 system also running Exchange Server 2003. Exchange module v4.0 is installed to back up Exchange. I'm seeing this:

NetWorker Savegroup: (alert) Exchange completed, 1 client(s) (exchangeserver.mydomain.org Failed)
Start time: Wed Mar 17 15:00:02 2004
End time: Wed Mar 17 15:02:59 2004

--- Unsuccessful Save Sets ---

* exchangeserver.mydomain.org:MSEXCH:MB savegrp: suppressed 7 lines of output
* exchangeserver.mydomain.org:MSEXCH:MB svmain(908): begin_mb_item_backup() failed with status = 0x80040108
* exchangeserver.mydomain.org:MSEXCH:MB profile(134): MAPI Profile: Name does not exist or was not opened.
* exchangeserver.mydomain.org:MSEXCH:MB The XBSA transaction was not committed; the save operation did not complete.
* exchangeserver.mydomain.org:MSEXCH:MB Found an orphan file D:\win32app\nsr\tmp\nsrxch01860_0000.tmp
* exchangeserver.mydomain.org:MSEXCH:MB Found an orphan file D:\win32app\nsr\tmp\nsrxch01860_0001.tmp
* exchangeserver.mydomain.org:MSEXCH:MB Found an orphan file D:\win32app\nsr\tmp\nsrxch02572_0001.tmp
* exchangeserver.mydomain.org:MSEXCH:MB Found an orphan file D:\win32app\nsr\tmp\nsrxch02572_0002.tmp
* exchangeserver.mydomain.org:MSEXCH:MB Found an orphan file D:\win32app\nsr\tmp\nsrxch05980_0000.tmp
* exchangeserver.mydomain.org:MSEXCH:MB Found an orphan file D:\win32app\nsr\tmp\nsrxch05980_0001.tmp
* exchangeserver.mydomain.org:MSEXCH:MB Backup operation finished with errors.

--- Successful Save Sets ---

* exchangeserver.mydomain.org:MSEXCH: nsrxchsv_ese.exe Version: 4.0.0.44 Supporting Exchange 2000 and Exchange 2003
* exchangeserver.mydomain.org:MSEXCH: System Version: 5.2 Build 3790
* exchangeserver.mydomain.org:MSEXCH: ESEBCLI2.DLL Version: 6.5.6944.0
* exchangeserver.mydomain.org:MSEXCH: Performing an Exchange save operation; save level is Incremental (Legato Backup Level: incr).

* exchangeserver.mydomain.org:MSEXCH: Parsing parameters from the command line
* exchangeserver.mydomain.org:MSEXCH: Processing storage group "First Storage Group"
* exchangeserver.mydomain.org:MSEXCH: Backup storage group First Storage Group to exchangeserver.mydomain.org
* exchangeserver.mydomain.org:MSEXCH: Backup of logs for storage group First Storage Group was successful
* exchangeserver.mydomain.org:MSEXCH: Completed backup of First Storage Group Status: 0x0
* exchangeserver.mydomain.org:MSEXCH: The operation completed successfully.
* exchangeserver.mydomain.org:MSEXCH: exchangeserver.mydomain.org: MSEXCH:IS 30 MB 00:00:34 6 file(s)
exchangeserver.mydomain.org: index:exchangeserver.mydomain.org level=9, 311 MB 00:01:09 159 files
exchangeserver.mydomain.org: bootstrap level=full, 3408 KB 00:00:08 154 files


What does that error mean, and what should I do about the "orphan" file warnings?

Thanks
-Jay
 
Your Remote User entry for the client obviously does not have the right security properties ...

- List Contents
- Read Properties
- Administer Information Store
- View Information Store Status
- Receive As
- Send As

However, if all of the above settings are in place and the backup still fails,
start nsrexecd on the Exchange server with the server name.
Example:

net start nsrexecd -s NW_server_name

Later change the service parameters appropriately.
 
DavinaTreiber posted that Networker 6.2 does not support Windows Server 2003.

The error message:
* exchangeserver.mydomain.org:MSEXCH:MB svmain(908): begin_mb_item_backup() failed with status = 0x80040108
* exchangeserver.mydomain.org:MSEXCH:MB profile(134): MAPI Profile: Name does not exist or was not opened.
* exchangeserver.mydomain.org:MSEXCH:MB The XBSA transaction was not committed; the save operation did not complete.

.. relates to the Exchange backup, taken with Exchange module v4.0.

So, does Networker itself being v6.2 actually bear on this problem?

Thanks
-Jay
 
Possibly not, but if you are using a version of NetWorker that was produced before Windows 2003 and Exchange 2003 even existed, there are many seemingly unrelated issues that might just impact on the problem - you just don't know since the versions have not been tested together. Basically, without compatible versions, all bets are off. I would recommend you upgrade NetWorker to 7.1.1 before continuing.

I don't know what the correct version of the Exchange module is suitable for Exchange 2003. Have you checked? Also, is that version of the Exchange module compatible with NetWorker 6.2?
 
I believe that Exchange Module v4.0 is compatible with Networker 6.2. I'll try an upgrade of the Network server to 7.1, though as this has worked before without the error, I'm not sure that's it at all.

To help with the diagnoses, how do I prevent Networker from "suppressing" lines of output, as it likes to do in its completion reports?

Thanks
-Jay
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top