Resources to Backup
...
- System database (hosted in RDS database, or in case of Derby EFS disk storage)
- Disk-based Aggregation data (Stored on EFS storage)
- Database based Aggregation data (Stored in Redis storage, like MemoryDB)
- Duplicate UDR detection (Stored on EFS disk storage)
...
General Requirements
Regardless of the method chosen for the provisioning of backup and restore operations, there are requirements that must be met:
...
Schedule – When the backup occurs. Make sure to align this with you cold backup window defined in previous step!
Backup window – The window of time in which the backup needs to start. Make sure to align this with you cold backup window defined in previous step!
Lifecycle – When to move a recovery point to cold storage and when to delete it
Backup vault – Used to organize recovery points created by the Backup rule.
- Backups should be taken as snapshot backups. I.e do not enable "continuous backups for point-in-time recovery (PITR)" as that can lead to unpredictable behaviour.
If AWS Backup is not available as a service in your region, the recommendation is to use EFS to EFS backup, see https://aws.amazon.com/solutions/implementations/efs-to-efs-backup-solution/.
...
To protect against availability zone failures, a production setup should always be setup with a Standby Instance. This is already the case in the provided Terraform template configuration (multi_az = true).
To protect against the unlikely case of region failure, cross region backup can be configured using AWS Backup. See https://aws.amazon.com/getting-started/hands-on/amazon-rds-backup-restore-using-aws-backup/. If AWS Backup is not available as a service in your region, you can instead rely on RDS built in backup mechanism and manually configure the backup in S3 to be replicated to other region.
...
To protect against multi availability-zone failures (unlikely) or human errors (more likely) snapshot backups to different region can be enabled. This is described in https://docs.aws.amazon.com/memorydb/latest/devguide/snapshots-automatic.html. Follow these instructions to configure:
- Snapshot window - A period during each day when MemoryDB begins creating a snapshot. The minimum length for the snapshot window is 60 minutes. Although not required for consistency, it is recommended to align this with your cold backup window (if enabled) as configured in step 1.
- Snapshot retention limit – The number of days the snapshot is retained in Amazon S3.
5. Kubernetes Managed Resources
...
It is recommended to install all Kubernetes managed resources as Helm charts managed by automated CI/CD pipelines. The process to setup such a pipeline is described in Installation Procedure for CI Pipeline(4.3.0)
If Kubernetes resources are managed by CI/CD, there is no need to backup the deployed resources in the EKS cluster. If for some reason CI/CD is not set up, Kubernetes resources should be backed up to be recoverable if disaster happens. To backup Kubernetes managed resources in EKS, the recommended tool to use is Velero. See documentation on https://velero.io/ for information on how to set this up.
...
Pricing of backup data is based on volumes and are defined at https://aws.amazon.com/backup/pricing/ and https://docs.aws.amazon.com/memorydb/latest/devguide/snapshots-costs.html.At the time of writing RDS backup cost $0.05 per GB-Month and EFS cost $0.095 per GB-Month, both prices being for Warm Storage. MemoryDB snapshots is free for one snapshot backup. Storage space for additional snapshots is charged at a rate of $0.085/GB per month for all AWS Regions (at the time of writing 2021-09-30).