1 -- if you want to just have only few tables and schema available to DR site on you can unload on S3 and load it to DR site Cluster when needed.
2 -- You can also run dual ETL to load data in primary and DR cluster for specific tables. For both option 1 & 2 You can use Redshift Serverless as a DR cluster, which will be auto paused when not being used and will be available in minutes when you need it.
3 -- AZ Failure - You may want to look into CROSS AZ Relocation feature of Redshift. This will have fail over cluster available with no data loss and will be available in minutes. https://docs.aws.amazon.com/redshift/latest/mgmt/managing-cluster-recovery.html
4 -- Region Failure - You can enable cross region snapshot to copy data in other region in a automated fashion and restore it to the DR cluster when required. https://aws.amazon.com/blogs/aws/automated-cross-region-snapshot-copy-for-amazon-redshift/
Relevant questions
Is CloudEndure(CE)/AWS Elastic Disaster Recovery(AWS EDRS) supported for disaster recovery of SAP on AWS?
Accepted Answerasked 2 months agoElastic disaster recovery - failed to failback
asked 3 months agoIs able Redshift to restore leader node upon fail as it would do with compute nodes?
Accepted Answerasked 7 years agoPoint in Time Recovery on Deleted Tables
Accepted Answerasked 4 years agoRedshift Disaster Recovery, attempting to restore tables to cluster in another account.
asked 16 days agoDisaster Recovery in Elasticseach
asked 5 months agoRestoring Redshift Schema (only schema no data)form Prod cluster to non-prod cluster
asked 6 months agoAWS elastic disaster recovery
asked 6 months agoDisaster Recovery in Elasticseach
asked 6 months agoUsing redshift-data boto3 to make cross account redshift calls
asked 7 months ago