Updated May 10, 2026 Manages a recurring backup schedule for a VM. The schedule auto-prunes backups older thanDocumentation Index
Fetch the complete documentation index at: https://docs.rafftechnologies.com/llms.txt
Use this file to discover all available pages before exploring further.
keep_count, so backups it creates must not be managed via raff_backup — that fights the retention engine. For one-shot backups, use raff_backup.
Example — daily
Example — weekly
Argument reference
Required
| Argument | Type | Description |
|---|---|---|
vm_id | string (UUID) | Source VM. ForceNew — point at a different schedule’s VM by replacing the resource |
frequency | string | daily or weekly |
time | string | Time of day, e.g. 08:00 or 8am |
keep_count | int | Number of backups to retain before auto-pruning |
Optional
| Argument | Type | Description |
|---|---|---|
day_of_week | string | Day of week (Monday–Sunday). Required when frequency = "weekly" |
Attribute reference (computed)
| Attribute | Description |
|---|---|
id | Schedule ID |
name | Auto-generated schedule name |
runtime | Next scheduled run time |
region | Region (mirrors the source VM’s region) |
price_per_hour | Hourly price in USD for the storage the schedule’s backups consume |
Lifecycle
| Operation | Behavior |
|---|---|
terraform apply (create) | Creates the schedule. The first backup runs at the next time slot |
Change frequency, time, day_of_week, keep_count | In-place update |
Change vm_id | Replacement — destroy + recreate |
terraform destroy | Deletes the schedule. Existing backups it created remain — delete via raff backup delete if no longer needed |
Importing existing schedules
Permissions
The API key needsvm.backup in the project. The system role Project Admin grants this.
Data sources
Related
raff_backup
One-shot backup (don’t combine with schedule-created backups).
raff_vm
Compute resource the schedule is attached to.
CLI: raff backup schedule
Imperative equivalent.