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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problem doing an exchange recovery

Status
Not open for further replies.

ee01akk

MIS
Dec 3, 2008
19
GB
Networker 7.3.4 server and Networker module for exchange 5.1.1.

Problem recovering log files- can you help?
 
You have an exchange Cluster and did not provide the -a switch with nsrexchrc.

Please dont provide .raw files, convert them with nsr_render_log myRaw.raw >Textfile.txt

to somethin eays readible. Not everyone has the render_logs command at hand or the time for converting.
And please provide more information what you want to do and what the problem is. Otherwise its difficult to help.
 
Hi,

We are using Windows 2003 x64 SP2, our Exchange infrastructure is 2007 SP1 with Rollup 3.

We upgraded the Networker module to version 5.1.1 on the 31st October so the “The feature "NetWorker Module for Microsoft Exchange Server/11" is not properly enabled for client uos-cl-ex7-l1.soton.ac.uk” errors from March and June are not applicable as they refer to an older version of the module and we were having some licensing issues at the time.

The output of the nsrlic –v command is attached as are the event logs.

The database we are trying to restore is 240GB and the servers are using the same network switches that have worked for previous restores many times before.

Thanks for your help.
 
 http://www.zshare.net/download/525285228ed459ee/
The errors I get are just like the following example from the attached file:

46842 1227615279 5 0 0 5812 8432 0 uos-msg00021-cp nsrxchrc 25 Not recovered: %s (%u.%u) 3 23 54 /Information Store/First Storage Group/E0000223E1E.log 5 10 1224962720 5 10 1224965177
46842 1227615279 5 0 0 5812 8432 0 uos-msg00021-cp nsrxchrc 25 Not recovered: %s (%u.%u) 3 23 54 /Information Store/First Storage Group/E0000223E1F.log 5 10 1224962720 5 10 1224965178
46842 1227615280 5 0 0 5812 8432 0 uos-msg00021-cp nsrxchrc 25 Not recovered: %s (%u.%u) 3 23 54 /Information Store/First Storage Group/E0000223E20.log 5 10 1224962720 5 10 1224965179
46842 1227615280 5 0 0 5812 8432 0 uos-msg00021-cp nsrxchrc 25 Not recovered: %s (%u.%u) 3 23 54 /Information Store/First Storage Group/E0000223E21.log 5 10 1224962720 5 10 1224965180



The recovery finishes but as it can’t recover the log files it can’t replay them and so the recovered data is useless.

I've attached the log file in text format as a ZShare upload.
 
 http://www.zshare.net/download/525342030b68b6c5/
In your log file is following entry:

46845 1227606502 1 0 0 5812 8432 0 uos-msg00021-cp nsrxchrc 28 Preallocating "%s" Size: %s 2 23 44 W:\RS1\Recovery Storage Group\RSGMailbox.edb 0 12 240670120944
46833 1227613837 5 0 0 5812 8432 0 uos-msg00021-cp nsrxchrc 60 %s(%d): XBSA error 0x%0.4x returned while getting XBSA data. 3 23 6 rcutil 1 3 524 1 1 3
38008 1227613837 5 0 0 5812 8432 0 uos-msg00021-cp nsrxchrc 2 %s 1 24 92 Internal system error, please see nsr\applogs\xbsa.messages on the client system for reason.

So you should taken a look into the xbsa.messages file on your exchange server.

xbsa errors are often network problems,
in your case it might be due to insufficient storage capacity !

Check your W:\ volume : is there enough capacity for your *.edb and the log files ?


 
The W:\ drive is a 10GB mount point with a 500GB LUN mounted to W:\RS1 for restoring a database and a 136GB LUN mounted to W:\RS1\Logs. The database we are trying to recover is 240-ish GB plus a maximum of 136GB of log files (as the Log LUN is that size) so we have plenty of spare space.
 
Latest xbsa.messages:

XBSA-1.0.1 LNMs_2007.Build.294 6872 Sun Nov 16 00:02:23 2008 _nwbsa_close_create_object_session: BSA_RC_ABORT_SYSTEM_ERROR System detected error due to savefile_fini() failure, typically caused by bad network hardware (NICs, routers, etc). Operation aborted
XBSA-1.0.1 LNMs_2007.Build.294 5268 Wed Nov 19 16:36:30 2008 _nwbsa_read_asdf_section: BSA_RC_ABORT_SYSTEM_ERROR System detected error due to asdf_read_and_unwrap_section. Operation aborted
XBSA-1.0.1 LNMs_2007.Build.294 4052 Thu Nov 20 12:00:38 2008 _nwbsa_read_asdf_section: BSA_RC_ABORT_SYSTEM_ERROR System detected error due to asdf_read_and_unwrap_section. Operation aborted
XBSA-1.0.1 LNMs_2007.Build.294 8472 Thu Nov 20 17:43:27 2008 _nwbsa_read_asdf_section: BSA_RC_ABORT_SYSTEM_ERROR System detected error due to asdf_read_and_unwrap_section. Operation aborted
XBSA-1.0.1 LNMs_2007.Build.294 5572 Fri Nov 21 13:15:10 2008 _nwbsa_read_asdf_section: BSA_RC_ABORT_SYSTEM_ERROR System detected error due to asdf_read_and_unwrap_section. Operation aborted
XBSA-1.0.1 LNMs_2007.Build.294 8356 Fri Nov 21 20:26:09 2008 _nwbsa_is_retryable_error: received a retryable network error (Severity 0 Number -13): retry needed
 
I think networker has a problem crossing the mountpoint borders.

Retry the restore with traditional LUNS :
Take your 500 GB Lun create mount it as volume eg. W:\
and recreate your RSG on W:\ the retary the restore.
 
If we were to fall back to the previous version of the Networker Module (5.1) as the backup I am trying to recover was backed up using v5.1.1 will the older module recover the data correctly?

Also, is there a command that can check to see if the backup on the Networker server contains the log files my recovery is trying to restore?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top