1. NiceLabel Help Center
  2. Knowledge Base
  3. Installation and Upgrades

Set up Automation Failover Cluster

To enable NiceLabel Automation in a high-availability (fail-over) cluster:

  1. Install NiceLabel Automation on all nodes.

  2. Enable the Microsoft Failover Clustering feature on your Windows Servers.

  3. Create a network-shared folder accessible to all nodes with full privileges to NiceLabel Automation. Automation will copy system files to this folder. You can also store your printing solution files in the same folder (.misx, .nlbl, images,...)

  4. On all nodes, open  NiceLabel Automation Builder and go to File > Options > Automation. Select the option Enable Failover Cluster Support and enter the network shared folder path you defined in a previous step.

    24_automation_failover1.png

  5. On all nodes, go to the Services console. Select NiceLabel Automation Service and on the General tab set Startup type to Manual. Then Stop the service.

    25_automation_failover2.png

  6. Add NiceLabel Automation Services to your Failover Cluster Manager:

    1. Open Failover Cluster Manager.

    2. Expand your cluster and go to Roles.

    3. Select Create Empty Role. Enter the name of the role.

    4. Click Add Resource > Generic Service.

    5. Add NiceLabel Automation Service and NiceLabel Proxy Service 10.

    6. Create dependencies for Automation Services. Open  NiceLabel Automation Service and go to the Dependencies tab. Insert NiceLabel Proxy Service 10.

      26_automation_failover3.jpeg

    7. (Optional) You can set which Automation configuration file (.misx) will open at starting the service. Go to the General tab and enter the path to the .misx file in Startup parameters. .misx file must be stored in the shared folder that is accessible to all nodes.

      27_automation_failover4.jpeg

    8. Click OK.

Your Automation failover cluster is now set.

To test the Automation failover cluster, right-click the newly created role and select Start role. Select the Owner node which is currently active. You can reboot the active node or switch to another node. Right-click on the role and select Move. After a few seconds, the Owner should change and Automation is now running on the new node.