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!

Save group didn't complete and idle 1

Status
Not open for further replies.

plugin1

Technical User
Sep 22, 2010
12
US
Hi,

We have backup server running on Sun solaris 10 with Networker version 7.4. Every weekend it goes idle after running for some duration during the full backup. Though it says running I don't see any activity. Details as below. The completed volume is still in the drive.

I'm not able to restart and it says the savegroup is already running.

My only choice to terminate the group and start the savegroup again or restart the networker services again (sometimes).

Let me know what is would be idle solution to fix the issue? Am I missing something?

inactivity timeout: 30;
File inactivity threshold: 30;
File inactivity alert threshold: 30;

drive 3 (/dev/rmt/3cbn) slot 17: CCL106 (mounted)

Code:
SunOS xxxxxx 5.10 Generic_142900-13 sun4v sparc SUNW,SPARC-Enterprise-T5220

Code:
Up since: Wed Jan 18 05:58:47 2012                Version: Sun StorageTek(TM) Enterprise Backup 7.4.5,REV=726 Network Edition/85

Sessions:

Messages:

 Sun 03:22:48 write completion notice: Writing to volume CCL106 complete
 Sun 23:59:00 savegroup alert: Group Dev Server aborted, savegrp is already running
 Mon 02:15:00 savegroup alert: Group Lab Servers aborted, savegrp is already running

Pending:

Code:
ps -ef | grep nsr
    root 29396 29135   0   Jan 18 ?         444:36 /usr/sbin/nsr/nsrmmd -n 4
    root 10390 29131   0   Jan 21 ?           0:00 /usr/sbin/nsr/save -s xxxxxxx -S -g Dev Server -LL -f - -m xxxx
    root 10392 29135   0   Jan 21 ?           0:01 /usr/sbin/nsr/savegrp Lab Servers
    root 29392 29131   0   Jan 18 ?           0:16 /usr/sbin/nsr/nsrlcpd -s xxxxx -N 1 -n 1
    root 10382 29131   0   Jan 21 ?           0:00 /usr/sbin/nsr/save -s xxxxx -S -g Dev Server -LL -f - -m xxxxx
    root 29388 29135   0   Jan 18 ?           1:13 /usr/sbin/nsr/nsrmmgd
    root 29393 29135   0   Jan 18 ?         214:14 /usr/sbin/nsr/nsrmmd -n 1
    root 29131     1   0   Jan 18 ?           4:46 /usr/sbin/nsr/nsrexecd
    root 29147 29135   0   Jan 18 ?           1:39 /usr/sbin/nsr/nsrmmdbd
    root 10381 29131   0   Jan 21 ?           0:00 /usr/sbin/nsr/save -s xxxxx -S -g Dev Server -LL -f - -m xxxxx
    root 29149 29135   0   Jan 18 ?           4:07 /usr/sbin/nsr/nsrjobd
    root 10396 29131   0   Jan 21 ?           0:00 /usr/sbin/nsr/save -s xxxxx -S -g Dev Server -LL -f - -m xxxxx
    root 10391 29131   0   Jan 21 ?           0:00 /usr/sbin/nsr/save -s xxxxx -S -g Dev Server -LL -f - -m xxxxx
    root 29135     1   0   Jan 18 ?           5:17 /usr/sbin/nsr/nsrd
    root 10388 29131   0   Jan 21 ?           0:00 /usr/sbin/nsr/save -s xxxx -S -g Dev Server -LL -f - -m xxxxxx
    root 29399 29135   0   Jan 18 ?         598:58 /usr/sbin/nsr/nsrmmd -n 6
    root 10756 29135   0   Jan 21 ?           0:03 /usr/sbin/nsr/savegrp Dev Server
    root 10389 29131   0   Jan 21 ?           0:00 /usr/sbin/nsr/save -s xxxxx -S -g Dev Server -LL -f - -m xxxxx
    root 10387 29131   0   Jan 21 ?           0:00 /usr/sbin/nsr/save -s xxxxx -S -g Dev Server -LL -f - -m xxxxx
    root 10380 29131   0   Jan 21 ?           0:00 /usr/sbin/nsr/save -s xxxxx -S -g Dev Server -LL -f - -m xxxxx
    root 29397 29135   0   Jan 18 ?         156:51 /usr/sbin/nsr/nsrmmd -n 5
    root 10379 29131   0   Jan 21 ?           0:01 /usr/sbin/nsr/save -s xxxxx -S -g Dev Server -LL -f - -m xxxxx
    root 10383 29131   0   Jan 21 ?           0:00 /usr/sbin/nsr/save -s xxxxx -S -g Dev Server -LL -f - -m xxxxx
    root 10384 29131   0   Jan 21 ?           0:00 /usr/sbin/nsr/save -s xxxxx -S -g Dev Server -LL -f - -m xxxxx
    root 29148 29135   0   Jan 18 ?           0:23 /usr/sbin/nsr/nsrindexd
    root 16103 16092   0 09:35:29 pts/1       0:00 grep nsr
    root 29394 29135   0   Jan 18 ?         186:35 /usr/sbin/nsr/nsrmmd -n 2
    root 29395 29135   0   Jan 18 ?         152:54 /usr/sbin/nsr/nsrmmd -n 3
 
Version 7.4 is very old and contains some bugs. It is out of support.
If you are running solaris 8 on your backup server cannot upgrade beyond 7.4 SP5 but zhis was a pretty stable release.
You need an upgrade enabler to run this version.

If you have maintenance and a newer solaris upgrade to 7.6.2.7
to get this releases look at ftp://ftp.legato.com/pub/NetWorker/Cumulative_Hotfixes/7.4

respective newer solaris upgrade to 7.6.2.7
to get this releases look at ftp://ftp.legato.com/pub/NetWorker/Cumulative_Hotfixes/7.6/old_7.6.2.7

7.6.3.1 is also an option but be careful ...

Enjoy
 
Finding the reason is not that simple. If possible, you should update - the latest versions have a much better error reporting and built-in capabilities like 'jobkill'.

One thing i would never do is to use (group) names with spaces. This could cause more problems than expected.
 
Thank you so much a060463xyz and 605 for your reply. I'll seriously consider your recommendations.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top