Did you see this already with 8.1.x or after 8.2.x? If with 8.1.x, why did you go to 8.2.x instead of trying to fix it there? Anyway, can you check following:
- permissions are set correctly (in NSR usergroup)
- there is no mismatch between backup server name and storage node definition (like one is defined over shortname and other over FQDN)
ledugarte
96 Posts
0
December 27th, 2016 10:00
Have you tried delete storage node resource and create it again?.
Raja_Bala
37 Posts
0
January 3rd, 2017 21:00
In SN, Stop NW services
Rename /nsr/res/nsladb directory to something like /nsr/res/nsrladb_old
Start NW services and check.
roberto_giovann
2 Posts
0
January 5th, 2017 07:00
Hi all,
the Storage Node is the Backup Server and so do not me delete storage node resource.
About rename /nsr/res/nsladb directory being the nsrladb resource of backup server, has it the same impact of a pure storage node host?
Thanks in advance
ble1
4 Operator
•
14.4K Posts
0
January 6th, 2017 00:00
Did you see this already with 8.1.x or after 8.2.x? If with 8.1.x, why did you go to 8.2.x instead of trying to fix it there? Anyway, can you check following:
- permissions are set correctly (in NSR usergroup)
- there is no mismatch between backup server name and storage node definition (like one is defined over shortname and other over FQDN)