---
title: "How to manage backup, restore, and logs"
slug: "orbit-web-how-to-backup-restore-and-logs"
updated: 2026-11-03T14:48:12Z
published: 2026-11-03T14:48:12Z
canonical: "docs.senhasegura.io/orbit-web-how-to-backup-restore-and-logs"
---

> ## 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 manage backup, restore, and logs

Attention

          

The Segura™ backup files are encrypted using **AES-256** encryption. To perform this procedure, you should be in contact with the Segura™ **support team**.

## Restore a backup

          Attention

          

The Segura™ backup files are encrypted. To perform this procedure, you should be in contact with the Segura™ **support team**.

The backups executed are exported to the remote drive of the customer's choice. But a copy of the backup is kept inside the instance to speed up the restore process if necessary.

The Segura™ enginer will execute the backup file opening procedure (decrypt) to get the backup file ready to be restored.

Once the backup file is decrypted, the Segura™ engineer should use the `orbit backup` command line tool to restore the target version.

          Alert!

          

This procedure will restore all database data and schema to the desired past time. You should restore all other binaries if performed a system upgrade was between the current time and the selected backup file. The binary application files can be restored using the **Debian APT tool**.

## Logs

You can observe the execution of the backup through the **CRON** schedule in the report **Orbit Server Manager > Logs > Backup**.

## Backup report

In the **Credential Backup report** under **Settings > Backup > Credentials**, you get information if the credential complies with the password policies.

1. **Password Policy:** Lists the password policy related to the credential, as configured. For example:

- Low
- Average
- High

1. **Conformity:**

- **Yes**: In green, if the credential complies with the related policy
- **No**: In red, if the credential does not comply with the related policy

          Info

          

At the time of backup, Segura™ checks the composition of the password with the policy and updates the information on whether or not it is adherent.