Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

NetBackup Exchange restore - ERR - unable to create object for restore

Created: 27 Jan 2013 • Updated: 28 Jan 2013 | 2 comments
Willie_SA's picture
This issue has been solved. See solution.

Error when restoring part of Exchange .

Extract from log - full log attached:

01/26/2013 22:07:34 - Error bpbrm (pid=25485) from client cprvnmsmcafee2: ERR - unable to create object for restore: Microsoft Information Store:\ (BEDS 0x0: )

01/26/2013 22:07:34 - Warning bpbrm (pid=25485) from client cprvnmsmcafee2: WRN - error writing file: C:\SG6 Recovery\ (err=WIN32 13: Unknown error)

01/26/2013 22:07:34 - Warning bpbrm (pid=25485) from client cprvnmsmcafee2: WRN - error writing byte: 0

01/26/2013 22:07:34 - Warning bpbrm (pid=25485) from client cprvnmsmcafee2: WRN - wanted buffer size: 60416

01/26/2013 22:07:34 - Warning bpbrm (pid=25485) from client cprvnmsmcafee2: WRN - error writing file: C:\SG6 Recovery\Logs_1358866814

01/26/2013 22:07:34 - Warning bpbrm (pid=25485) from client cprvnmsmcafee2: WRN - disk full at byte: 0

Comments 2 CommentsJump to latest comment

Marianne's picture

Please help us understand what ' restoring part of Exchange ' means?

Trying to restore Information Store to a Recovery Storage Group?

Which NBU version? Which Exchange version?

If 2007, see:

HOWTO TN: http://www.symantec.com/docs/TECH57346

Video:  http://www.symantec.com/tv/products/details.jsp?vid=754369875001

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

SOLUTION
Willie_SA's picture

Sorry for the limitid information - let me try and give you more.

The error occured during the restore of an Exchange Storage Group - SG06.

NBU server - UNIX master / media server - NBU 7.1

Exchange 2007.

The actual restore did work - but a utility(ESEUTIL) against the Exchange had to be completed before the actaul restored SG was usable again.

Although tests are still done to the effected users - it seems that everything is OK again.