Knowledge base · Backups

Schedules, retention and alerts

How backup windows work, how retention is enforced and crypto-shredded, and when VaultKeep emails you.

The schedule

Each project has one schedule, under the Schedule tab:

If an organization has more projects than its plan allows (for example after a downgrade), only the oldest N projects keep backing up until you remove some.

Retention and crypto-shredding

Every night at 04:10 UTC a sweep looks for backups older than their retention. For each one it:

  1. deletes the objects from storage (managed R2 or your own destination);
  2. destroys the backup's wrapped data key;
  3. marks the backup as deleted and writes an audit entry with the number of objects removed.

Because the key is destroyed, an object that somehow survives step 1 is permanently unreadable. Storage-sync backups share unchanged objects with newer runs; the sweep keeps any object a newer manifest still references.

If your own destination is unreachable on the night of the sweep, the key is still destroyed and the failure is recorded in the audit entry. The leftover ciphertext can be cleaned up later, or left, since nobody can read it.

Alerts

Owners and admins are emailed when:

Every alert links to the project. There is no separate notification setting yet; if you need a webhook or a Slack integration, tell us at support@vaultkeep.dev.

Running things by hand

On the project page: Back up now, Sync storage (if configured), and Verify on any successful backup. Manual jobs go to the front of the queue.


Still stuck? Email support@vaultkeep.dev with your project name (never your connection string) and we'll take a look.