# How to Back Up All Files and Deleted Files on Employee Endpoints

Canonical: https://www.nsecsoft.com/en/course/backup-2.html

Language: en-US

Updated: 2026-11-04T08:00:37.794517Z

In enterprise data security management, file backup can be used to establish a baseline of employee endpoint files and to retain evidence copies of deleted files\. For scenarios that need to take into account pre\-preservation, post\-event recovery and audit evidence collection, it is recommended that administrators plan in the file backup strategy first full disk \[…\]

In enterprise data security management,

**file backup**

can be used to establish a baseline of employee endpoint files and to retain evidence copies of deleted files. For scenarios that need to take into account pre-preservation, post-event recovery and audit evidence collection, it is recommended that administrators plan in the

**file backup**

strategy

**first full disk backup**

and

**backup when files are deleted**

, covering "full basic backup" and "key deletion behavior traces" respectively.

It should be noted that the goals of full disk backup and deleted file backup are not the same. The former is more suitable for establishing an initial backup baseline to facilitate subsequent recovery, migration, and audit troubleshooting; the latter is more suitable for retaining evidence when files are deleted to facilitate verification of accidental deletion, malicious deletion, or audit evasion. Therefore, the management objectives should be clarified before implementation, and then decide whether to activate one of them individually or both at the same time.

#### **Back up all files on employee endpoints**

1\. Click

**Data Security**

→

**File Backup**

on the console to enter the file backup audit record interface.

2\. Click

**Policy**

to enter the backup policy setting interface.

3\. Click

**Backup Settings**

and check

**Perform full disk backup for the first time**

. This option is used to create a more complete base backup of the endpoint files when the policy is first executed.

![](<https://www.nsecsoft.com/site-assets/bd479a7e2f6829c160217f5ef8075eb7317c364c4447adfeb14f5da8239c94ec/58609ce4201102617e4b9308b5a1510e4ded6151f09eca74f0dc0839beaa96a6/2acecef6abf448f8df39ec636c03af6187b48ce3931513cbef14a589802ab0e3/3-all-files-1.png>)

4\. Click

**Specify File**

:

-   If you want the employee endpoint to continue to back up related files during subsequent file operations, click **Add** to create a rule.
-   File path is set to **No limit on file path**.
-   File size is set to **No limit on file size**
-   Check the file types that need to be backed up
-   Click **OK** to save the rule

5\. After the policy setting is completed, confirm that the endpoint for applying the policy is correct and click

**Apply**

to deliver the full backup policy.

A full disk backup is more suitable for establishing an initial backup baseline. For environments with a large number of endpoints and large files, it is recommended to give priority to trial runs on key endpoints or sample endpoints, and then decide whether to expand the scope after confirming the backup time, network usage, and storage growth.

#### **Back up employee deleted files**

If the enterprise is more concerned about accidental deletion recovery, malicious deletion tracing, or deletion behavior forensics, it can further enable

**Backup when files are deleted**

in the same policy. This capability will retain the corresponding backup copy when a deletion occurs on the endpoint to facilitate subsequent verification by the administrator.

1\. Click

**Backup Settings**

in the policy settings interface of

**File Backup**

.

2\. Check

**Back up when files are deleted**

.

3\. After confirming that the policy application endpoint is correct, click

**Apply**

to deliver the endpoint "Delete File Backup" policy.

After the policy takes effect, it is recommended to delete a test file on the test endpoint, and then go back to

**Data Security**

→

**File Backup**

to check whether the corresponding backup record has been generated. Administrators can also cooperate with the

**Backup Reason**

condition to further confirm whether the deleted files are correctly marked and retained.

![](<https://www.nsecsoft.com/site-assets/bd479a7e2f6829c160217f5ef8075eb7317c364c4447adfeb14f5da8239c94ec/31d1d1b6ebf3cd10a242effa1ad1987e6dc5034188dd578ad99779d48967779f/4f065e11458a9071650abd4644a136ad5ab5ea92c10131ce0f79f66859a4eaef/3-all-files-2.png>)

#### **Implementation Suggestions**

-   **Perform full disk backup for the first time** is more suitable for establishing an initial backup baseline. It is recommended to combine the **specified file** rules for continuous optimization in the future.
-   **Backup when files are deleted** is more suitable for recovering accidentally deleted files, tracking abnormal deletion behavior and retaining evidence collection evidence.
-   If an enterprise only cares about office documents, design files or code data, it is recommended to appropriately converge on file types to avoid excessive storage costs caused by undifferentiated backups.
-   For key positions, it is recommended to combine deleted file backup with **File Operation** audit to facilitate the restoration of the complete track before and after deletion.
-   Before officially distributing it on a large scale, it is recommended to verify the backup time, resource usage and subsequent query results on a sample endpoint.
