Unsolved
This post is more than 5 years old
27 Posts
0
1083
June 28th, 2012 18:00
Savegroup failure Windows Corp Completed/Aborted
I am a rookie on this software.
I got a save group completion alert and it said that 1 client failed - how can fnd the job and see what failed.?
EMC Network 7.4.5
Is there a way to display more log entires?
Please advise - I am viewing this in the Monitoring window > Logs
I did seee this on the report that was sent.
* mail001.com:MSEXCH:IS savegrp: suppressed 71 lines of output.
* mail001..com:MSEXCH:IS 46776:nsrxchsv: Backup database: DB_1 {7F80C9BF-1D42-4C2E-9773-23317D367CD6}
* mail001..com:MSEXCH:IS 46783:nsrxchsv:nsresesv(2520): XBSA error 0x0003 returned while creating XBSA object.
* mail001.com:MSEXCH:IS 38008:nsrxchsv:Internal system error, please see nsr\applogs\xbsa.messages on the client system for reason.
* mail001.com:MSEXCH:IS 46778:nsrxchsv:Error saving GUID for database DB_1
* mail001..com:MSEXCH:IS 46774:nsrxchsv:The backup of SG_1 failed; status is 0x00000003.
* mail001.com:MSEXCH:IS 46767:nsrxchsv:Completed backup of SG_1 Status: 0x00000003
* mail001..com:MSEXCH:IS The system cannot find the path specified.
* mail001.com:MSEXCH:IS 46885:nsrxchsv:Backup operation finished with errors. No savetime was sent.
* mail001..com:MSEXCH:IS 43709:nsrxchsv:Stop time: Fri Jun 29 00:57:40 2012
* mail001..com:MSEXCH:IS
Looks like it failed on the IS store?
Thanks.
nmc2
268 Posts
0
June 28th, 2012 21:00
Hello John,
Can you check is there any error message in "C:\program files\legato\nsr\applogs\xbsa.messages" on client.
Paste the message here.
Regards,
Prajith
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
June 30th, 2012 09:00
During the IS store backup MS API returned error where something specified could not be found. What exactly we do not know as that was not passed by API. You can check with Echange guys if they can dig more into their logs.
CarlosRojas
1.7K Posts
0
July 1st, 2012 02:00
Hi JohnLeonard,
This looks to me at first sight as a timeout. Have you already in place the TCP/IP values to avoid these timeouts?:
To avoid timeouts please do as follows in NetWorker and Exchange servers:
1.- Group Inactivity Timeout is set to "0" in the Exchange client configuration in NMC.
2.- Add the TCP/IP settings as described in the article above, and if it still fails I would suggest to add the following values in Client and Server:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\TcpWindowSize=256000
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\GlobalMaxTcpWindowSize=16777216
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveInterval=1000
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveTime=600000
On Solaris:
#ndd -get /dev/tcp tcp_keepalive_interval
7200000
#ndd -set /dev/tcp tcp_keepalive_interval 3360000
These changes will require a reboot.
Also, you need to check the module logs, and these are:
C:\Program Files\Legato\nsr\applogs\XBSA.messages
C:\Program Files\Legato\nsr\applogs\nsrxchsv.raw
The first one is clear enough, but the second one you will have to render it to make it readable.
Anyway you will find the failure within the Application event logs in event viewer, also check out the system ones in case there is something wrong with Exchange services, as this could be also a crash in the IS.
Thank you.
Carlos.