-
Notifications
You must be signed in to change notification settings - Fork 63
/
databases-rds-backup-multiAZ-readreplicas.txt
43 lines (34 loc) · 1.33 KB
/
databases-rds-backup-multiAZ-readreplicas.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
Automated Backups
- Allow you to recover database to any point in time within retention period (1-35 days)
- Take full, daily snapshot
- Store transaction logs
- Enabled by default
- Stored in S3, free equal to size of database
- Deleted when RDS instance is deleted
Snapshots
- Database snapshots are done manually (stored even after RDS instance is deleted)
Restoring Backups
- When using either restore option, restored version of database will be a new RDS instance with new DNS endpoint
Encryption
- Done using AWS Key Management Service (KMS)
- Encrypting existing RDS is not currently supported
Multi-AZ RDS
- Used for Disaster Recover (DR) only
- Availability
- SQL Server
- Oracle
- MySQL Server
- PostgreSQL
- MariaDB
Read Replicas
- Used for scaling, not DR
- Must have automatic backups turned on to deploy a Read Replicas
- You hcan have up to 5 Read Replicas of any database
- Allow you to have a read-only copy of your database
- Achieved using asynchronous replication
- Used for performance improvements, read-heavy database workloads
- Each read replica will have its own DNS end point
- You can have read replicas that have Multi-AZ
- You can create read replicas of Multi-AZ source databases
- Read Replicas can be promoted to be their own databases (breaks replication)
- You can have a read replica in another Region