Feature Request: Backup Rotation per Schedule

[RobinBr26]

Feature Request: Backup Rotation per Schedule

Problem

Currently, the backup limit in Pterodactyl is global per server.
All schedules share the same backup pool.

When the limit is reached, the oldest backups are removed, regardless of which schedule created them.

In practice, frequent backups (for example hourly ones) quickly push out daily or weekly backups.

---

Real-World Gaming Use Case

For a typical Minecraft or game server, a realistic setup would be:

• Hourly backups retained for 12-20 hours
• Daily backups retained for 7 days
• Weekly backups retained for 3–4 weeks

This allows:

• Fast rollback for recent griefing or mistakes
• A daily fallback if issues are discovered later
• A weekly fallback for larger or unnoticed problems

With the current global-only limit, this tiered retention model cannot be reliably achieved.

---

Possible Solutions

Option 1 (Simpler)

When the limit is reached, a schedule should rotate only its own backups.

Meaning:

• Hourly backups overwrite older hourly backups
• Daily backups overwrite older daily backups
• Weekly backups overwrite older weekly backups

This keeps the system simple while solving the core issue.

Option 2

Allow defining a retention limit per schedule (for example “retain 10 backups for this schedule”).

This would provide more flexibility, though it may require additional structural changes.

---

Contribution

I would be happy to implement this feature myself and open a Pull Request.

I understand that PRs require maintainer approval beforehand, so I am opening this discussion first to confirm that this direction would be accepted.

Thank you for your time.