Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 0 additions & 23 deletions apps/docs/content/elasticsearch/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -74,29 +74,6 @@ envSecrets:
Changes to HEAP_PERCENT require a service restart to take effect.
:::

## Backup

Elasticsearch backups are created using `elasticdump`:

- **Format**: `.gz` (per index/component dump)
- **Tooling**: `elasticdump`
- **Compression**: Gzip compressed JSON data

For backup configuration, scheduling, retention policies, and management options, see the [Zerops Backups](/features/backup) documentation.

### Restoring Backups

To restore an Elasticsearch backup:

1. **Download** the backup file (`.gz`) from the Zerops UI
2. **Extract** the compressed files to access the JSON data
3. **Prepare** your target environment (clean existing indices or use a new instance)
4. **Restore** using either:
- **elasticdump tool**: Use the same tool that created the backup for restoration via Zerops VPN or during deployment
- **Elasticsearch API**: Import the data through REST API [calls](https://www.elastic.co/docs/deploy-manage/tools/snapshot-and-restore/restore-snapshot)

For assistance with the restoration process, contact Zerops support.

## Example Configuration

```yaml
Expand Down
2 changes: 1 addition & 1 deletion apps/docs/content/features/backup.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ Zerops provides an automated, secure backup system for supported services. This

## Supported Services

Zerops provides automated backup functionality for the following services. For specific backup format details and restore instructions, visit each service's documentation: [MariaDB](/mariadb/how-to/backup), [PostgreSQL](/postgresql/how-to/manage#backups), [Qdrant](/qdrant/overview), [Elasticsearch](/elasticsearch/overview), [NATS](/nats/overview), [Meilisearch](/meilisearch/overview), [Local Storage](/local-storage/how-to/manage#backups), and [SeaweedFS](/seaweedfs/overview#backup-and-recovery).
Zerops provides automated backup functionality for the following services. For specific backup format details and restore instructions, visit each service's documentation: [MariaDB](/mariadb/how-to/backup), [PostgreSQL](/postgresql/how-to/manage#backups), [Qdrant](/qdrant/overview), [NATS](/nats/overview), [Meilisearch](/meilisearch/overview), [Local Storage](/local-storage/how-to/manage#backups), and [SeaweedFS](/seaweedfs/overview#backup-and-recovery).

## Managing Backups in the UI

Expand Down
5 changes: 2 additions & 3 deletions apps/docs/content/guides/backup.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -6,11 +6,11 @@ description: "Zerops auto-backs up databases and storage daily (00:00-01:00 UTC)
Zerops auto-backs up databases and storage daily (00:00-01:00 UTC) with X25519 encryption; backups are retained for 7 days minimum after service/project deletion.

## Supported Services
MariaDB, PostgreSQL, Qdrant, Elasticsearch, NATS, Meilisearch, Local Storage, SeaweedFS.
MariaDB, PostgreSQL, Qdrant, NATS, Meilisearch, Local Storage, SeaweedFS.

**ClickHouse**: not on the standard auto-backup path — back it up with the native `BACKUP ALL ...` SQL command (super user), stored as `.tar.gz`.

**Not supported**: Runtimes, Object Storage (use S3 lifecycle policies), Valkey/KeyDB (in-memory).
**Not supported**: Runtimes, Object Storage (use S3 lifecycle policies), Valkey/KeyDB (in-memory), Elasticsearch.

## Schedule Options
- No backups
Expand Down Expand Up @@ -46,7 +46,6 @@ End-to-end with X25519 per-project keys. Decrypted only on download.
|---------|---------------|
| PostgreSQL | `pg_dump` → `.zip` (per-schema custom-format `-Fc` dumps) |
| MariaDB | `mariabackup` → `.xb.gz` (xbstream + gzip) — **not** `mysqldump` (that is the manual-export tool, a different operation) |
| Elasticsearch | elasticdump → `.gz` |
| Meilisearch | `.dump` |
| Qdrant | `.snapshot` |
| NATS | `.tar.gz` |
Expand Down
79 changes: 0 additions & 79 deletions apps/docs/content/references/import.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -89,22 +89,6 @@ services:
minContainers: 2
# Maximum number of containers
maxContainers: 6
# Full nginx config
nginxConfig: |-
server {
listen 80 default_server;
listen [::]:80 default_server;

server_name _;
root /var/www;

location / {
try_files $uri $uri/ /index.html;
}

access_log syslog:server=unix:/dev/log,facility=local1 default_short;
error_log syslog:server=unix:/dev/log,facility=local1;
}
# Zerops.yaml configuration
zeropsSetup: backendapi
zeropsYaml:
Expand Down Expand Up @@ -218,7 +202,6 @@ The Service Configuration section is divided into multiple subsections for bette
- [**Service Basic Configuration**](#service-basic-configuration) - Core parameters like hostname, type, mode, and environment variables
- [**Service Vertical Autoscaling**](#service-vertical-autoscaling) - CPU, RAM, and disk scaling settings
- [**Service Horizontal Autoscaling**](#service-horizontal-autoscaling) - Container count scaling settings
- [**Service Nginx Configuration**](#service-nginx-configuration) - Custom web server settings
- [**Service zerops.yaml Configuration**](#service-zeropsyaml-configuration) - Build and run configurations

<Dropdown>
Expand Down Expand Up @@ -279,22 +262,6 @@ services:
minContainers: 2 # Minimum number of containers (default: 1, max: 10)
maxContainers: 6 # Maximum number of containers (max: 10)

# Nginx configuration
nginxConfig: |- # Custom nginx configuration
server {
listen 80 default_server;
listen [::]:80 default_server;
server_name _;
root /var/www/public;

location / {
try_files $uri $uri/ /index.html;
}

access_log syslog:server=unix:/dev/log,facility=local1 default_short;
error_log syslog:server=unix:/dev/log,facility=local1;
}

# Zerops.yaml configuration
zeropsSetup: backendapi # Service setup name from zeropsYaml or repo
zeropsYaml: # Full zerops.yaml configuration
Expand Down Expand Up @@ -661,52 +628,6 @@ The `minContainers` and `maxContainers` parameters allow you to define the minim
The `mount:` field of the deprecated [Shared Storage](/shared-storage/overview) is no longer accepted, an import containing it fails with `yamlMountDeprecated`. Mount a [SeaweedFS](/seaweedfs/overview) service from the runtime's [`startCommands`](/zerops-yaml/specification#startcommands-) in zerops.yaml, or mount a [Local Storage](/local-storage/overview) volume through the [`volume` field](/zerops-yaml/specification#volume-). Existing setups can be moved with the [SeaweedFS migration guide](/seaweedfs/how-to/migrate-from-shared-storage).
:::

### Service Nginx Configuration

The nginx configuration defines the nginx settings for the service.

<table className="w-full my-1.5 whitespace-nowrap">
<thead>
<tr>
<th className="w-fit">Field</th>
<th className="w-fit">Type</th>
<th className="w-fit">Description</th>
</tr>
</thead>
<tbody>
<tr>
<td className="w-fit font-semibold">nginxConfig</td>
<td className="w-fit">string (multiline)</td>
<td className="w-full">Insert full nginx config.</td>
</tr>
</tbody>
</table>

```yaml
#yamlPreprocessor=on
services:
- hostname: app
type: php-nginx@8.4
enableSubdomainAccess: true
nginxConfig: |-
server {
listen 80 default_server;
listen [::]:80 default_server;

server_name _;
root /var/www;

location / {
try_files $uri $uri/ /index.html;
}

access_log syslog:server=unix:/dev/log,facility=local1 default_short;
error_log syslog:server=unix:/dev/log,facility=local1;
}
```

The `nginxConfig: |-` parameter allows you to specify a custom nginx configuration for the service.

### Service zerops.yaml Configuration

The `zeropsSetup` and `zeropsYaml` parameters provide flexibility in how you define and use your service configurations. Both parameters are optional and work together in the following ways:
Expand Down
Loading
Loading