Unsolved
This post is more than 5 years old
71 Posts
0
3012
November 21st, 2007 02:00
Dedicated Storage Node cannot save remote data from client
Hi,
Dedicated Storage Node cannot save remote data from client.
Cannot open a session with backup server.
Best regards,
M*
Dedicated Storage Node cannot save remote data from client.
Cannot open a session with backup server.
Best regards,
M*
No Events found!



Peregrine1
71 Posts
0
November 21st, 2007 02:00
SN keep trying contacting client, it's not able to create a save session.
Best regards,
M*
HabibG2
455 Posts
0
November 21st, 2007 02:00
HabibG2
455 Posts
0
November 21st, 2007 03:00
What is defined in the Storage node field? For DSN you must use you the Client FQN as your storage node.
Under Monitor, in the Log tab have a look how the backup is progressing.
Take a look at the Daemon.log for error message.
ble1
2 Intern
•
14.3K Posts
0
November 21st, 2007 11:00
ccampbell4
2 Posts
0
July 20th, 2010 05:00
This problem still exists and pops up occasionally when storage nodes are trying to back up their own local data.
The storage node ONLY has itself and nsrserverhost as storage nodes.
It complains -
Where beasttorls3 is a Dedicated Storage Node
and coretorls10 is the nsrserverhost (master Networker server)
Would EMC please get off their collective asses and address this issue?
coganb
736 Posts
0
July 20th, 2010 08:00
Have you opened a Service Request with support for this? If not, please do so, so that we can investigate this and get it fixed.
-Bobby
elvinperez
87 Posts
0
July 27th, 2010 11:00
Hello,
Verified file hosts both servers.
Regards,
elvin...E
ble1
2 Intern
•
14.3K Posts
0
August 19th, 2010 03:00
I have seen this sometimes with nsrauth enabled. Is this your case?
ccampbell4
2 Posts
0
August 19th, 2010 03:00
Apparently some enhanced authorization was enabled quietly and by
default at some version upgrade in the past.
I followed some instructions from EMC to DISABLE the (useless in our
environment) feature and am now waiting to see if the problem remains.
(Change the Authentication Mode field to be: 0.0.0.0/0,oldauth )
No one has yet explained to my HOW/WHY enhanced authentication would
result in this intermittent issue. And more importantly, if this is a
know issue why hasn't it been corrected?
Yes, I am working on the tenuous assumption that some client somewhere
might actually require their enhanced authentication. In our case,
actually having reliable backups is much more critical.
Has anyone vetted this new security mechanism to see if it actually does
enhance anything in the security realm? Just curious.
I should know within a week or two if this corrects the issue.
Hoping.. last time I raised this with EMC (perhaps a year ago or more)
their solution was to upgraded the dedicated storage nodes to non
dedicated storage nodes ($$).
Cheers,
-craig
ble1
2 Intern
•
14.3K Posts
0
August 19th, 2010 04:00
AFAIK this is known (at least to some people it is) and nsrauth is supposed to be fixed in 7.5.3.x code, but I will stick to 7.5.2.x for now.