Unsolved
This post is more than 5 years old
2 Posts
0
1701
March 14th, 2011 08:00
Networker Cloning using different storage nodes
Hi,
We have recently been having a cloning issue.
We have 3 storage nodes as follows all running Networker 7.5.1 (same as the Networker Server)
Back3 - 2k3 Server
Back4 - 2k8 Server
Back5 - 2k8 Server
All 3 share 6 drives on a Quantum tape drives.
When the backups run they are using the Storage node configured in the client setting, but when it clones, it is ignoring the clone storage node.
We have set the Storage node to back5, clone storage node to back5 and recoverstorage node to back5, but it seems to read on back5 for the clone, and clones accross the LAN to back4 where the writing is done.
I contacted EMC and they really have not helped.
I added the FORCE_REC_AFFINITY=Yes into the system properties on the networker server which I found the following on https://solutions.emc.com/emcsolutionview.asp?id=esg92849 but that has made no difference.
If anyone can help out i would be most apreciative.
Thanks
0 events found
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
1
March 14th, 2011 08:00
Clone storage is parameter which is determined by clone storage node setting on storage node itself and not client. That means, NW will use clone storage node setting of storage which did backup and will ignore whatever you set in client itself.
hgcyj41pq712317
2 Posts
0
March 14th, 2011 09:00
Hi, i am not sure I understand this answer, When in the client, globals 2 of 2 you can specify the clone storage node there. We have the clone storage node as a client What do we put in there?
Thanks
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
March 14th, 2011 17:00
Clone storage node is set in client resource of storage node client. This means:
clientA
sn: back3
csn: back4
Back3:
sn: back3
csn: back5
Above we have client configure to use back3 as storage and back4 as clone storage node. Data (save) will go to back3. When cloning starts, it will go to back5 and not back4 as defines in clone storage node for clientA. This is because clone storage node field is always checked against client resource for storage node used for reading data (as it is that client performing cloning read and not client owning the data).