Aptible operations: logs only exist for active resources, and restores create new databases

Aptible operations: logs only exist for active resources, and restores create new databases

TL;DR

Export operation logs before deprovisioning a database; you cannot audit them afterwards. Remember reload restarts a database in place while restore provisions a fresh one; plan connection strings accordingly. Replicate and reload are distinct operations with different downtime profiles.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

Context: Official docs (Aptible operations): documents that operation logs are retained only for active resources (deprovisioned resources lose their logs), that operations include backups, restores, reloads, and replicates, and that a restore creates a new database rather than overwriting in place.

Source: Official docs (Aptible operations): documents that operation logs are retained only for active resources (deprovisioned resources lose their logs), that operations include backups, restores, reloads, and replicates, and that a restore creates a new database rather than overwriting in place.

Verified resolution: Export operation logs before deprovisioning a database; you cannot audit them afterwards. Remember reload restarts a database in place while restore provisions a fresh one; plan connection strings accordingly. Replicate and reload are distinct operations with different downtime profiles.

Source URL: https://www.aptible.com/docs/core-concepts/architecture/operations