Attach a policy to a data source

A policy doesn't run by itself – it runs against the data sources you attach it to. Attach the same policy to ten databases and they all back up on the same schedule, with the same retention, to the same storage destination.

The destination is part of the policy itself (set at policy creation), so attaching is now just "which database does this policy run on?".

In the dashboard

The first scheduled run fires at the next matching cron time. Watch Backup jobs on the data source to confirm.

Reuse one policy across many databases

The whole point of policies is reuse. Attach daily-7day to ten databases and you get ten independent backup schedules running concurrently (subject to your concurrency limit). Each run produces its own backup file and job record.

Attach multiple policies to one data source

You can attach different policies to layer retention:

• hourly-2day for fast point-in-time recovery on a tight window.
• daily-30day for medium-term retention.
• weekly-1year for long-term archives.

All three policies fire independently and each produces its own backup file. Costs are additive – you're paying for three copies' worth of storage.

Pause an attachment

See Pause and resume.

Detach a policy

1. Open the data source.
2. In Backup policies, find the row for the policy you want to detach.
3. Click the trash button.

Detaching stops new runs immediately. Existing backup files stay in storage until they age out per the policy's retention rule (or until you delete the data source).