Attempting a kill on remote save

[aknoll]

Hi,
running the group several times succesfull, since few days the "SaveGroupCompletion" gives me following result:

NetWorker Savegroup: (alert) Filesystem_Unix_Produktion completed, 2
client(s) (dubaan2, dubaan3 Failed)
Start time: Wed Jul 30 20:00:01 2003
End time: Wed Jul 30 21:28:33 2003

--- Unsuccessful Save Sets ---

* dubaan2:/var 1 retry attempted
* dubaan2:/var 30.07.2003 20:44:58 nsrexec: Attempting a kill on remote save
* dubaan2:/var aborted due to inactivity
* dubaan2:/usr/oracle 1 retry attempted
* dubaan2:/usr/oracle 30.07.2003 20:44:33 nsrexec: Attempting a kill on remote save
* dubaan2:/usr/oracle aborted due to inactivity

* dubaan3:/home 1 retry attempted
* dubaan3:/home 30.07.2003 20:49:35 nsrexec: Attempting a kill on remote save
* dubaan3:/home aborted due to inactivity

--- Successful Save Sets ---

dubaan2: / level=full, 819 MB 00:07:03 15546
files
dubaan2: /usr level=full, 1729 MB 00:15:34 37304
files
dubaan2: /cluster/members/member2/boot_partition level=full, 79 MB
00:03:28 35 files
dubaan2: /cluster/members/member3/boot_partition level=full, 40 MB
00:00:09 31 files
bak-mmp-01: index:dubaan2 level=full, 8521 KB 00:13:56 90
files

dubaan3: /baan4/b4npa level=full, 14 GB 01:21:54 410102
files
dubaan3: /baan4/b4cae level=full, 5683 MB 00:40:12 354420
files
dubaan3: /baan4/bms level=full, 20 GB 01:23:41 602662
files
bak-mmp-01: index:dubaan3 level=full, 321 MB 00:03:46 11
files

Both Clients are phsyical Nodes of the Tru64 Cluster.
What could be the real problem ??

Alfred

 

[purpaul]

Sounds like the savegrp inactivity timeout is up and it is killing the sessions.

You can either increase to a larger setting, or set it to 0 which means it doesnt time out.

You may need to look into why those sessions are timing out.

If backups are slow you can suspect networking issues.