Wrong index location for virtual clients in mscs cluster

Usually you see that when relationship between physical and virtual clients is not defined correctly within NW configuration. To workaround it use -c option to force index usage.

You can also check the pathignorerule option for this.

Hello Hrvoje,

what do you mean with "relationship"?? i already tried the -c option but then networker uses for each virtual client a client connection license and that's not ok

Of course, it could be bug too - try to put 7.2.2 on clients and see if that makes any difference - if it does then you know what you must do.

That means that NW did not recognize that system to be in cluster. Relationship means:
a) create each phy client first
b) create virtual one then
c) make sure that virtual one has admin user @ phy boxes in remote access only
d) do the backup of phy clients first
e) do the backup of vir clients after

Hmmm then i think everything is configured the right way, so i can try 7.2.x on the phys node - any other idea what could go wrong?

Message was edited by:
legatokbacc

Hello Hrvoje

i installed 7.2.2 on one phys node and now it works for the virtual nodes running on this phys node -> bug in 7.3.2? -> i opened call with orchestra, perhaps you??

Not me as I'm onsite, but it does sound as bug (what else ).

Did this issue get resolved? Is the fix to downgrade the client? I have a similar problem with 7.3.2.