Restoring a snapshot
Restoring a snapshot to a serverless namespace replaces the current database with the database in the snapshot.
Restoring a snapshot to a serverless namespace is completed in two phases. The first phase completes in a few minutes, restores the data to your namespace, and makes it available for queries. The second phase of restoration is where your database is tuned, which can cause minor performance issues. This second phase can last from a few hours to several days, and in some cases, a couple of weeks. The amount of time depends on the size of the data, but performance progressively improves as the database gets tuned. At the end of this phase, your serverless namespace is fully tuned, and you can submit queries without performance issues.
Note
A table marked as no-backup in RA3 and Serverless is treated as a permanent table and will always be restored when you restore from a snapshot.
To restore a snapshot to a serverless namespace
-
On the Amazon Redshift Serverless console, choose Data backup.
-
Choose the snapshot to restore. You can only restore one snapshot at a time.
-
Choose Actions, Restore to serverless namespace.
-
Choose an available namespace to restore to. You can only restore to namespaces whose statuses are Available.
-
Choose Restore.
To restore a snapshot to a provisioned cluster
-
On the Amazon Redshift Serverless console, choose Data backup.
-
Choose a snapshot to restore.
-
Choose Action, Restore to provisioned cluster.
-
Enter a cluster identifier.
-
Choose a Node type. The number of nodes depends on the node type.
-
Follow the instructions on the page on the console page to enter the properties for Cluster configuration. See Creating a cluster for more information.
For more information about snapshots on provisioned clusters, see Amazon Redshift snapshots and backups.
