Skip to main content
Open Services → Remnawave, select the connection and go to the tab Backups. Before creating a profile, configure the performer and make sure that an active PostgreSQL is found on the status tab: local container or external database.

Create a profile

  1. Click Add a profile of.
  2. Specify the name, storage location, cron schedule and storage period.
  3. For S3, fill in the endpoint, bucket, region, access key, and secret key. There are no additional fields for local storage.
  4. Save the profile, then click Check access.
Compose and PostgreSQL connection settings are not requested by the profile: they are taken by the detected runtime. After saving the secret key S3 is not shown in the form. To replace it, enter a new value when editing the profile. The local archive is stored in the managed directory of the artist: on the panel server for local runtime or on the Remnawave server for agent runtime. When you select S3, the archive is uploaded to the specified bucket. The access checker accesses the found PostgreSQL and returns the version and size of the database or the error message.

External PostgreSQL

The active base is determined by the actual DATABASE_URL of the Remnawave container. For the external base, copying and recovery are performed from the Remnawave host. via PostgreSQL client in the network panel. Agent on the database server is not needed. Non-standard port, IPv6 and TLS are supported. available in the Remnawave container; the image of the PostgreSQL client is on the host of the performer. Prior to completion, the target is re-checked if the address, port, base or The user has changed, repeat the detection before starting again. Archives, integrity verification, S3 and retention period use the usual process. More on requirements and switching: External PostgreSQL.

Start copying.

In the profile card, click C Create a backup now. Status and result will appear in the same tab. For one profile, you cannot run a second backup while the previous one is in line or running. Axottle checks the cron schedule once a minute for the profiles that are turned on, and after successful launch, the profile shelf life applies. Card buttons also allow you to change the profile, delete it, and open related activities.

Check the archive and restore the base

Disclose your profile history and press the check button next to the archive, check the size and checksum, and for agency runtime, the tied agent does the check. Recovery is only available for a successful backup.Push the restore button, read the plan and confirm the action.The operation replaces the current Remnawave base, so create a fresh backup before it and make sure the right archive is selected.

Verification

  1. Make sure the runtime lists the PostgreSQL you want: a container or an external database address.
  2. Create a profile and run Check access.
  3. Run the backup manually and wait for the status of “successful” in history.
  4. Check the checksum for the created archive.
History contains a successful archive with a size, and verification does not report error.

Rollback

Deleting the profile also removes its backup log from Axottle. It does not delete archives from external S3 storage automatically. Code validation is not a substitute for creating and verifying an archive in your installation.