Skip to content

Commit c121099

Browse files
update for audit log backup and removal of backupv1
1 parent 542d38d commit c121099

File tree

5 files changed

+12
-123
lines changed

5 files changed

+12
-123
lines changed
Binary file not shown.
Binary file not shown.

docs/endpointprotector/admin/systemmaintenance/backup.md

Lines changed: 8 additions & 123 deletions
Original file line numberDiff line numberDiff line change
@@ -16,129 +16,6 @@ The System Backup feature allows you to create and manage comprehensive backups
1616
Using the web interface or administrative console, you can perform backups, restore previous
1717
versions, and set up automatic routines to ensure your data is consistently protected.
1818

19-
### From the Web Interface
20-
21-
This module allows you to make complete system backups.
22-
23-
![Allows you to make complete system backups](listofsystembackups.webp)
24-
25-
To view the list of current backups, go to **System Maintenance****System Backup v2**.
26-
27-
To restore the system to an earlier state, click **Restore** next to the entry and then confirm your
28-
action.
29-
30-
:::warning
31-
Once deleted, a backup cannot be recovered.
32-
:::
33-
34-
35-
The Download button will prompt you to save the **.eppb backup file** on the local drive. It is
36-
recommended to keep a good record of where these files are saved.
37-
38-
:::warning
39-
When using the Restore Backup feature, we recommend requesting assistance from customer
40-
support.
41-
:::
42-
43-
44-
![Allows you to make complete system backups](createsystembackup.webp)
45-
46-
On the Make Backup section, you have the following options:
47-
48-
- Save the Database content – the backup file will contain all the devices, rights, logs, settings
49-
and policies present on the Endpoint Protector server at the making of the backup
50-
- Save the Application sources – the backup will contain files such as the Endpoint Protector clients
51-
and others related to the proper functioning of the server
52-
53-
:::note
54-
The System Backup will not contain nor preserve the IP Address, File Shadowing copies or
55-
the Temporary Logs Files.
56-
:::
57-
58-
59-
The second section, Status, returns the state of the system. If a backup creation is in progress, it
60-
will be reported as seen below.
61-
62-
![System Backup Status](systembackupstatus.webp)
63-
64-
If the system is idle, the button will return the last known status, which by default is set at 100%
65-
done.
66-
67-
The next menu, Upload, allows you to populate the backup list with .eppb files from the local
68-
filesystem. This functionality is useful in cases of server migration or crash recovery.
69-
70-
:::info
71-
Endpoint Protector Backup Files (.eppb) larger than 200 MB can only be uploaded
72-
from the console of the appliance. We recommend that you contact Customer Support when a created
73-
.eppb file exceeds this 200 MB limit.
74-
:::
75-
76-
77-
![Upload System Backup](uploadsystembackup.webp)
78-
79-
From this section, you can schedule an automatic backup routine by setting a trigger condition, the
80-
System Backup time interval. The routine can be set to run daily, weekly, monthly and so forth. The
81-
Scheduler will also prompt the administrator with the Last Automatic System Backup reminder.
82-
83-
:::info
84-
A scheduled routine is recommended in order to prevent unwanted loss.
85-
:::
86-
87-
88-
![Schedule an automatic backup routine](availablebackups.webp)
89-
90-
### From the Console
91-
92-
Endpoint Protector offers the option to revert the system to a previous state from the
93-
administrative console on which the initial configuration occurs.
94-
95-
![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)
96-
97-
The Number 2 (System Backup) menu presents you with the following options:
98-
99-
- System Restore – can be performed if a system backup has been performed prior to the event, using
100-
the web interface
101-
- Import – can be performed if a .eppb file has been downloaded and saved on an FTP server
102-
- Export – can be performed in order to save existing backups on an existent FTP server
103-
104-
To either import or export the .eppb files, an administrator will need to provide the system a valid
105-
FTP IP address and the path inside its filesystem to the .eppb file.
106-
107-
An example is shown below:
108-
109-
![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)
110-
111-
## System Backup v2
112-
113-
From this section, you can migrate the database (entities, rights, settings, policies,
114-
configurations, etc.) from an older Endpoint Protector Server to a newer one.
115-
116-
:::note
117-
This feature is not intended as a replacement for the System Backup functionality but
118-
rather as a migration tool from older Endpoint Protector images to the ones starting with version
119-
5.2.0.6.
120-
:::
121-
122-
123-
The version of the old Server and the new Server will have to be the same. Before starting the
124-
migration process, make sure both Servers have the same version (e.g.: update the old server to
125-
5206, aligning it with the new server that is about to be deployed).
126-
127-
System Backup v2 does not include logs, Audits or System Backups. If needed, these should be
128-
downloaded before proceeding.
129-
130-
**Example**
131-
132-
The initial Endpoint Protector deployed was version 4.4.0.7. Over time, updates were applied though
133-
the Live Update section (deprecated starting with the 2509 version), bringing the appliance to Endpoint Protector version 5.2.0.6.
134-
While these constantly included patches and security updates, they did not include a full roll-out of a new core
135-
OS version (e.g.: the appliance is still running on Ubuntu 14.04 LTS).
136-
137-
As Ubuntu 14.04 no longer receives security patches since 2019, those that want to migrate to a
138-
Server running on the latest Ubuntu LTS version should take advantage of this functionality.
139-
140-
![Migrate the database (entities, rights, settings, policies, configurations, etc.) from an older Endpoint Protector Server to a newer one.](listofsystembackups.webp)
141-
14219
### Creating a System Backup v2 (Migration)
14320

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

17451
![Importing and Restore (Migrate)](importingrestore.webp)
52+
53+
:::warning
54+
Once deleted, a backup cannot be recovered.
55+
:::
56+
57+
:::info
58+
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.
59+
:::
Binary file not shown.

docs/endpointprotector/admin/systemmaintenance/overview.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -102,6 +102,10 @@ The Backup export CSV file will differ based on the Endpoint Protector Server v
102102
- For Endpoint Protector 5.7.0.0, reports, only one file containing all threats discovered, separated
103103
by an underscore
104104

105+
:::warning
106+
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.
107+
:::
108+
105109
### Audit Log Backup Scheduler
106110

107111
While the Audit Log Backup starts the backup instantly, the Audit Log Backup Scheduler provides the

0 commit comments

Comments
 (0)