Backups and Archives
Durable, low-cost storage for data you need to keep
Store backups and long-term archives with built-in geo-redundancy — no replication rules, no retrieval delays.
Backup and archive workloads need storage that is durable, affordable, and accessible when it counts. Traditional providers force you to choose between cost and retrieval speed: cheap archive tiers come with hours-long restore times, and cross-region redundancy requires manual replication setup.
Tigris stores every object redundantly across multiple geographic locations by default. Lifecycle rules automatically transition objects from Standard to Infrequent Access to Archive as they age, so you get the lowest storage cost without managing tiering manually. When you need to restore, data is available immediately — no rehydration wait.
Benefits
Automatic tiering with lifecycle rules
Define age-based rules to move objects between storage tiers automatically. A backup written today starts in Standard, transitions to Infrequent Access after 30 days, and moves to Archive after 90 — all without application changes.
tigris buckets lifecycle set my-backups \
--rule '{"prefix":"backups/","transitions":[{"days":30,"storage_class":"INFREQUENT_ACCESS"},{"days":90,"storage_class":"ARCHIVE"}]}'
Geo-redundant by default
Every object is stored across multiple regions automatically. You don't need to configure cross-region replication, manage replica buckets, or pay extra for redundancy. If a region goes down, your backups are still accessible from another location.
No retrieval delays
Unlike traditional archive storage where restoring data takes minutes to hours, objects in every Tigris storage tier are accessible immediately. When you need to restore from a backup, you can start reading data right away — there is no rehydration step.
Zero egress fees
Restoring backups from traditional cloud storage can be expensive — especially cross-region restores during an incident. Tigris charges nothing for data transfer out, so disaster recovery doesn't come with a surprise bill.
S3-compatible API
Use your existing backup tools — rclone, AWS CLI, restic, or any S3-compatible
client. Point them at t3.storage.dev with your Tigris credentials and your
existing backup scripts work without modification.
# Example: rclone sync to Tigris
rclone sync /var/backups tigris:my-backups/daily/
Common patterns
Database backups
Schedule automated database dumps to Tigris. Lifecycle rules handle tiering automatically, and object notifications can trigger verification jobs when a new backup lands.
# Dump and upload
pg_dump mydb | gzip | aws s3 cp - s3://my-backups/db/$(date +%F).sql.gz
# Verify latest backup exists
aws s3 ls s3://my-backups/db/ --recursive | tail -1
Application state snapshots
Use Tigris snapshots to capture the state of an entire bucket at a point in time. Snapshots are instant and zero-copy — no data is duplicated until it changes.
# Take a point-in-time snapshot
tigris snapshots take my-app-data --name pre-migration-2024-03
Compliance and audit logs
Store logs and audit trails that must be retained for regulatory compliance. Lifecycle rules move them to Archive tier for the lowest storage cost, while IAM policies ensure they remain immutable.