Did you check the logs? NMC might be broken and not showing sessions while those could be there. Checks either logs or status with nsrwatch if you can.
Would you please explain in more details especially the nsrwatch
Many thanks
Log can be checked with nsr_render_log /path/to/daemon.raw
nsrwatch is command which gives you kind of text GUI. On Windows you have it on recent versions only so if this is not the case you can use any Linux/UNIX box to connect to server via nsrwatch. Recent versions are way better as they give you ability to select what you wish to monitor and thus take better advantage of of screen space.
The behaviour was die to the fact that those 3 clients were in a kind of "hanging state". I have rebooted those clients and Legato is backing them up now.
Thanks for the hint, Hrvoje. I just verified that it was delivered with 7.6.2 - just another undocumented feature.
Why doesn't EMC add this info to the Release Notes? Often i get the impression that they are afraid customers could even use a feature ...
Perhpps because it has been a bug not to have in the first place I remember running lynx on my MS DOS box long time ago. Anyway, on more serious note, if you check list of "Fixed bugs in NW release in 7.6 SP2" in release notes (table 3) you will find LGTpa49895 - Add nsrwatch to Windows. So it is documented. I agree that given the wide usage of nsrwatch it might have caught more attention by placing it in what is new area, but since this was seen as bug I guess it ended up where it ended at the end.
"Perhpps because it has been a bug not to have in the first place I remember running lynx on my MS DOS box long time ago. Anyway, on more serious note, if you check list of "Fixed bugs in NW release in 7.6 SP2" in release notes (table 3) you will find LGTpa49895 - Add nsrwatch to Windows. So it is documented. I agree that given the wide usage of nsrwatch it might have caught more attention by placing it in what is new area, but since this was seen as bug I guess it ended up where it ended at the end."
I can understand that. However, i can only fix what already exists. You may call me a stupid customer, but as such i first start reading about new features - i will only look in the bugfix section when i am waiting for a specific solution. At least my way. And other customers might do it the same way.
I only read bug fixes... that way I leverage what unseen errors I might have and do they affect me But I agree, nsrwatch thingy should have get more space in release notes....
Johans2
100 Posts
0
July 4th, 2011 00:00
Some additional info:
When I start another group manually, it nearly immediately starts loading the taep and it runs....
So it seems to be related to the Group ???
Rgds,
Johan
ble1
4 Operator
•
14.4K Posts
0
July 4th, 2011 00:00
Did you check the logs? NMC might be broken and not showing sessions while those could be there. Checks either logs or status with nsrwatch if you can.
jarady
2 Intern
•
132 Posts
0
July 4th, 2011 01:00
Hrvoje,
Would you please explain in more details especially the nsrwatch
Many thanks
ble1
4 Operator
•
14.4K Posts
0
July 4th, 2011 01:00
Log can be checked with nsr_render_log /path/to/daemon.raw
nsrwatch is command which gives you kind of text GUI. On Windows you have it on recent versions only so if this is not the case you can use any Linux/UNIX box to connect to server via nsrwatch. Recent versions are way better as they give you ability to select what you wish to monitor and thus take better advantage of of screen space.
Johans2
100 Posts
0
July 4th, 2011 02:00
The behaviour was die to the fact that those 3 clients were in a kind of "hanging state". I have rebooted those clients and Legato is backing them up now.
Thanks
Johan
bingo.1
2.4K Posts
0
July 4th, 2011 21:00
"On Windows you have it on recent versions only so if this is not the case you can use any Linux/UNIX box to connect to server via nsrwatch."
Thanks for the hint, Hrvoje. I just verified that it was delivered with 7.6.2 - just another undocumented feature.
Why doesn't EMC add this info to the Release Notes? Often i get the impression that they are afraid customers could even use a feature ...
ble1
4 Operator
•
14.4K Posts
0
July 5th, 2011 02:00
Perhpps because it has been a bug not to have in the first place
I remember running lynx on my MS DOS box long time ago. Anyway, on more serious note, if you check list of "Fixed bugs in NW release in 7.6 SP2" in release notes (table 3) you will find LGTpa49895 - Add nsrwatch to Windows. So it is documented. I agree that given the wide usage of nsrwatch it might have caught more attention by placing it in what is new area, but since this was seen as bug I guess it ended up where it ended at the end.
bingo.1
2.4K Posts
0
July 5th, 2011 10:00
"Perhpps because it has been a bug not to have in the first place
I remember running lynx on my MS DOS box long time ago. Anyway, on more serious note, if you check list of "Fixed bugs in NW release in 7.6 SP2" in release notes (table 3) you will find LGTpa49895 - Add nsrwatch to Windows. So it is documented. I agree that given the wide usage of nsrwatch it might have caught more attention by placing it in what is new area, but since this was seen as bug I guess it ended up where it ended at the end."
I can understand that. However, i can only fix what already exists. You may call me a stupid customer, but as such i first start reading about new features - i will only look in the bugfix section when i am waiting for a specific solution. At least my way. And other customers might do it the same way.
ble1
4 Operator
•
14.4K Posts
0
July 5th, 2011 11:00
I only read bug fixes... that way I leverage what unseen errors I might have and do they affect me
But I agree, nsrwatch thingy should have get more space in release notes....