Trigger your backup system on a reliable schedule without maintaining your own cron server.
Why Use RunLater for Backups?
- No server to maintain
- Automatic retries if trigger fails
- Full logging of every backup trigger
- Timezone-aware scheduling
Common Setup Patterns
Supabase
Supabase has built-in backups, but you can trigger custom backup logic via Edge Functions. Create an Edge Function that runs your backup, then schedule it with RunLater.
PlanetScale
Use PlanetScale's API to create backup branches. Add your API key in the headers.
Custom Backup Script
If you have a backup script on your server, expose it as an endpoint and trigger it with RunLater.
Example: Nightly Backup at 3 AM
- URL:
https://api.yourservice.com/backup - Method: POST
- Headers:
Authorization: Bearer your-api-key- Schedule:
0 3 * * *(Daily at 3 AM UTC)
Best Practices
- Set a high retry count (5-10) for critical backups
- Use a longer timeout if backups take time to initiate
- Monitor the logs to ensure backups are triggering
- Consider multiple schedules for redundancy