UNSOLVED

adamsm1

updated

16 years ago

A

adamsm1

4 Posts

0

24200

May 31st, 2010 19:00

save failed to authenticate with nsrmm using GSS Legato: Timed out

Hi,

Have a NetWorker 7.6 server backing up numerous Windows 2003 and 2008 clients. On various save jobs we get the following errors: -

2010-05-28T11:01:36Z 39077:save: error, Failed to connect to storage node on myserver.mydomain.internal: save failed to authenticate with nsrmm using GSS Legato: Timed out

5777:save: Cannot open save session with myserver.mydomain.internal

Has anyone else come across this issue?

Any assistance would be greatly appreciated.

Cheers,

Mark.

  • 1907

    0

    Posted June 1st, 2010 03:00

    Hi Mark,

    This is Known issue in 7.6 , You can have a Look at the BUG ID (NW112881) , I'm not sure whether the bug is fixed or not , But there is a work around for this.

    You may need to disable nsrauth on the client end.

    HTH

    Hari.

  • 1907

    0

    Posted June 1st, 2010 07:00

    Mark,

               Try the steps mentioned in the below KB article

    http://solutions.emc.com/EMCSolutionView.asp?id=esg83259&usertype=C

  • AnthonyTX

    12 Posts

    1907

    0

    Posted June 7th, 2010 14:00

    I get the same error on NW 7.5.2.  It only happens over the weekend when I have my full backup jobs running. Strange part is that some drives on a server will backup but others get this error.  If I re-run the job a few days later then it all runs fine.  Is there some issue with nsrauth getting overloaded?

  • Daniea3

    123 Posts

    1907

    0

    Posted June 8th, 2010 06:00

    You may try disabling nsrauth on the client.

    Arun

  • awcrane

    14 Posts

    1907

    0

    Posted June 29th, 2010 07:00

    After fighting this same exact issue non stop for 3 months they figured out turning off NSRAUTH was a workaround for this error(not a fix). Turning off NSRAUTH breaks the configuration wizard and the browsing when modifying a job. They figured out a workaround for that(not a fix). Now the configuration wizard won't work with the SQL servers. This software is crap!

  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    1907

    0

    Posted July 13th, 2010 04:00

    Real men don't use nsrauth nor wizard

    I believe nsrauth has been worked on for 7.5SP3 (should be out soon or at least until August I believe).

    Those wizard thingy might be cool in the start, but afterwards you should be able to use existing setup as template and achieve what you want much faster even without wizard.  nsrauth has been common enemy since 7.3.x release so I always recommend not to use it.

  • S-h-u-r-i-k

    1 Message

    1912

    0

    Posted August 12th, 2011 07:00

    Hi,

    Please, can you give a link to BUG base (ID (NW112881))?

    I have same problem with 7.6

    Thank you

  • kmkramer25

    76 Posts

    1912

    0

    Posted September 16th, 2011 07:00

    I'm getting this occasionally on some filesystems on the same client during the same save session. I'm running  7.6.Build.142

  • kmkramer25

    76 Posts

    363

    0

    Posted September 16th, 2011 10:00

    all have same errors in there, here is one

    40473 09/02/11 22:30:05  2 0 0 1 15618 0 snapshot4.xxx.com savegrp command ' save -s snapshot4.centtech.com -g Jedi-Combined -LL -m jedi5w.xxx.com -l full -q -W 78 -N /share/fs10 /share/fs10' for client jedi5w.xxx.com exited with return code -1.

    32496 09/02/11 22:30:05  2 0 0 1 15618 0 snapshot4.xxx.com savegrp job (1186762) host: jedi5w.xxx.com savepoint: /share/fs10 had ERROR indication(s) at completion.

    64690 09/02/11 22:30:05  2 0 0 1 15618 0 snapshot4.xxx.com savegrp savegrp:Jedi-Combined * jedi5w.xxx.com:/share/fs10  See the file /nsr/tmp/sg/Jedi-Combined/sso.jedi5w.xxx.com.07aqGE for output of save command.

    /nsr/tmp/sg/Jedi-Combined/sso.jedi5w.xxx.com.07aqGE has already be rotated/deleted.

  • Mark_Bellows

    240 Posts

    1912

    0

    Posted September 16th, 2011 10:00

    Hi!

    Can you render the daemon.raw file from the client and get the exact error message?

    To do this, go the location of the daemon.raw file, typically located at C:\Program Files\Legato\nsr\logs

    Copy the daemon.raw file, paste it in the same folder. Rename to the date you are doing the work. For example, daemon_09162011.raw

    Next, open the command prompt and CD to the logs file directory:

    cd C:\Program Files\Legato\nsr\logs

    Then run the following command:

    nsr_render_log daemon_09162011.raw >> daemon_09162011.log

    Of course the name of the file will be based on what you have named it to. The daemon_date.log file will be in a readable format. You should have the information you need there that we will need to help you.

    Mark Bellows