Restriction for multiple Samba instances that require winbind

The Sun Cluster HA for Samba data service can support multiple Samba instances. However, only one winbind instance is supported per global zone, non-global zone or failover zone.

If you intend to deploy multiple Samba instances that also require winbind, then you will need to consider if 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.

Within these examples:

• There are two nodes within the cluster, node1 and node2.

• Both nodes have two non-global zones each named z1 and z2.

• Additional non-global zones are represented by z[n].

• Each example listed simply shows the required Nodelist property value when creating a failover or scalable resource group.

• Benefits and drawbacks are listed within each example as + and -.

Although these examples show non-global zones z1 and z2, you may also use global as the zone name or omit the zone entry within the Nodelist property value to use the global zone.

Example 3 Run all Samba instances and a winbind instance within the same failover resource group.

Create a single failover resource group that will contain all the Samba instances and a winbind instance in non-global zones across node1 and node2.

# clresourcegroup create -n node1:z1,node2:z1 RG1

• + Only one non-global zone per node is required.

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

Example 4 Run each Samba/winbind instance within separate failover resource groups.

Create multiple failover resource groups that will each contain one Samba/winbind instance in exclusive non-global zones across node1 and node2.

# clresourcegroup create -n node1:z1,node2:z1 RG1
#
# clresourcegroup create -n node1:z2,node2:z2 RG2
#
# clresourcegroup create -n node1:z[n],node2:z[n] RG[n]

• + All Samba/winbind instances have independent failover in separate failover resource groups.

• + All Samba/winbind instances are isolated within their own exclusive non-global zones.

• -Each resource group requires a unique non-global zone per node.

Example 5 Run each Samba instance within separate failover resource groups and winbind in a scalable resource group.

Create multiple failover resource groups that will each contain one Samba instance and one scalable resource group that will contain a scalable winbind resource in shared non-global zones across node1 and node2.

# clresourcegroup create -n node1:z1,node2:z1 RG1
#
# clresourcegroup create -n node1:z1,node2:z1 RG2
#
# clresourcegroup create -n node1:z1,node2:z1 RG[n]
#
# clresourcegroup create -S -n node1:z1,node2:z1 RG3

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

• + Only one non-global zone per node is required.

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

For a scalable resource group different zones from the same node cannot be specified in the Nodelist parameter, thereby limiting a scalable resource group for winbind to one zone from the same node.

Example 6 Run each Samba/winbind instance in separate failover resource groups that contain separate failover zones across node1 and node2.

Create multiple failover resource groups that will each contain a failover zone. Each failover zone will then contain one Samba/winbind instance.

# clresourcegroup create -n node1,node2 RG1
#
# clresourcegroup create -n node1,node2 RG2
#
# clresourcegroup create -n node1,node2 RG[n]

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

• + The same failover zone per resource group is used per node.

• + Each failover zone is only active on one node at a time.

• - Each resource group requires a unique failover zone per node.

If your requirement is simply to make Samba highly available you should consider choosing a global or non-global zone deployment over a failover zone deployment. Deploying Samba within a failover zone will incur additional failover time to boot/halt the failover zone.