Unsolved
This post is more than 5 years old
5 Posts
0
3627
August 29th, 2011 06:00
nsradmin: different 'client id's shown in output using show
LS,
when I execute the following in nsradmin:
nsradmin> show
Will show all attributes
nsradmin> print type: nsr client; name: quercus0329s
type: NSR client;
name: quercus0329s;
server: quercus0616s;
client id: \
0ee0bc9f-00000004-4e48ec03-4e5b8e32-add2acb8-7966896f;
scheduled backup: Enabled;
< >
nsradmin> show name; client id
nsradmin> print type: nsr client; name: quercus0329s
name: quercus0329s;
client id: \
8ee8c8a9-00000004-4dc8d9e2-4dc8fa73-0354acb8-7966896f;
nsradmin>
Notice the different client id's. Has someone got an explanation?
Many thanks, Edgar.
No Events found!
coganb
736 Posts
0
August 30th, 2011 06:00
Hi,
This does seem odd. I don't know why but it would seem like you have duplicate clientid's for the client and depending on which way you issue the command, a different one is being picked up. What I find easiest in cases like this is to get a full list of everything and have a look through that to see what's in there. To output a list of all of the clients, just create a small file:
[root@vm-lego-230 Bobby]# more input_nsradmin
option hidden
p type: NSR client
q
[blank line here]
[root@vm-lego-230 Bobby]# nsradmin -i input_nsradmin > vmlego230_NSR_Client.cfg
This will create a file (here it's vmlego230_NSR_Client.cfg) with the full output of every NSR client resource. This should give you a better idea of what's going on.
You can also check the correct clientid for the client in the NMC to compare. If there's been a backup against a client with the incorrect clientid, then you can find it using mminfo.
There's more details on duplicate clientid's and what to do with them here:
'Unknown volume' - Troubleshooting 'client id' issues
-Bobby