The simple clustering scenario of one Back4 moving between two different cluster nodes was already supported prior the version 2.1.

But sometimes you want to run multiple Back4 instances (e.g. cleanup, indexing and db tasks on one node, dataSrc on the other).

In this scenario, clustering was not supported prior to version 2.1, because the Back4config name that controls the service behavior was linked to the server name, and not to the cluster application name.

Example

The cluster has two defined cluster File Servers AAA and BBB and two physical servers server01 and server02. I install Tera Back4 with the name One and Tera Back4 with the name Two on both nodes of the cluster.

I add the One to cluster AAA and Two to cluster BBB.

I create back4config AAA with port 7373 and BBB with port 7374.

I want back4 to read the configuration that matches the cluster server name (AAA or BBB), and not the physical machine name (server01 and server 02).

We could, for example, define a rule, where: if the back4 starts and it is aware of being a cluster resource, it will look for a configuration named "cluster_clusternodename", or, maybe even better and simpler, look for a configuration named as the instance name (One, Two). The second option may be generic, also for Back4 not in cluster (now the configuration needs to be named as the server).

Important

Copy the System.Management.Automation.dll in the Back4 folder.

The System.Management.Automation.dll can be found in (actual path can be different based on the OS):

Windows 8: C:\Program Files\Reference Assemblies\Microsoft\Windows Power Shell\v1.0

Windows Server 2012: C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Management.Automation\v4.0_3.0.0.0__31bf3856ad364e35\

To find the location of the dll on a system:

1.Open a Power Shell.

2.Use the command:

[psobject].assembly.location