Snapshot rotation and pinning: how many to keep

Scheduled backups only keep working while there's room for the next one. This is how RestoreCord makes that room, and how pinning keeps your most important copies out of harm's way.

Short answer

Each server has a snapshot limit: 1 on Free, 5 on Premium, 30 on Business and 50 on Enterprise. At the limit, a successful scheduled snapshot replaces the oldest unpinned one. Pinned and legacy snapshots are never deleted automatically.

Limits are counted per server

PlanSnapshots per serverMessages per channelAutomated
Free150No
Premium5200No
Business30500Yes
Enterprise502,000Yes

The count is per source server, not across your account, and older legacy snapshots tied to the same guild count toward it.

What rotation does

When a scheduled snapshot finishes successfully and the server is already at its limit, RestoreCord deletes the oldest unpinned current-format snapshot of that server. The newest copies stay and the stalest one steps aside. A failed run deletes nothing, so a bad night never costs you a good backup.

Two kinds of snapshot are never rotated:

  • Pinned snapshots, which you mark yourself
  • Legacy snapshots taken in an older format

Pin milestones, not everything

Pinning is for recovery points you know are good and would still want years from now:

  • The server right before a large role or permission redesign
  • Launch day, or the day a big event kicked off
  • The first clean snapshot after recovering from a raid or a nuke
  • The last state before handing the server to a new owner or team

Do the rolling-history math

Every pin removes a slot from rotation. Decide how much rolling history you want, then pin around it. On Business with weekly runs, pinning 4 leaves 26 rotating slots, about six months of weekly copies. On Enterprise with daily runs, pinning 10 leaves 40 rotating slots, a little over a month of daily history.

PlanSuggested schedulePinsRolling history
FreeManual, before big changesNot needed with 1 slotYour single latest snapshot
PremiumManual, weekly habit1 milestone4 recent manual copies
BusinessWeekly4 milestones26 weeks, about six months
EnterpriseDaily10 milestones40 days of daily copies

If every slot is pinned, nothing can rotate and the schedule has nowhere to put new copies. Keep at least as many unpinned slots as the rolling history you want.

Finding the right snapshot later

The Snapshots page is built for the moment you need one specific copy under pressure:

  • Search by name, description, server or snapshot ID.
  • Group by time or by server, or switch grouping off.
  • Sort by date, name or size.
  • Filter to pinned only to see just your milestones.
  • Rename or edit a description while you still remember why you took it.

Deleting by hand

You can remove snapshots you no longer need. Manual cleanup is also how you make room on Free and Premium, which have no scheduled rotation.

Setting up the schedule first? Start with scheduling automatic backups. Want proof the copies work? Try a practice restore, or head back to RestoreCord Snapshots.

A twice-a-year pinning review

Run through this list whenever your server changes shape, and the rotation keeps doing its job.

Count your rolling slots

Plan limit minus pins equals the history the schedule can keep. Write that number down.

Pin the last clean state

The first good snapshot after a raid, a nuke or a big rebuild deserves a pin.

Unpin old milestones yearly

A pin from three redesigns ago is a slot the schedule could be using.

Rename vague snapshots

Fix names like Backup 2 while you still remember what they protected.

Filter by Pinned only

Check the list of milestones regularly so it stays short and deliberate.

Delete by hand on Free and Premium

Without scheduled rotation, manual cleanup is how you free a slot for the next snapshot.

Rotation and pinning questions

History that rolls forward on its own

Let RestoreCord rotate your snapshots while the milestones you pinned stay exactly where you left them.