networker ignores client's recover storage node list

Question

hello,

i have a situation where networker ignores recover storage node value from client config when trying to recover data. we have EDL (EMC disk library) as backup device. EDL has also embedded storage node (ESN) enabled which is used for cloning. there is physical library connected to EDL back-end.

according to EMC best practices we configured "read host" value to be ESN from library properties. this ensures that ESN is used when reading data during cloning. according to NW manuals client's recover storage node value should have higher priority when choosing SN for recovery. but for some reason NW ignores that value and mounts all volumes to ESN.

does anyone have some ideas which might be wrong or is this expected behaviour?

kaido

kipz1 · Answer

hello,i haven't tried playing with client's clone storage node. but yes, i have tried to just set read host to empty value and that works. when there is no read host value recover storage node is not ignored anymore.so seems that this is expected behaviour and EMC cloning best practices are actually not the best...?kaido

benzino1 · Answer

Have you try to set read hostname to empty value and set clone storage node to EDL on each client which data should be cloned? I think this should help NW to proper choose of recover SN. You can also try to set read hostname to empty value (without changing anything else) only for recover time.

ble1 · Answer

What NW version and did you try FORCE_REC_AFFINITY? AFAIK, this has been broken and fixed so it depends on which version you are...

kipz1 · Answer

NW version is 7.3.3. i haven't tried this affinity yet.

ble1 · Answer

If I remember correctly for 7.3.3 there is a patch and it is supposed to be fixed in 7.3SP4.

NetWorker

networker ignores client's recover storage node list

Was this post helpful?