Highlighted
axavier1
2 Iron

Strange group behavior.

Hi,

last week my Exchange IS and PF group do not stop after the backup finished, they keep running. Searching daemon.log I found this:

nsrd: runq: NSR group EXCHANGE_DIARIO_BASE exited with return code 5.

anyone get this erro before ?

Looking nsrxchsv.log all IS and PF backup finished without erros, the message below occurs after the bootstrap backup.

My Networker server is 7.3.2 Jumbo Update 1

Regards,

Anderson Stockler Xavier
Tags (1)
Reply
10 Replies
Highlighted
ble1
6 Indium

Re: Strange group behavior.

Restart NW server application - that should clear status of the group. Do you have any additional information in applogs on EXCH client?
Reply
Highlighted
axavier1
2 Iron

Re: Strange group behavior.

Hi Hrvoje,

the group runs every day at 6 pm and I need to restart NW server every noon because the group still running I also try to clean nsr/tmp but I get the same problem. I think some problem with savegrp and console because savegrp exited with code 5 and can´t pass any status to console, when I try to stop the group I received the message that the group must be started either automatically or from the GUI and must be currently running in order to be stopped.

On nsrxchgsv.log all backups finished without errors and the most stranger about this error is that later I do mailbox backup and mailbox backup group finished ok.

[2568] 04/11/07 20:18:44 The backup of Remoto completed successfully; backup level is Full (Legato Backup Level: full).
[2568]
04/11/07 20:18:44 Completed backup of Remoto Status: 0x00000000
The operation completed successfully.
[2568] 04/11/07 20:18:45 Resource monitor thread termination status: 0x0
[2568]
04/11/07 20:18:45 The backup of Information Store on MSXCHSVR completed successfully.
[2568] 04/11/07 20:18:45 flocos1: MSEXCH:IS 74 GB 02:18:41 45 file(s)
[2568]
04/11/07 20:18:45 Stopping performance monitor update thread.
[2568] 04/11/07 20:18:45 Performance monitor update thread terminating
[2568]
04/11/07 20:18:45 Sent savetime 1176333525 to savegrp.
[2568]
04/11/07 20:18:45 Completion time Wed Apr 11 20:18:45 2007

Regards,

Anderson Stockler Xavier
Reply
Highlighted
ble1
6 Indium

Re: Strange group behavior.

The log looks fine. Tell me, when this hanging happens:
a) do you see on server savegrp process
b) do you see hanging process on client
c) is there tcp connection established/idle between server and client
Reply
Highlighted
axavier1
2 Iron

Re: Strange group behavior.

> The log looks fine. Tell me, when this hanging
happens:
a) do you see on server savegrp process


No, I think this is the problem the savegrp hang and don´t pass any state to console, and they after save bootstrap, all backup finished successfully but after Networker save bootstrap the savegroup hangs, this happen only with this group.

04/11/07 20:00:09 nsrd: MSXCHSVR:MSEXCH:IS/Matriz M-Z done saving to pool 'EXCHANGE DIARIO' (EXCHDIARIO.009) 21 GB
04/11/07 20:00:13 nsrd: MSXCHSVR:MSEXCH:IS/Remoto saving to pool 'EXCHANGE DIARIO' (EXCHDIARIO.009)
pools supported: EXCHANGE DIARIO;
04/11/07 20:18:44 nsrd: MSXCHSVR:MSEXCH:IS/Remoto done saving to pool 'EXCHANGE DIARIO' (EXCHDIARIO.009) 9788 MB
pools supported: EXCHANGE DIARIO;
04/11/07 20:19:16 nsrd: write completion notice: Writing to volume EXCHDIARIO.009 complete
04/11/07 20:20:10 nsrd: NSRSVR:bootstrap saving to pool 'EXCHANGE DIARIO' (EXCHDIARIO.009)
pools supported: EXCHANGE DIARIO;
04/11/07 20:20:49 nsrmmdbd: media db is saving its data. This may take a while.
04/11/07 20:20:50 nsrmmdbd: media db is open for business.
04/11/07 20:20:51 nsrd: NSRSVR:bootstrap done saving to pool 'EXCHANGE DIARIO' (EXCHDIARIO.009) 21 MB
04/11/07 20:20:53 nsrd: runq: NSR group EXCHANGE_DIARIO_BASE exited with return code 5.
pools supported: EXCHANGE DIARIO;
04/11/07 20:21:23 nsrd: write completion notice: Writing to volume EXCHDIARIO.009 complete


> b) do you see hanging process on client

No

> c) is there tcp connection established/idle between
server and client


No
Reply
Highlighted
ble1
6 Indium

Re: Strange group behavior.

Try to setup no index save in group properties - it might help.
Reply
Highlighted
axavier1
2 Iron

Re: Strange group behavior.

no index save is enable in this group.
Reply
ble1
6 Indium

Re: Strange group behavior.

What is the module version you use and saveset for these backups?
Reply
Highlighted
axavier1
2 Iron

Re: Strange group behavior.

hmm, version 4.1.0.148, I will schedule update for version 4.1.0.473 I hope the upgrade resolve this issue, and I use this savesets:

MSEXCH:IS
MSEXCH:PF
Reply
Highlighted
ble1
6 Indium

Re: Strange group behavior.

My first suggestion is to apply latest build for 4.1 and second suggestion would be to test this backup with client parallelism 1 if upgrade won't help (or have IS and PF backed up separately and not at the same time).
Reply