Multiple Samba Instances That Require winbind

The HA for Samba data service can support multiple Samba instances. However, only one winbind instance is supported per global zone or zone cluster.

If you intend to deploy multiple Samba instances that also require winbind, determine whether winbind needs to be a scalable service. The following discussion will help you determine how to deploy single or multiple Samba instances with winbind. Disregard any reference to winbind if it is not required.

Each example includes the following information:

• The zone cluster samba-zc is configured on two nodes of the global cluster, node1 and node2.

• Benefits and drawbacks are listed within each example.

Example 1-1  Running All Samba Instances and a winbind Instance Within the Same Failover Resource Group

This example creates a single failover resource group that contains all the Samba instances and a winbind instance in zone cluster samba-zc on global-cluster nodes node1 and node2.

node1# clresourcegroup create -Z samba-zc RG1

Benefits

Only one non-global zone per node is required.

Drawbacks

All Samba/winbind instances do not have independent failover as they are all within the same failover resource group.

Example 1-2  Running Each Samba or winbind Instance Within Separate Failover Resource Groups

Create multiple failover resource groups that will each contain one Samba or winbind instance in dedicated zone-cluster nodes across global-cluster nodes.

node1# clresourcegroup create -Z samba-zc1 RG1
node1# clresourcegroup create -Z samba-zc2 RG2
node1# clresourcegroup create -Z samba-zcN RGn

Benefits

All Samba or winbind instances have independent failover in separate failover resource groups.

All Samba or winbind instances are isolated within their own dedicated zone-cluster nodes.

Drawbacks

Each resource group requires a unique zone cluster.

Example 1-3  Running Each Samba Instance Within Separate Failover Resource Groups and winbind in a Scalable Resource Group

Create multiple failover resource groups that each contain one Samba instance plus one scalable resource group that contains a scalable winbind resource shared across zone cluster samba-zc on global-cluster nodes node1 and node2. All Samba instances share the same zone-cluster.

node1# clresourcegroup create -Z samba-zc RG1
node1# clresourcegroup create -Z samba-zc RG2
node1# clresourcegroup create -Z samba-zc RG[n]
node1# clresourcegroup create -Z samba-zc -S RG3

Benefits

All Samba instances have independent failover within separate failover resource groups.

Only one zone cluster is required.

Drawbacks

None

• +/- All Samba instances share the same non-global zone.