BACKUP SEAL 

BACKUP SEAL
Available since:
Redis Open Source 8.10.0
Time complexity:
O(1)
ACL categories:
@admin, @slow, @dangerous,
Compatibility:
Redis Software and Redis Cloud compatibility

Freezes the current backup, producing the final immutable file set: the BASE snapshot, the incremental append-only file (INCR), and a standalone manifest.

Examples 

127.0.0.1:6379> BACKUP SEAL
OK

Details

BACKUP SEAL moves the backup state machine from incrementing to sealed. Restore loads BASE + INCR, so the restored dataset reflects the state at the seal boundary, not merely the earlier BASE snapshot. Sealing performs the following steps:

  • Flushes and fsyncs the current INCR file.
  • Hard-links the INCR file into the backup directory.
  • Writes a standalone manifest that references only this backup's {BASE, INCR} file set.
  • Rotates the live AOF when AOF persistence is enabled.
  • Stops and removes the temporary AOF state when the backup created it for an appendonly no instance.

After sealing, the file set is complete and immutable. The data plane can copy the files reported by BACKUP LIST, then call BACKUP CLEANUP to release them.

For the full workflow and restore procedure, see Redis persistence.

Redis Software and Redis Cloud compatibility

Redis
Software		 Redis
Cloud		 Notes
❌ Standard
❌ Active-Active		 ❌ Standard
❌ Active-Active

Return information

See also

BACKUP START | BACKUP STATUS | BACKUP LIST | BACKUP ABORT | BACKUP CLEANUP

RATE THIS PAGE
Back to top ↑