mirror of
https://github.com/Dokploy/website.git
synced 2026-06-15 20:25:25 +02:00
95682a01c2
- Introduced new MDX components and configuration files for the documentation site. - Added various images and icons to enhance the visual representation of the documentation. - Updated package.json and pnpm-lock.yaml to include new dependencies for the documentation. - Created a .gitignore file for the new docs app to manage ignored files effectively. - Enhanced README with instructions for restarting the dev server after adding new MDX files.
61 lines
2.1 KiB
Plaintext
61 lines
2.1 KiB
Plaintext
---
|
|
title: Backups
|
|
description: 'Learn how to create and restore backups of your Dokploy applications and services.'
|
|
---
|
|
|
|
import { Callout } from 'fumadocs-ui/components/callout';
|
|
|
|
Dokploy provides a comprehensive backup and restore system that saves your entire Dokploy file system and database to ensure your data is safe and recoverable.
|
|
|
|
## Prerequisites
|
|
|
|
Before using the backup feature, you need to have an S3 destination configured in your system. This is where your backups will be stored.
|
|
|
|
## Creating Backups
|
|
|
|
To create a backup:
|
|
|
|
1. Navigate to Web Server → Backups
|
|
2. Select "Create Backup"
|
|
3. Choose your S3 destination
|
|
4. Configure the backup schedule using cron syntax (optional)
|
|
|
|
When a backup is created, Dokploy will:
|
|
- Back up the PostgreSQL database (`dokploy-postgres`)
|
|
- Save the Dokploy file system (`/etc/dokploy`)
|
|
- Combine and compress both into a single backup file (.zip)
|
|
- Upload the backup to your specified S3 destination
|
|
|
|
## Restoring Backups
|
|
|
|
To restore a backup:
|
|
|
|
1. Navigate to Web Server → Backups
|
|
2. Select "Restore Backup"
|
|
3. Choose the S3 destination containing your backup
|
|
4. Browse and select the backup file you want to restore
|
|
5. Review the summary of files to be restored
|
|
|
|
During restoration, Dokploy will:
|
|
- Clear the existing `/etc/dokploy` directory and replace it with the backup contents
|
|
- Drop the existing `dokploy-postgres` database
|
|
- Disconnect current database users
|
|
- Restore the database from the backup
|
|
|
|
<Callout type="info">
|
|
After restoration is complete, you may need to log in again. If necessary, you can restart Traefik to ensure all services are properly configured.
|
|
</Callout>
|
|
|
|
## Post-Restoration Steps
|
|
|
|
After restoring a backup, especially if you're restoring to a different server, consider the following:
|
|
|
|
1. If your server IP has changed:
|
|
- Update the IP address in Web Server → Server → Update IP
|
|
- Reconfigure Git providers if they were set up using IP addresses
|
|
- Update your DNS records to point to the new IP
|
|
- Recreate Traefik.me domains if you're using them
|
|
|
|
2. If you're using domain names instead of IPs for Git providers, no additional configuration is needed.
|
|
|