NW 731 Recover Storage Node setting doesn't work

Sorry, if I leave the "recover storage node" resource blank, it still defaults to the IP storage node, it is almost as if the "recover storage node" resource is being ignored.

Here is the client config for one of the SAN storage nodes:
type: NSR client;
name: br15at01e;
server: splhrl192;
client id: \
816f3776-00000004-45c06308-45c06307-017e0000-ac1e0798;
scheduled backup: Enabled;
comment: UBTUB15T1M - fs;
Save operations: ;
archive services: Disabled;
schedule: Full Every Tuesday;
browse policy: 31day;
retention policy: 31day;
statistics: elapsed = 240111, index size (KB) = 35610,
amount used (KB) = 35610, entries = 229942;
directive: Unix Standard exclude Oracle;
group: UBTUB15T1M;
save set: All;
priority: 500;
remote access: root@*, oracle@*, rman@*;
remote user: ;
password: ;
backup command: ;
application information: ;
ndmp: No;
executable path: ;
server network interface: ;
aliases: br15at01, br15at01e, br15at01e.baplc.com;
index path: ;
owner notification: ;
parallelism: 4;
archive users: ;
storage nodes: br15at01e;
recover storage nodes: br15at01e;
clone storage nodes: ;
hard links: Disabled;
short filenames: Disabled;
client OS type: ;
CPUs: ;
NetWorker version: ;
enabler in use: No;
licensed applications: ;
licensed PSPs: ;


Here is the pool config for that backup:

type: NSR pool;
name: 31dayC;
comment: ;
enabled: Yes;
pool type: Backup;
label template: Default;
retention policy: ;
groups: UBTUB15T1M, UBTUBFC76M;
clients: ;
save sets: ;
levels: ;
devices: ;
store index entries: Yes;
auto media verify: No;
Recycle to other pools: No;
Recycle from other pools: No;
volume type preference: ;
max parallelism: 0;
mount class: default;

There are some 200+ other groups in the pool, just didn't paste them all in to this!

I assume that what you want is to have storage node = recover storage node. In that case simply leave recover storage node field empty.

OK, can you post example? Example should include client configuration and pool configuration used for backup.

Well, it should work. Actually it should work without you forcing recover storage node at all. While not directly, indirectly 7.3.2 jumbo had some code change to fix FORCE_REC_AFFINITY issue so it might be that was fixed silently too. Try 7.3.2 jumbo on your server and storage nodes and then try the same thing again. If it doesn't work then you will need to have your support have closer look at configuration and what NW think is going on.

Thanks, but we are not in a position to go to 7.3.2.

In that case open it up with support and if they confirm an issue to be there see if that can port back the patch (if one exists).

Thanks, I already have a case open with support - I wanted to use this avenue as well in case it was something someone had already experienced and had a fix for.

Not as yet, support (EMC) are currently trawling through the various log files and config details they requested.

I think this could be generic to 7.3.1 as this happens on any SAN storage node I attempt a recovery on.

Did support reproduced your issue? I guess that is rather easy if issue is there...