Add backups, migration, and DNS/mail guides
This commit is contained in:
@@ -16,7 +16,7 @@ export default defineConfig({
|
|||||||
sidebar: [
|
sidebar: [
|
||||||
{
|
{
|
||||||
label: 'Getting Started',
|
label: 'Getting Started',
|
||||||
items: [{ label: 'Overview', slug: 'overview' }, { label: 'Installation', slug: 'install' }, { label: 'Quickstart', slug: 'quickstart' }, { label: 'Operations', slug: 'operations' }, { label: 'Security', slug: 'security' }, { label: 'Troubleshooting', slug: 'troubleshooting' }],
|
items: [{ label: 'Overview', slug: 'overview' }, { label: 'Installation', slug: 'install' }, { label: 'Quickstart', slug: 'quickstart' }, { label: 'Backups and Restore', slug: 'backups-restore' }, { label: 'Migrations', slug: 'migrations' }, { label: 'DNS and Mail', slug: 'dns-mail' }, { label: 'Operations', slug: 'operations' }, { label: 'Security', slug: 'security' }, { label: 'Troubleshooting', slug: 'troubleshooting' }],
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
label: 'Admin Panel',
|
label: 'Admin Panel',
|
||||||
|
|||||||
53
doccs/site/src/content/docs/backups-restore.md
Normal file
53
doccs/site/src/content/docs/backups-restore.md
Normal file
@@ -0,0 +1,53 @@
|
|||||||
|
---
|
||||||
|
title: Backups and Restore
|
||||||
|
---
|
||||||
|
|
||||||
|
This guide covers backup strategy, schedules, retention, and restores.
|
||||||
|
|
||||||
|
## Backup types
|
||||||
|
|
||||||
|
- **Admin backups**: system-wide backups managed by administrators.
|
||||||
|
- **User backups**: per-account backups for self-service restore.
|
||||||
|
|
||||||
|
## Recommended strategy
|
||||||
|
|
||||||
|
- Keep at least one offsite destination.
|
||||||
|
- Use multiple retention windows (daily/weekly/monthly).
|
||||||
|
- Test restores regularly on a staging account.
|
||||||
|
|
||||||
|
## Configure schedules (admin)
|
||||||
|
|
||||||
|
1) Open **Admin → Backups**.
|
||||||
|
2) Add destinations (local and/or remote).
|
||||||
|
3) Create schedules and set retention.
|
||||||
|
4) Validate the first run completes successfully.
|
||||||
|
|
||||||
|
## User backups
|
||||||
|
|
||||||
|
Users can trigger and manage their own backups under **User → Backups**.
|
||||||
|
|
||||||
|
## Restore workflow
|
||||||
|
|
||||||
|
1) Choose a backup snapshot.
|
||||||
|
2) Select a restore scope (full account, database, or files).
|
||||||
|
3) Confirm the target account and overwrite options.
|
||||||
|
4) Review the restore logs and verify services.
|
||||||
|
|
||||||
|
## CLI examples
|
||||||
|
|
||||||
|
Create a backup for a user:
|
||||||
|
|
||||||
|
```
|
||||||
|
jabali backup create <user>
|
||||||
|
```
|
||||||
|
|
||||||
|
Restore a backup to a user:
|
||||||
|
|
||||||
|
```
|
||||||
|
jabali backup restore <path> --user=<user>
|
||||||
|
```
|
||||||
|
|
||||||
|
## Troubleshooting
|
||||||
|
|
||||||
|
- If restores fail, check `jabali-agent` and `jabali-queue` status.
|
||||||
|
- Review logs in `/var/www/jabali/storage/logs` and systemd logs.
|
||||||
36
doccs/site/src/content/docs/dns-mail.md
Normal file
36
doccs/site/src/content/docs/dns-mail.md
Normal file
@@ -0,0 +1,36 @@
|
|||||||
|
---
|
||||||
|
title: DNS and Mail Deliverability
|
||||||
|
---
|
||||||
|
|
||||||
|
This guide helps you ship reliable DNS and email delivery.
|
||||||
|
|
||||||
|
## DNS basics
|
||||||
|
|
||||||
|
- Ensure the panel hostname resolves to the server IP.
|
||||||
|
- If hosting DNS, add glue records at the registrar.
|
||||||
|
- Keep zone templates consistent for new domains.
|
||||||
|
|
||||||
|
## Required mail DNS records
|
||||||
|
|
||||||
|
- **PTR**: reverse DNS must match your mail hostname.
|
||||||
|
- **SPF**: authorize your server IP.
|
||||||
|
- **DKIM**: enable signing for outgoing mail.
|
||||||
|
- **DMARC**: enforce policy and reporting.
|
||||||
|
|
||||||
|
## Checklist
|
||||||
|
|
||||||
|
1) PTR set and matches `mail.your-domain`.
|
||||||
|
2) SPF includes your server IP.
|
||||||
|
3) DKIM published and active in your MTA.
|
||||||
|
4) DMARC policy set (start with `p=none` then tighten).
|
||||||
|
|
||||||
|
## Testing deliverability
|
||||||
|
|
||||||
|
- Send a test email to a mailbox at a major provider.
|
||||||
|
- Review headers for SPF/DKIM/DMARC pass.
|
||||||
|
- Use log files to confirm message flow.
|
||||||
|
|
||||||
|
## Logs
|
||||||
|
|
||||||
|
- Postfix: `/var/log/mail.log` (path may vary by distro)
|
||||||
|
- Rspamd: `/var/log/rspamd/rspamd.log`
|
||||||
37
doccs/site/src/content/docs/migrations.md
Normal file
37
doccs/site/src/content/docs/migrations.md
Normal file
@@ -0,0 +1,37 @@
|
|||||||
|
---
|
||||||
|
title: Migrations (cPanel and WHM)
|
||||||
|
---
|
||||||
|
|
||||||
|
Jabali supports imports from common panels with detailed logs and staged steps.
|
||||||
|
|
||||||
|
## cPanel migration
|
||||||
|
|
||||||
|
1) Upload the cPanel archive from **Admin → Migration** or **User → cPanel Migration**.
|
||||||
|
2) Run **Analyze** to validate the archive contents.
|
||||||
|
3) Review findings (domains, databases, mailboxes, forwarders, SSL).
|
||||||
|
4) Run **Restore** and monitor the live log output.
|
||||||
|
|
||||||
|
## WHM migration
|
||||||
|
|
||||||
|
1) Open **Admin → WHM Migration**.
|
||||||
|
2) Enter WHM credentials and select accounts.
|
||||||
|
3) Start the migration and track progress per account.
|
||||||
|
|
||||||
|
## CLI examples
|
||||||
|
|
||||||
|
Analyze a cPanel archive:
|
||||||
|
|
||||||
|
```
|
||||||
|
jabali cpanel analyze <file>
|
||||||
|
```
|
||||||
|
|
||||||
|
Restore a cPanel archive:
|
||||||
|
|
||||||
|
```
|
||||||
|
jabali cpanel restore <file> <user>
|
||||||
|
```
|
||||||
|
|
||||||
|
## Notes
|
||||||
|
|
||||||
|
- Some migration tabs appear only after a successful **Analyze**.
|
||||||
|
- Provide a sample cPanel backup to capture all tab screenshots.
|
||||||
Reference in New Issue
Block a user