Hi Abhijith, The planned setup for us is to host Citrix / Windows users home directories on the shared storage, contained within these directories is some Lotus Notes config files (address book etc) and notes throws a canary whenever there is a break in connection to these files and does not attempt a re-connect, and as a result I was hoping to be able to fail over the file locks. The directory as presented to the Citrix clients fails over flawlessly, the OS reconnects to the new server and you would never have known that the backend has moved, but Notes, errors all over the place, clicking out of error messages (x12) very visible, very irritating, and horrible in a demo of your new file server with your manager! I also seem to be getting clients disconnecting from the node that I am not stopping the service on, but this may just be me, I will re-test tomorrow. thanks for the feedback Jay On Jun 22, 2010 3:33pm, Abhijith Das <adas@redhat.com> wrote: > > > ----- "Jason Fitzpatrick" jayfitzpatrick@gmail.com> wrote: > > > > > From: "Jason Fitzpatrick" jayfitzpatrick@gmail.com> > > > To: linux-cluster@redhat.com > > > Sent: Tuesday, June 22, 2010 6:43:36 AM GMT -06:00 US/Canada Central > > > Subject: [Linux-cluster] Samba Statefull Failover > > > > > > Hi all > > > > > > Just wondering if it is possible to statefully migrate smb > > > connections > > > between cluster nodes, I am running ctdb (Samba's Cluster software) > > > but all connections are dropped when the service is failed between > > > nodes > > > > > > Setup is as follows > > > > > > 2 node cluster > > > DRBD backend shared storage in Master Master configuration > > > cman presenting GFS2 /Storage folder > > > Samba + Winbind + CTDB used to present /Storage/Test_Share via > > > \\clustername\test_share (both nodes are AD integrated) > > > > > > Connections to replicated storage are working fine, AD accounts are > > > authenticated correcly and smbstatus shows that CTDB is load > > > ballancing the cluster address between nodes correctly, > > > > > > When I run ctdb shutdown I expect existing connections to be migrated > > > > Also, I think "ctdb shutdown" is not the right command (Use "ctdb disable", it > > should all be in the man pages). Only one node should fail so that the > > other node can take over the IP address. If the IP address is not taken > > over, the clients will probably not be able to reconnect. > > > > Cheers! > > --Abhi > > > > -- > > Linux-cluster mailing list > > Linux-cluster@redhat.com > > https://www.redhat.com/mailman/listinfo/linux-cluster >