Openfiler 2.3 Active/Passive Cluster (heartbeat,DRBD) With Offsite Replication Node
|
Submitted by wayner (Contact Author) (Forums) on Sun, 2011-02-06 19:40. :: Linux | High-Availability | Storage
Openfiler 2.3 Active/Passive Cluster (Heartbeat, DRBD) With Offsite Replication NodeIntroductionOpenfiler is a Linux based NAS/SAN application which can deliver storage over nfs/smb/iscsi and ftp. It has a web interface over that you can control these services. The howto is based on the Howto from Kyle Gililland. A lot of thanks to him for this. The cluster we build will consist of two nodes replicating each other and taking over services and storage in case of emergency. Furthermore we have an Offsite Replication Server, which ideally stands in a physically different position and replicates the configurations/storage from which ever node is active. In case of emergency this Offsite Replication Server can be used to restore the cluster and to deliver the services. I used the Openfiler VMware Images 2.3 x86 and Openfiler 2.3 x86 Installation Media to test out it this howto. Hopefully you will be able to repeat my steps and have a safe and cheap Storage Solution.
Overview
RequirementsHardware
1. InstallationIn the Installation process of openfiler leave the portion of the disk you wanna use for Storage Services unused. In this case it was a second harddisk in each system. We create the partitions for Storage Replication after the installation. Networkconfiguration
After finishing the installation build yourself a nice working environment while you update the openfiler systems. It's important to update the systems now as openfiler 2.3 standard installation media dont bring DRBD 8.3.x which is needed for 3-node replication. conary update conary While the systems update you add the other filers to the /etc/hosts file and generate some ssh-keys and exchange them. root@filer01 ~# nano /etc/hosts #Installed by rBuilder 127.0.0.1 filer01 localhost.localdomain localhost 10.10.50.102 filer02 10.10.50.103 filer03 root@filer02 ~# nano /etc/hosts #Installed by rBuilder 127.0.0.1 filer02 localhost.localdomain localhost 10.10.50.101 filer01 10.10.50.103 filer03 root@filer03 ~# nano /etc/hosts #Installed by rBuilder 127.0.0.1 filer03 localhost.localdomain localhost 10.10.50.101 filer01 10.10.50.102 filer02 Then we create ssh-keys without a passphrase which we use for easier file-exchange. root@filer01 ~# ssh-keygen -t dsa
Generating public/private dsa key pair. Do the same on the other 2 nodes: root@filer02 ~# ssh-keygen -t dsa Exchange the public keys between the nodes: root@filer01 ~# scp .ssh/id_dsa.pub root@filer02:~/.ssh/authorized_keys2
2. Prepare The Partitions For DRBDSetup the partitions for DRBD which will contain the configuration files for openfiler and its storage services. Don't add any of this to /etc/fstab. If you created the partitions in the installation process remove the entries for them at the /etc/fstab file. You have todo this steps on all 3 Machines. fdisk /dev/sdb
Command (m for help): n You have to exist fdisk with w to write the changed to the disk. You can check the partitions after this: fdisk -l
Disk /dev/sda: 2355 MB, 2355978240 bytes NOTE: Before you can continue the systems should have finished update.
3. Create A Basic Heartbeat ConfigurationThis step is needed to create the virtual IP that DRBD is going to use for the offsite replication. Create /etc/ha.d/authkeys ( filer01 and filer02 ): auth 2 2 crc Change the accessrights to the /etc/ha.d/authkeys file: chmod 600 /etc/ha.d/authkeys Create etc/ha.d/ha.cf ( filer01 and filer02 ): debugfile /var/log/ha-debug logfile /var/log/ha-log logfacility local0 bcast eth1 keepalive 5 warntime 10 deadtime 120 initdead 120 udpport 694 auto_failback off node filer01 node filer02 Edit /opt/openfiler/etc/cluster.xml ( filer01 ): <?xml version="1.0" ?> <cluster> <clustering state="on" /> <nodename value="filer01" /> <resource value="MailTo::it@company.com::ClusterFailover"/> <resource value="IPaddr::10.10.50.100/24/eth1" /> </cluster> Go to https://10.10.11.101:446 and start iscsi target service ( this will create /etc/ha.d/haresources on filer01 ). Copy haresource file to filer02 and start heartbeat IP: root@filer01 ~# scp /etc/ha.d/haresources root@filer02:/etc/ha.d/haresources Wait till heartbeat is up on both nodes, then stop heartbeat on filer02: root@filer02 ~# service heartbeat stop This should create a failover where filer01 gets the ip address 10.11.50.100, check this with ifconfig on filer01, the output should be like this. root@filer01 ~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:0C:29:D9:66:27 If this is set you can now continue to start creating the drbd devices. If not check the output of /var/log/ha-log and try to figure out what is wrong.
4. DRBD ConfigurationThis manual implies that you have worked with drbd in the past and know howto tune the drbd common section regarding to your hardware. Using protocol C is save on stacked resources but not the best regarding network performance. Remove the old drbd.conf and create a new one: root@filer01 ~# rm /etc/drbd.conf root@filer01 ~# nano /etc/drbd.conf global {
usage-count yes;
}
common {
protocol C;
disk {
on-io-error detach;
}
net {
after-sb-0pri disconnect;
after-sb-1pri disconnect;
after-sb-2pri disconnect;
rr-conflict disconnect;
}
syncer {
al-extents 257;
rate 100M;
}
handlers {
pri-on-incon-degr "echo O > /proc/sysrq-trigger ; halt -f";
pri-lost-after-sb "echo O > /proc/sysrq-trigger ; halt -f";
local-io-error "echo O > /proc/sysrq-trigger ; halt -f";
}
startup {
degr-wfc-timeout 120; # 2 minutes.
}
}
resource meta {
on filer01 {
device /dev/drbd0;
disk /dev/sdb1;
address 10.10.50.101:7788;
meta-disk internal;
}
on filer02 {
device /dev/drbd0;
disk /dev/sdb1;
address 10.10.50.102:7788;
meta-disk internal;
}
}
resource data {
on filer01 {
device /dev/drbd1;
disk /dev/sdb2;
address 10.10.50.101:7789;
meta-disk internal;
}
on filer02 {
device /dev/drbd1;
disk /dev/sdb2;
address 10.10.50.102:7789;
meta-disk internal;
}
}
resource meta-U {
stacked-on-top-of meta {
device /dev/drbd10;
address 10.10.50.100:7788;
}
on filer03 {
device /dev/drbd10;
disk /dev/sdb1;
address 10.10.50.103:7788;
meta-disk internal;
}
}
resource data-U {
stacked-on-top-of data {
device /dev/drbd11;
address 10.10.50.100:7789;
}
on filer03 {
device /dev/drbd11;
disk /dev/sdb2;
address 10.10.50.103:7789;
meta-disk internal;
}
}Copy this file over to the other nodes: root@filer01 ~# scp /etc/drbd.conf root@filer02:/etc/drbd.conf Initiate the lower resources: root@filer01 ~# drbdadm create-md meta Start DRBD on filer01 and filer02: root@filer01 ~# service drbd start Set the lower drbd resources primary on filer01: root@filer01 ~# drbdsetup /dev/drbd0 primary -o Create the DRBD Metadata on the stacked ressource: root@filer01 ~# drbdadm --stacked create-md meta-U Enable the stacked resource and set it to primary: root@filer01 ~# drbdadm --stacked up meta-U Create DRBD metadata on filer03 and start the resources: root@filer03 ~# drbdadm create-md meta-U Control the sync process on the nodes with: root@filer01 ~# service drbd status drbd driver loaded OK; device status: This way it should look when all nodes are synced and filer01 is the primary.
5. Prepare The Configuration PartitionFiler01Initiate meta partition: NOTE: Here we gonna use the stacked resource instead of the lower level one! root@filer01 ~# mkfs.ext3 /dev/drbd10 Openfiler to Meta-Partition: root@filer01 ~# mkdir /meta Samba/NFS/ISCSI/PROFTPD Configuration Files to Meta Partition: root@filer01 ~# service nfslock stop httpd Modules for Openfiler ( use lib64 for 64bit openfiler ): root@filer01 ~# rm /opt/openfiler/etc/httpd/modules Restart Openfiler to see if everything worked: root@filer01 ~# service openfiler restart NOTE: If it doesnt restart check if you have linked the httpd Modules, probably you use lib64 instead of lib!
Filer02 and Filer03Openfiler Configuration: mkdir /meta Samba/NFS/ISCSI/PROFTPD Configuration Files to Meta Partition: service nfslock stop
|



Recent comments
1 day 1 hour ago
1 day 8 hours ago
1 day 12 hours ago
1 day 13 hours ago
1 day 22 hours ago
2 days 7 hours ago
2 days 8 hours ago
2 days 12 hours ago
2 days 16 hours ago
2 days 16 hours ago