# Local Storage

URL: /docs/storage-providers/local

Source: https://github.com/easypanel-io/monorepo/blob/main/apps/website/content/docs/storage-providers/local.mdx

Store backups at a filesystem path on the Easypanel server.



A Local provider writes backup data to a path on the Easypanel server. It is
simple and useful for temporary copies, but it is not an off-server disaster
recovery destination.

<Callout type="warn">
  A local backup can be lost with the same disk, filesystem, or server as the
  original data. Do not use Local as the only copy of production data.
</Callout>

## Configure local storage [#configure-local-storage]

1. Choose an absolute filesystem path with enough capacity. The form suggests:

   ```text
   /etc/easypanel/backups
   ```

2. Create the directory or ensure its parent can be created and written by the
   Easypanel server process.

3. Open **Settings → Server → Storage Providers**.

4. Select **Add Provider → Local**.

5. Enter:
   * **Name**, used in backup forms and action logs;
   * **Path**, the base directory for this provider.

6. Save the provider.

7. Create a backup configuration and perform a manual run.

8. Verify the file on the server and check the backup action log.

Easypanel saves a Local provider without checking whether the path exists or is
writable. The manual run is the first complete validation.

## Destination paths [#destination-paths]

The backup's destination path is joined below the provider path. For example:

```text
Provider path:    /etc/easypanel/backups
Destination path: production/orders-postgres
Final directory:  /etc/easypanel/backups/production/orders-postgres
```

Use one destination path per configuration. Database retention deletes older
files under its path, while volume backup synchronizes the directory to match
the source volume.

## Capacity and monitoring [#capacity-and-monitoring]

Local backups consume the same server storage pool unless the path points to a
separately mounted filesystem. Monitor:

* free space and inode availability;
* filesystem mount health;
* backup duration and action logs;
* database retention;
* provider-side snapshots when the path is on a separately managed volume.

A full backup filesystem can also affect other services when it shares their
disk.

## Recovery [#recovery]

Database restore can read a backup through the Local provider by its exact
destination path and filename. Volume recovery remains manual.

If the Easypanel server itself is unavailable, local files are recoverable only
when the underlying disk or filesystem is still accessible. Copy important
backups to an independent destination.

## Edit or remove the provider [#edit-or-remove-the-provider]

Editing **Path** changes where future backup actions read and write. It does not
move files from the previous directory.

Removing the provider deletes only its Easypanel configuration. It does not
delete the directory or files, but backup configurations referencing the old
provider ID will fail.

## Troubleshooting [#troubleshooting]

### Backup reports a missing path or permission error [#backup-reports-a-missing-path-or-permission-error]

* Use an absolute provider path.
* Confirm that the directory exists or its parent can be written.
* Check filesystem ownership and permissions.
* Confirm that the filesystem is mounted and not read-only.

### Backup fails because the disk is full [#backup-fails-because-the-disk-is-full]

Free capacity, reduce database retention, or move the provider to another
filesystem. Confirm that incomplete files are not consuming unexpected space.

### Files appear in an unexpected location [#files-appear-in-an-unexpected-location]

Check both the provider's base **Path** and the backup configuration's
**Destination Path**. Editing either setting affects future actions but does
not relocate old files.

See [Storage Providers](/docs/storage-providers) for shared provider behavior
and [Backups](/docs/backups) for recovery planning.