Skip to content
Docs
strackt.io Open app

Remove a service

Retire a database or cache you no longer need — safely, with a final snapshot and automatic cleanup.

Remove a service

When a database or cache has outlived the app that needed it, you can retire it from the service's own page with Remove.

Before it can go

A service can't be removed while something still depends on it. strackt checks first and tells you exactly what's in the way — usually one of:

  • An application is still connected to it. You don't have to disconnect it first — the confirmation lists every application that loses access, and removing the service unbinds them for you.
  • It still holds data. A database moves to a recoverable state instead of being deleted outright. A cache is torn down straight away, so the confirmation shows what its keyspaces still hold before you commit.
  • Something is already happening to it. A restore, another running operation, or a move to a different server has to finish first. So does a data move — though a queued one can be cancelled.
  • Environments still back up to it. For a backup receiver, turn off Server backup on each of them first.

Whichever applies, strackt names it on the service's page and in the message you get back if a removal is refused, along with what to do about it.

Once nothing depends on it, the Remove action is ready.

What happens when you remove it

Removal is safe and unattended:

  1. strackt takes a final snapshot first, so there's a recovery point if you ever need what was on it.
  2. The service moves into a retiring state and the work runs in the background — you don't have to wait on the page.
  3. When it's done, you're notified. If something goes wrong, the service shows an error so you can retry.

The final snapshot is kept for a limited window and then cleared automatically, so old retired services don't pile up storage.

Disconnecting an app (automatic cleanup)

You don't have to remove a whole service just to detach one app. When you disconnect an application from a service — or delete an environment that used it — strackt automatically cleans up that app's own database, its user account, and its stored credentials on the service. Other apps sharing the same service are untouched. There's nothing to tidy up by hand and no leftovers.

Was this helpful?