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.
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?
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).
ble1
4 Operator
•
14.4K Posts
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
4 Operator
•
14.4K Posts
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).