Overview: Difference between revisions

From SambaWiki
No edit summary
No edit summary
Line 1: Line 1:
'''[[Replicated Failover Domain Controller and file server using LDAP]]'''
'''Overview'''


[[1.0. Configuring Samba]]

[[2.0. Configuring LDAP]]

[[3.0. Initialization LDAP Database]]

[[4.0. User Management]]

[[5.0. Heartbeat HA Configuration]]

[[6.0. DRBD]]

[[7.0. BIND DNS]]

----





Revision as of 04:43, 26 January 2007

Replicated Failover Domain Controller and file server using LDAP


1.0. Configuring Samba

2.0. Configuring LDAP

3.0. Initialization LDAP Database

4.0. User Management

5.0. Heartbeat HA Configuration

6.0. DRBD

7.0. BIND DNS



We will be configuring a 2 node cluster using Samba and Openldap to provide windows domain authentication. Heartbeat will provide the 2 nodes with one virtual IP address; we will use this IP address to map network drives and access recourses.

Most of us are familiar with some form of RAID; we will be using DRBB software RAID1 over LAN to provide real time data replication, it replicates the data on a block level; if a failure occurs on node1 or it becomes unresponsive resources will be migrated to node2 and the DRBD drive mounted.

This is a complex setup and strict guide lines need to be followed in order to achieve stability.

We should start with 2 identical machines each with 2 hard drives. One of these drives will be used for the operating system; the other is our DRBD RAID1 over LAN drive.

By today’s standards anything in the Pentium 4 range and above will suit, Operating system drive should be no less then approximately 40GB, the DRBD replication drive should be approximately 300GB each - SATA and SCSI are also fine. DRBD can currently address and replicate data storage up to 4TB.

Once familiar with this kind of configuration you can easily take one node offline to upgrade additional storage or any hardware requirements without users suffering.

High Availability and data replication should not replace traditional backups such as tape and external media devices, especially if you are using this configuration and are not familiar with the workings.

The machines will need to be in close proximity to each other so we can use Serial communication to provide a fault tolerant heartbeat. If you choose not to use serial you may have unexpected failovers due to bandwidth delay or a network card failure. Ideally we want to have a quick failover so it is important that these precautions are taken.

Each node will require 2 network cards.

Here is a basic configuration overview: