Amazon Backup integration with Amazon Redshift - Amazon Redshift
ConsiderationsLimitationsUsing Amazon Backup with Amazon Redshift
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Amazon Backup integration with Amazon Redshift

Amazon Backup is a fully managed service that helps you centralize and automate data protection across Amazon services, in the cloud, and on premises.

Using Amazon Backup for Amazon Redshift, you can configure data protection policies and monitor activity for different Amazon Redshift resources in one place. You can also create and store snapshots on Amazon Redshift provisioned clusters and serverless namespaces. This lets you automate and consolidate backup tasks that you had to do separately before, without any manual processes.

Note

No-backup tables are not supported for RA3 and Serverless. A table marked as no-backup in RA3 and Serverless will be treated as a permanent table that will always be backed up while taking a snapshot, and restored when restoring from a snapshot.

A backup, or recovery point, represents the content of a resource, such as an Amazon Redshift cluster, at a specified time. Amazon Backup saves backups in backup vaults, which you can organize according to your business needs. The terms recovery point and backup are used interchangeably. For more information about Amazon Backup, see Backup creation, maintenance, and restore in the Amazon Backup Developer Guide.

Amazon Redshift is natively integrated with Amazon Backup. That lets you define your backup plans and assign Amazon Redshift resources to the backup plans. Amazon Backup automates the creation of Amazon Redshift manual snapshots, and securely stores these snapshots in a backup vault that you designate in your backup plan. For information about vaults, see Backup vaults in the Amazon Backup Developer Guide. In the backup plan, you can define the backup frequency, backup window, lifecycle, or backup vault. For information about backup plans, see Backup plans in the Amazon Backup Developer Guide.

For information about creating and restoring Amazon Redshift Serverless snapshots without using Amazon Backup, see Snapshots and recovery points. For information about creating and restoring Amazon Redshift provisioned cluster snapshots without using Amazon Backup see Amazon Redshift snapshots and backups.

Considerations for using Amazon Backup with Amazon Redshift

Following are considerations for using Amazon Backup with Amazon Redshift:

  • Amazon Backup for Amazon Redshift is available where both Amazon Backup and Amazon Redshift are available in the same Amazon Web Services Regions. For information on where Amazon Backup is available, see Amazon Redshift endpoints and quotas in Amazon Web Services General Reference.

  • To get started using Amazon Backup, verify that you have met all the prerequisites. For more information, see Prerequisites in the Amazon Backup Developer Guide.

  • Affirmatively opt in to Amazon Backup service. Opt-in choices apply to the specific account and Amazon Web Services Region. If you want to use backups in multiple Regions with a given account, you must opt in to each individual Region with that account. For more information, see Opt in to managing services with Amazon Backup in the Amazon Backup Developer Guide.

  • Amazon Backup integration for Amazon Redshift only supports manual snapshots for provisioned clusters and serverless namespaces.

  • Once you use Amazon Backup to manage snapshot settings, you can't continue to manage manual snapshot settings using Amazon Redshift. Instead, you can continue to manage the settings using an Amazon Backup plan. For more information, see Backup plans in the Amazon Backup Developer Guide.

  • Restoring whole data warehouse snapshots to a serverless namespace is a destructive change. All previously existing data in the target namespace is lost when you restore a data warehouse snapshot to that namespace. This only applies to restoring data warehouse snapshots. Restoring single table snapshots to a namespace doesn’t delete existing data.

  • To restore a snapshot to a provisioned cluster, you need to have an IAM policy with the RestoreFromClusterSnapshot permission. To restore a snapshot to a serverless namespace, you need to have an IAM policy with the RestoreFromSnapshot permission. These permissions apply to the target data warehouse type, not to source snapshot type. For example, to restore a cluster snapshot to a namespace, you would need the RestoreFromSnapshot permission, not RestoreFromClusterSnapshot. For more information on managing IAM policies, see Identity and access management in Amazon Redshift.

Limitations for using Amazon Backup with Amazon Redshift

Following are limitations for using Amazon Backup with Amazon Redshift:

  • You can't use Amazon Backup to manage Amazon Redshift automated snapshots. To manage automated snapshots, use tags. For information about tagging resources, see Tagging resources in Amazon Redshift.

  • When restoring single tables from a snapshot, you can’t restore from a provisioned cluster snapshot to a serverless namespace or vice versa. You can restore entire snapshots in any configuration. For example, you can restore all of the databases in a provisioned cluster snapshot to a serverless namespace, but you can’t restore a single table from that same snapshot to the same namespace.

Managing Amazon Backup with Amazon Redshift

To protect resources on your Amazon Redshift data warehouses, you can use the Amazon Backup console, or programmatically use the Amazon Backup API or Amazon Command Line Interface (Amazon CLI). When you need to recover a resource, you can use either the Amazon Backup console or the Amazon CLI to find and recover the resource you need. For more information, see Amazon Command Line Interface.

When using Amazon Backup for Amazon Redshift, you can perform the following actions:

  • Create periodic backups that automatically initiate Amazon Redshift snapshots. Periodic backups are useful to meet your long-term data retention needs. For more information, see Amazon Redshift backups in the Amazon Backup Developer Guide.

  • Automate backup scheduling and retention by centrally configuring backup plans.

  • Restore a provisioned cluster or serverless namespace to the saved backup you choose. You can choose to restore all of the data in the snapshot or a single table from it. You set how often to back up your resources. For information about restoring provisioned cluster snapshots, see Restore an Amazon Redshift cluster in the Amazon Backup Developer Guide. For information on restoring serverless namespace snapshots, see Amazon Redshift Serverless restore in the Amazon Backup Developer Guide.