---
title: "How to activate and deactivate the App Primary Failover"
slug: "installation-how-to-activate-and-deactivate-the-app-primary-failover"
updated: 2026-03-04T12:03:00Z
published: 2026-03-04T14:36:14Z
canonical: "docs.senhasegura.io/installation-how-to-activate-and-deactivate-the-app-primary-failover"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.senhasegura.io/llms.txt
> Use this file to discover all available pages before exploring further.

# How to activate and deactivate the App Primary Failover

In this article, you’ll find a guide on how to activate the **[App Primary Failover](/v4-2/docs/installation-app-primary-failover)**.

## Requirements

To successfully activate the **App Primary Failover**, you must meet the following requirements:

- The environment must be in a cluster.
- The number of members in the cluster must be greater than or equal to three, including the Arbitrator, when present.
- The number of members in the cluster must be odd.
- All instances of senhasegura must have connectivity with all necessary devices and endpoints.

          Important

          

Once **App Primary Failover** is activated, manual intervention to select the primary instance isn’t possible.

          Info

          

The **App Primary Failover** runs every 60 seconds and the logs can be found in the file `/var/log/senhasegura/app-primary-failover/app-primary-failover.log`.

## How to activate the App Primary Failover

To activate the **App Primary Failover**, follow these steps:

1. [Start an SSH session with administrator credentials](/v4-2/docs/administration-ssh-access).
2. Run the following command to start the **App Primary Failover**:

```
sudo systemctl enable --now app-primary-failover
```

1. Repeat the steps above for all other cluster members.

          Caution

          

Failure to apply these steps to all cluster members may result in the malfunctioning of the feature.

## How to deactivate the App Primary Failover

To deactivate the **App Primary Failover**, follow these steps:

1. [Start an SSH session with administrator credentials](/v4-2/docs/administration-ssh-access).
2. Run the following command to start the **App Primary Failover**:

```
sudo systemctl enable --now app-primary-failover
```

1. Repeat the steps above for all other cluster members.

          Caution

          

Failure to apply these steps to all cluster members may result in the malfunctioning of the feature.