Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file not shown.
Binary file not shown.
131 changes: 8 additions & 123 deletions docs/endpointprotector/admin/systemmaintenance/backup.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,129 +16,6 @@ The System Backup feature allows you to create and manage comprehensive backups
Using the web interface or administrative console, you can perform backups, restore previous
versions, and set up automatic routines to ensure your data is consistently protected.

### From the Web Interface

This module allows you to make complete system backups.

![Allows you to make complete system backups](listofsystembackups.webp)

To view the list of current backups, go to **System Maintenance** > **System Backup v2**.

To restore the system to an earlier state, click **Restore** next to the entry and then confirm your
action.

:::warning
Once deleted, a backup cannot be recovered.
:::


The Download button will prompt you to save the **.eppb backup file** on the local drive. It is
recommended to keep a good record of where these files are saved.

:::warning
When using the Restore Backup feature, we recommend requesting assistance from customer
support.
:::


![Allows you to make complete system backups](createsystembackup.webp)

On the Make Backup section, you have the following options:

- Save the Database content – the backup file will contain all the devices, rights, logs, settings
and policies present on the Endpoint Protector server at the making of the backup
- Save the Application sources – the backup will contain files such as the Endpoint Protector clients
and others related to the proper functioning of the server

:::note
The System Backup will not contain nor preserve the IP Address, File Shadowing copies or
the Temporary Logs Files.
:::


The second section, Status, returns the state of the system. If a backup creation is in progress, it
will be reported as seen below.

![System Backup Status](systembackupstatus.webp)

If the system is idle, the button will return the last known status, which by default is set at 100%
done.

The next menu, Upload, allows you to populate the backup list with .eppb files from the local
filesystem. This functionality is useful in cases of server migration or crash recovery.

:::info
Endpoint Protector Backup Files (.eppb) larger than 200 MB can only be uploaded
from the console of the appliance. We recommend that you contact Customer Support when a created
.eppb file exceeds this 200 MB limit.
:::


![Upload System Backup](uploadsystembackup.webp)

From this section, you can schedule an automatic backup routine by setting a trigger condition, the
System Backup time interval. The routine can be set to run daily, weekly, monthly and so forth. The
Scheduler will also prompt the administrator with the Last Automatic System Backup reminder.

:::info
A scheduled routine is recommended in order to prevent unwanted loss.
:::


![Schedule an automatic backup routine](availablebackups.webp)

### From the Console

Endpoint Protector offers the option to revert the system to a previous state from the
administrative console on which the initial configuration occurs.

![Endpoint Protector offers the option to revert the system to a previous state from the administrative console on which the initial configuration occurs.](administrativeconsole.webp)

The Number 2 (System Backup) menu presents you with the following options:

- System Restore – can be performed if a system backup has been performed prior to the event, using
the web interface
- Import – can be performed if a .eppb file has been downloaded and saved on an FTP server
- Export – can be performed in order to save existing backups on an existent FTP server

To either import or export the .eppb files, an administrator will need to provide the system a valid
FTP IP address and the path inside its filesystem to the .eppb file.

An example is shown below:

![An administrator will need to provide the system a valid FTP IP address and the path inside its filesystem to the .eppb file](ftpconnectiondetails.webp)

## System Backup v2

From this section, you can migrate the database (entities, rights, settings, policies,
configurations, etc.) from an older Endpoint Protector Server to a newer one.

:::note
This feature is not intended as a replacement for the System Backup functionality but
rather as a migration tool from older Endpoint Protector images to the ones starting with version
5.2.0.6.
:::


The version of the old Server and the new Server will have to be the same. Before starting the
migration process, make sure both Servers have the same version (e.g.: update the old server to
5206, aligning it with the new server that is about to be deployed).

System Backup v2 does not include logs, Audits or System Backups. If needed, these should be
downloaded before proceeding.

**Example**

The initial Endpoint Protector deployed was version 4.4.0.7. Over time, updates were applied though
the Live Update section (deprecated starting with the 2509 version), bringing the appliance to Endpoint Protector version 5.2.0.6.
While these constantly included patches and security updates, they did not include a full roll-out of a new core
OS version (e.g.: the appliance is still running on Ubuntu 14.04 LTS).

As Ubuntu 14.04 no longer receives security patches since 2019, those that want to migrate to a
Server running on the latest Ubuntu LTS version should take advantage of this functionality.

![Migrate the database (entities, rights, settings, policies, configurations, etc.) from an older Endpoint Protector Server to a newer one.](listofsystembackups.webp)

### Creating a System Backup v2 (Migration)

You can create a new migration backup from the System Maintenance, System Backup v2 section.
Expand Down Expand Up @@ -172,3 +49,11 @@ should be turned off. Its IP would then have to be reassigned to the new Applian
deployed Endpoint Protector Clients to start communicating with the new Appliance.

![Importing and Restore (Migrate)](importingrestore.webp)

:::warning
Once deleted, a backup cannot be recovered.
:::

:::info
The Endpoint Protector Server cannot process backup files larger than 200 MB. If a created backup file exceeds this limit, we recommend that you contact Customer Support for assistance.
:::
Binary file not shown.
4 changes: 4 additions & 0 deletions docs/endpointprotector/admin/systemmaintenance/overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -102,6 +102,10 @@ The Backup export CSV file will differ based on the Endpoint Protector Server v
- For Endpoint Protector 5.7.0.0, reports, only one file containing all threats discovered, separated
by an underscore

:::warning
The audit log backups feature allows you to create copies and/or dumps of logs and file shadows into an export file, either manually or on a scheduled basis. Please note that the initial storage location for these export files is not suitable for long-term storage. It is essential that administrators download and store these files in secure locations to ensure their safety. In SaaS environments, be aware that export files may be lost during the upgrade process, so regular downloading and secure storage are crucial.
:::

### Audit Log Backup Scheduler

While the Audit Log Backup starts the backup instantly, the Audit Log Backup Scheduler provides the
Expand Down
Loading