similar to: samba file server with heartbeat and drbd

I'm currently testing fail-over with a two-node active-active cluster (with node dig and node dag): Both nodes are up, one is manually killed. CTDB on the node that's still alive should perform a recovery and everything should working again. What's infrequently happening is: After killing the pacemaker-process on dag (and dag consequently being fenced), dig's CTDB tries to

Hi everyone, I need some help to setup my configuration failover system. My goal is to have a redundance system using Xen + DRBD + Corosync + Pacemaker On Xen I will have one virtual machine. When this computer has network down, I will do a Live migration to the second computer. The first configuration I will need is a crossover cable, won''t I? It is really necessary? Ok, I did it. eth0

hi guys, we're evaluating the available clustering options to get ctdb up and running for a highly available file server. we've set up both gluster and ocfs2 both on seperate 2 node setups. ocfs2 seems to provide better throughput and iops to samba clients than does gluster and that is comparing a single node server to a ctdb clustered 2 node server. problem with ocfs2 is that i've

Hi guys I'm wondering if anyone here is using the GlusterFS OCF resource agents with Pacemaker on CentOS 7? yum install centos-release-gluster yum install glusterfs-server glusterfs-resource-agents The reason I ask is that there seem to be a few problems with them on 3.10, but these problems are so severe that I'm struggling to believe I'm not just doing something wrong. I created

Hi, Can u please explain for what purpose pacemaker cluster used here? Regards, Jiffin On Thursday 07 December 2017 06:59 PM, Tomalak Geret'kal wrote: > > Hi guys > > I'm wondering if anyone here is using the GlusterFS OCF resource > agents with Pacemaker on CentOS 7? > > yum install centos-release-gluster > yum install glusterfs-server

Hi We've got drbd going between 2 nodes:) ATM there is un-partitioned space on each node but (we think) they are syncing OK. It looks as though it has synced the whole partition (2GB) from the primary node 1 to the other node: node 1 smb1:/home/steve # cat /proc/drbd version: 8.4.4 (api:1/proto:86-101) GIT-hash: 3c1f46cb19993f98b22fdf7e18958c21ad75176d build by SuSE Build Service 1:

Hi, I been working on for about a month and half on setup drbd and nfs. I keep running into issue with the way heartbeat/pacemaker handles nfs. Does anyone know a good way to set up a HA NFS server with DRBD and Heartbeat and NFS. I am willing to share my pain in setting it up. Chuck Payne NEO Linux System Engineer chuck.payne at vocolacity.com -------------- next part -------------- An HTML

I'm trying to setup a pair of FreePBX-4.211.64 boxes using Pacemaker, Corosync, and DRBD. All the examples I've found so far use Heartbeat, but Heartbeat is not in the repositories and doesn't want to compile from source. Does anyone have a working configuration they can share or a tutorial they can point me to? Also, what does drbdlinks bring to the party? Isn't just linking

Hi, I want to upgrade from 8.0 to 8.1 but yum update does not work. Still 8.0 Probably the cause is that I compiled DRBD myself because it was not available for 8.0 when I set up the machine. Now yum update says: Error: ?Problem 1: cannot install the best update candidate for package drbd-pacemaker-9.11.0-1.el8.x86_64 ? - nothing provides pacemaker needed by

Hi, I want to combine all the above mentioned technologies. The Linbit pages warn not to use the drbd: VBD with HVM DomUs. This page however: http://publications.jbfavre.org/virtualisation/cluster-xen-corosync-pacemaker-drbd-ocfs2.en (thank you Jean), simply puts two DRBD devices in dual primary mode and starts Xen DomUs while pointing to the DRBD devices with phy: in the DomU config files.

I am running a two-node web cluster on OCFS2 via DRBD Primary/Primary (v8.3.8) and Pacemaker. Everything seems to be working great, except during testing of hard-boot scenarios. Whenever I hard-boot one of the nodes, the other node is successfully fenced and marked ?Outdated? * <resource minor="0" cs="WFConnection" ro1="Primary" ro2="Unknown"

You could also use pacemaker to manage promoting the drbd device and mounting it with a dead master role as a dependency. Are you using anything to automatically promote the send slave already?

Hello all, has someone worked with DRBD (http://www.drbd.org) for HA of mail storage? if so, does it have stability issues? comments and experiences are thanked :) Thanks, Rodolfo.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! I think I stumbled on at least two bugs in the CentOS 7.2 pacemaker package, though I'm not quite sure if or where to report it. I'm using the following package to set up a 2-node active/passive cluster: [root at clnode1 ~]# rpm -q pacemaker pacemaker-1.1.13-10.el7_2.4.x86_64 The installation is up-to-date on both nodes as of the

Hello, I'm considering moving our windows shares (2003 domain) to a samba server, to improve performance, setup clustering and use scheduled lvm snapshots. However, I've not clarified how our current security policy would be applied on this server and like to ask you some things (sorry, I'm sure they already have been posted but there is so much on this topic to read I prefer to ask

Hi all, could somebody point me to what is considered a sound way to offer Xen guests on a two node DRBD cluster in combination with Pacemaker? I prefer block devices over images for the DomU''s. I understand that for live migration DRBD 8.3 is needed, but I''m not sure as to what kind of resource agents/technologies are advised (LVM,cLVM, ...) and what kind of DRBD config

Dear all, I have two samba servers auth agains ldap, so I use: idmap backend = ldap:ldap://127.0.0.1 Is it possible to setup ctdb to run with a ldap backend? I know ctdb uses: idmap backend = tdb2 Any suggestions? Greetings Daniel ----------------------------------------------- EDV Daniel M?ller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 T?bingen Tel.:

Hello list, Working on migrating my existing High-Availability setups from CentOS 5.3 to 6.0, both x86_64. I generally setup a fairly simple 2 node active/passive cluster using DRBD , Heartbeat, and Pacemaker. Use these clusters to run our proprietary Medical software plus a few key services ( openvpn , Digi PortServer Daemon, etc.). I had a procedure in place for doing all of this under 5.3

Hello, I'm testing a HA cluster using Heartbeat and DRBD. I've moved /etc/samba /var/log/samba /var/run/samba and /var/cache/samba to the shared DRBD volume. My problem is that I don't know if these are the only files I should move in the shared volume, I can't find a doc listing all the files used by Samba. Are there other files I should move to the shared volume so that the

Hi everybody, our university uses a Samba 3.6.9 server as PDC for a windows domain on a single physical server (external LDAP on another server is used). To get some redundancy up running a second physical machine was bought, which is exactly the same as the one running. Now I?m searching for the best way to get the job done. The first thought was to build a HA-Cluster with Corosync/Pacemaker