“Backup Redshift” creates a point-in-time snapshot or exports tables to S3 so data can be restored or re-created later.
Backups let you recover from accidental deletes, failed deployments, or region-wide outages. Manual snapshots and UNLOAD
exports provide fine-grained restore points beyond Redshift’s automatic retention.
Run CREATE SNAPSHOT
in any database. The command stores a cluster-wide backup in Amazon S3 without interrupting queries.
UNLOAD
exports query results to compressed files in an S3 bucket you own. Grant iam_role
or aws_access_key_id
/secret_access_key
before running.
1.Choose bucket s3://acme-backups/redshift/
.
2. Add server-side encryption if needed.
3. Partition files with PARALLEL ON
to speed export on large tables.
Use the AWS Console or aws redshift restore-from-cluster-snapshot
CLI to spin up a new cluster.Point apps to the restored endpoint once data validates.
• Schedule nightly CREATE SNAPSHOT
via EventBridge.
• Export critical fact tables weekly with UNLOAD
.
• Tag snapshots by environment for lifecycle policies.
• Test restores quarterly.
Ignoring IAM roles: Always attach an IAM_ROLE
with S3 write access to avoid AccessDenied
errors.
Exporting without compression: Add GZIP
to cut storage costs and speed transfers.
• Can I automate snapshot deletion?
• How long do automatic snapshots last?
• Does UNLOAD
impact cluster performance?
.
Most snapshots finish in minutes because Redshift copies only changed blocks (block-level incremental). Very large clusters may take longer but remain online.
No. UNLOAD is fully concurrent; queries and writes continue, though heavy exports can consume I/O. Use off-peak windows for multi-terabyte tables.
Yes. Add ENCRYPTED
or specify KMS_KEY_ID
in the UNLOAD command, or rely on default S3 SSE-S3 encryption.