Skip to main content
Version: 78.0.0

a9s Backups and Restores Considerations

This section describes concerns and limitations to be considered when using the a9s Service Backups and Restores.

a9s LogMe2​

Backups and restores are fully supported for a9s LogMe2. The backup process is based on OpenSearch's Snapshot functionality, which differs from the backup process of the other a9s Data Services.

Instead of exporting the data into a single backup file that is uploaded by the a9s Backup Agent, the a9s Backup Agent instructs OpenSearch to take a snapshot. OpenSearch then writes that snapshot directly into the snapshot repository configured by the Platform Operator on the backup storage.

As a consequence, a backup of an a9s LogMe2 Service Instance is not a single self-contained file; therefore, the manual downloading of backups is not provided for a9s LogMe2. Backups can still be created, listed and restored as usual through the a9s Service Dashboard, the a9s Public API, and the Cloud Foundry CLI.

Backups and restores are fully supported for a9s Search. The backup process is based on OpenSearch's Snapshot functionality, which differs from the backup process of the other a9s Data Services.

Instead of exporting the data into a single backup file that is uploaded by the a9s Backup Agent, the a9s Backup Agent instructs OpenSearch to take a snapshot. OpenSearch then writes that snapshot directly into the snapshot repository configured by the Platform Operator on the backup storage.

As a consequence, a backup of an a9s Search Service Instance is not a single self-contained file; therefore the manual downloading of backups is not provided for a9s Search. Backups can still be created, listed and restored as usual through the a9s Service Dashboard, the a9s Public API, and the Cloud Foundry CLI.

info

Please note that for all a9s Search Service Instances, backup sizes are displayed as 0 B in the backup metadata. This is expected behavior due to the nature of the snapshot process and does not indicate a backup failure or data loss.

This was fixed in anynines-deployment v78.0.0. Backups created afterwards report their actual size. The size of already existing backups is not recalculated retroactively, so 0 B entries remain visible until those backups are removed by the backup retention policy.