ashxos

updated

18 years ago

A

ashxos

142 Posts

0

9157

March 28th, 2009 00:00

Job aborted due to inactivity

Hi All,

After upgrading from 7.3.2 to Networker 7.5, our backup jobs are getting failed

I am attaching the logs of Failed Job.

What will be the reason?

NDMP Backup :
==============
savegrp: suppressed 2 lines of verbose output
42910:nsrndmp_save: Performing Non-DAR Backup..
42952:nsrndmp_save: encshare.encnet.com:/PRDHFS NDMP save running on 'encsafe.encnet.com'
7136:nsrndmp_save: (interrupted), exiting
42751:nsrndmp_save: Tape server halted: The backup is aborted by operator.
42619:nsrndmp_save: NDMP Service Warning: Backup was aborted
42617:nsrndmp_save: NDMP Service Log: server_archive: emctar vol 1, 302622 files, 0 bytes read, 64310845440 bytes written

42913:nsrndmp_save: Save session closed with NW server successfully

aborted due to inactivity



LAN Backup :
==============
1) Cannot determine status of backup process. Use mminfo to determine job status.
aborted due to inactivity

2) 1 retry attempted
aborted due to inactivity
  • Meko2

    4 Posts

    5167

    0

    Posted March 28th, 2009 06:00

    I ran into this immediately after going to 7.5 as well.

    EMC had me change the Inactivity Timeout to 0 on the Group properties, Advanced tab for the job set. Once changed, everything is once again backing up just fine.

    EMC did note that there has been some reported issues in the communication between the agent and networker server on 7.5. I would have gone back to 7.4 SP4 if this had not fixed my issue.
  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    5167

    0

    Posted March 28th, 2009 04:00

    It seems like connection between filer and server was dropped (do you have firewall) or had been idle for more than inactivity timeout is set.
  • Aquatique

    1 Message

    5167

    0

    Posted March 29th, 2009 22:00

    I've got the same failure with 3Tb volume after upgrading to 7.5
  • ashxos

    142 Posts

    5167

    0

    Posted March 30th, 2009 00:00

    Thanks Meko!

    Thats worked fine! (Inactivity Timeout to 0)

    But I went through a hell to change that setting for a 48 Nos of Groups.

    Any way, I hope so ki EMC will take care of such issue.

    Thanks!
  • Sltn

    22 Posts

    5167

    0

    Posted December 6th, 2016 06:00

    what does it mean to change the Inactivity time out=0 ?

  • bingo.1

    1 Rookie

    •

    2430 Posts

    5167

    0

    Posted December 6th, 2016 08:00

    There will be no limit - it will wait forever. Not something you want to do.

  • Sltn

    22 Posts

    5167

    0

    Posted December 6th, 2016 23:00

    why not?coz I have an essue with backuping a group and the support told me that it's a network problem and asked me to change the Inactivity time out to 0.

  • bingo.1

    1 Rookie

    •

    2430 Posts

    5167

    0

    Posted December 7th, 2016 02:00

    Honestly, if there is a network problem, I would fix that first. From the GUI's online help:

    Inactivity timeout - The number of minutes of inactivity before the group of saves concludes that a client machine is (presumably) permanently hung. A value of zero indicates that no inactivity checking is done. The value is ignored by synthetic full level backup.

    If you really need a higher value than 30 mins, you can increase it, of course. BTW - the max value is 1000 mins (16 hrs) ... and unfortunately 0 . However, by setting it to 'forever' you just give up control. So you might never detect a hung client. Not really the best idea.

  • Sltn

    22 Posts

    5167

    0

    Posted December 7th, 2016 04:00

    there is no Network problem and inactivity timeout is set to 30 ..

  • bingo.1

    1 Rookie

    •

    2430 Posts

    658

    0

    Posted December 7th, 2016 08:00

    Fine. Now what is the issue? - backup aboted due to inactivity?

    If this is true (we still do not really know), try to find out whether the backup always fails with the same file.

    Run a manual "save -v" or "savegrp -v" to see more details.