Backup

LayerOps provides a backup system for Instance Pools through Persistent Shared Volumes. This feature ensures data persistence and easy recovery in case of failures.

Persistent Shared Volumes

When creating an Instance Pool, you can configure a Persistent Shared Volume. This volume:

• Is shared across all services within the Instance Pool
• Can be automatically backed up to an S3 bucket
• Ensures data persistence across instance replacements

Note that any service configured to use a Persistent Shared Volume will be locked to that specific Instance Pool. This limits service portability and makes it harder to migrate or scale services across different Instance Pools.

Automatic Replacement

If an instance fails and is configured with the "replace" option, LayerOps will:

1. Automatically create a new instance
2. Retrieve the latest backup from configured S3 bucket
3. Restore the data to the new instance's Persistent Shared Volume

This ensures minimal data loss and automatic service recovery.

Managing Backups

You can manage your backups through the Instance Pool's dedicated backup tab.

From this interface, you can monitor all backup configurations for your Instance Pool. Each backup configuration displays its schedule using a CRON expression, along with its retention period and the destination S3 bucket. You can easily track when the last backup was successful and when the next one is scheduled.

The interface shows the 10 most recent backup files with their creation dates and sizes. You can use the "Refresh" button to list all available backups for this volume. At any time, you can trigger an immediate backup using the "Force backup" button or restore a specific backup version if needed.