View Single Post
  #57  
Old 25th September 2006, 17:35
djalex djalex is offline
Member
 
Join Date: Aug 2006
Posts: 49
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hi Falko,

I managed to get the setup working now. The systems have been renamed as follows:

Primary server - PRI_SRVR
Secondary server - SEC_SRVR
Windows client - WIN_CLNT
Samba service - SMB_SRVC

First, I entered the following commands on both primary and secondary linux servers.

groupadd hacluster
useradd -g hacluster -d /home/hacluster -m hacluster
groupadd haclient
useradd -g haclient -d /home/haclient -m haclient


I edited the configuration files as follows:

hosts [present in /etc/hosts and C:/Windows/system32/drivers/etc/hosts]
====
192.168.50.151 PRI_SRVR
192.168.50.152 SEC_SRVR
192.168.50.153 WIN_CLNT
192.168.50.195 SMB_SRVC

drbd.conf [present in /etc]
=======
resource r0
{
protocol C;

startup
{
degr-wfc-timeout 120; # 2 minutes
}
disk
{
on-io-error detach;
}
net
{
}
syncer
{
rate 10M;
group 1;
al-extents 257;
}
on PRI_SRVR
{
device /dev/drbd0;
disk /dev/hda5;
address 192.168.50.151:7789;
meta-disk internal;
}
on SEC_SRVR
{
device /dev/drbd0;
disk /dev/hda5;
address 192.168.50.153:7789;
meta-disk internal;
}
}

ha.cf [/etc/ha.d]
====
Logfacility local0
logfile /var/log/ha-log
debug 1
bcast eth0
deadtime 10
auto_failback off
node PRI_SRVR SEC_SRVR

haresources [/etc/ha.d]
=========
PRI_SRVR IPaddr::192.168.50.195

authkeys [/etc/ha.d]
=======
auth 3
3 md5 goose

smb.conf [/etc/samba]
=======
[global]
workgroup = workgroup
admin users = root
share modes = yes
browseable = yes
username map = /etc/samba/smbusers
password server = None
guest ok = yes
guest account = haclient
interfaces = 192.168.50.195

[files]
path = /mnt/files
writeable = yes

smbusers [/etc/samba]
=======
root = root
haclient = user01

I started up DRBD, heartbeat and SAMBA on both primary and secondary servers. On the windows system, I clicked on Start - Run typed the address \\192.168.50.195. I then logged in with the user account user01. After authentication, I was able to see the Samba share files on the Linux server - even had the ability to modify and save information in the files.
Then I shut down the primary server. SEC_SRVR stood in for the primary hosting the SAMBA service IP address 192.168.50.195. I then logged in to the SAMBA share with the service IP address and login user user01. I was able to see that the file was still available along with the information saved, prior to the crash. Due to time restrictions, I have to end the experimental study at this juncture. But this can be used as a model for future research and investigation. Falko, I would like to thank you for the efforts you took to troubleshoot the problem. Although the solution was not easily attainable, you tried your best. Thank you for taking the interest in my experimental study; it is greatly appreciated.

Best regards,
Alex
Reply With Quote