Different Pool, Same Members

Hi all,

 

 

I've done some brief testing:

 

 

1 x VS, with a persistence of 30s

 

2 x pools, A and B

 

 

when Pool A is the resource for the VS, it serves data. When the resource is changed to Pool B, if there is an active persistence record pointing to a member in Pool A, that active persistence record will have priority over a resource change to Pool B. Thus, it seems that persistence trumps resource allocation during a resource change. Which is what weas expected of the device.

 

 

Regards

 

 

Dean