Chapter 1. Introduction

This chapter discusses the following:

What is Samba for IRIX?

Samba for IRIX is a suite of programs implementing a subset of the server message block (SMB) protocol, the file sharing protocol used by Microsoft Windows operating systems. Samba for IRIX allows a machine running the IRIX operating system to provide filesystem and printer services to Windows clients.

Samba for IRIX can be configured to allow the IRIX machine to appear as one of the following:

  • A standalone workgroup server (sometimes referred to as a peer-to-peer server)

  • A member server of a Windows NT domain

  • A Windows NT primary domain controller

For more information, see Chapter 3, “Editing Configuration Files”, the Samba for IRIX Installation and Administration Guide, and the other documentation that comes with Samba for IRIX.

What is FailSafe?

IRIS FailSafe enables applications and services to be highly available, at a fraction of the cost of specialized fault-tolerant systems. FailSafe automatically fails over applications from one system in the cluster to another, in case of failure. In combination with a RAID or mirrored disk configuration, a FailSafe cluster provides resilience from any single point of failure.

What is FailSafe for Samba?

FailSafe for Samba makes IRIX filesystems highly available for Windows clients. IRIX filesystem can be XFS or CXFS.

FailSafe operates on the concept of resources. A resource can be a filesystem, an IP address, or any entity that can be moved from one node to another when a problem (or scheduled downtime) occurs. In the case of Samba, the resource that can be failed over is the ability of a Samba server to respond to service requests on a particular network basic input output system (NetBIOS) name.

In an IRIS FailSafe 2.1 cluster, one or more nodes can export Samba resources. A FailSafe resource group can contain multiple Samba resources (each with a unique NetBIOS name) and a single node in the FailSafe cluster may have multiple resource groups that contain Samba resources. If a node that exports Samba resources fails, another node provides backup service.

The FailSafe for Samba plug-in provides the Samba resource type and the following set of action scripts:


Starts the Samba resource


Stops the Samba resource


Tests to see if the Samba resource is running


Tests to see if the Samba resource is already running


Restarts the Samba resource

These scripts are found in the /var/cluster/ha/resource_types/Samba directory.

Required Software

The required software for Samba failover is as follows:

  • Samba software

    See the Samba for IRIX Installation and Administration Guide for more information about Samba.

  • Base IRIS FailSafe software

    See the installation chapter of the IRIS FailSafe Version 2 Administrator's Guide for a complete list of required base software.

  • IRIS FailSafe Samba software

    • The IRIS FailSafe Version 2 Samba Administrator's Guide subsystem is failsafe2_samba.books.book_AG

    • The man page subsystem is

    • The release notes subsystem is

    • The base software subsystem is failsafe2_samba.sw.base

Overview of Configuring IRIS FailSafe for Samba

To configure an IRIS FailSafe cluster for failover of Samba, follow these steps:

  1. If not previously performed, install, configure, and test the base IRIS FailSafe software as described in the IRIS FailSafe Version 2 Administrator's Guide.

  2. Install the Samba for IRIX software on the cluster nodes.

  3. Install the IRIS FailSafe for Samba software. See “Required Software”.

  4. Edit the configuration files. See Chapter 3, “Editing Configuration Files”.

  5. Install the Samba resource type. The Samba resource type will be installed in the cluster database automatically if the FailSafe cluster was created after installing Samba for IRIX software. See “Installing the Samba Resource Type” in Chapter 4.

  6. Create Samba FailSafe resources and add the resources and their dependencies to a resource group. See “Creating a Samba Resource” in Chapter 4, and “Creating a Samba Resource Group” in Chapter 4.

  7. Bring the resource group containing Samba resources online. Enter the following:

    cmgr> admin online resource_group RG_name in cluster clustername

    The Windows client should be able to see all of the resources that you have defined under server names.

  8. (Optional) If you are running with encrypted passwords from the smbpasswd file and you want all Samba resources to use the same smbpasswd file, create a symbolic link to the default smbpasswd file. For example, for a Samba resource named server2 with a filesystem dependency of /fs2, you would execute the following commands:

    # cd /fs2/.samba/server2/private/
    # ln -s /usr/samba/private/smbpasswd smbpasswd

    If you make changes to the smbpasswd file, you must copy it to all nodes that will be able to serve this Samba resource.

  9. Test the Samba failover. See Chapter 5, “Testing FailSafe for Samba”.