Handling errors in GitProtect

This article describes how to troubleshoot and handle errors in GitProtect.

Determining whether a task has failed

GitProtect notifies you if a backup task fails. By default, e-mail notifications are enabled, but you can also configure notifications via Slack or any webhook. Notifications can be set up in the Settings tab.

When you open the relevant tab GitProtect will indicate if any tasks have ended with errors or warnings.

In the following example, the task for the DebianDatabase device ended with an error — it's visible instantly upon opening the relevant tab.

Additionally, you can view statistics for the entire backup plan, not just a single device. To do this, open the Plans tab and click the statistics button on the right side of the window. In the Latest tasks section, you can see the most recent task executions.

Latest tasks section in the backup plan statistics panel.

---

Handling errors via Tasks tab

In general, the easiest way to handle an error in GitProtect is via Tasks tab:

1

Open the Tasks tab, then go to latest tasks.

2

Locate the task of interest (one that ended with failures or warnings) and click the expand button on the right side of the window.

3

Click the info icon to open the device details for more information.

4

All errors and warnings can be found in the STATUS DETAILS section. To view more information, expand the tab — in this specific case, the task failed because the device has no connectivity with the Management Service.

---

Handling errors via Logs tab

All errors and warnings are also displayed in the Logs tab — here you can view both statistics and logs for all devices connected to your Management Service.

The Logs tab provides more information than just backup plan errors and warnings. To view the logs you are interested in, use the search feature located in the top-right corner of the window.

---

Useful links and items

TasksLog files