HA(On-Premise) VS AWS RDS for Oracle ( Multi-AZ)
[ Multi-AZ ]
1. Main Purpose is high avaiilability
2. Non-Aurora : Synchronous replication
3. Non-Aurora : automated backups are taken from standby
4. Always span at least two Availability Zones with a single region
AWS RDS For Oracle 전제
1) 5분마다 Transaction Log 백업
2) 하루 한번 Snapshot Backup ( 복구 가능 셋 )
Snapshot 은 OS + DB 에 대한 Disk Backup 이며, 수행 전, Begin Backup 수행, 완료 후, End Bakcup 수행됨
3) Default 7일 보관, 최장 35일 보관 가능, Maual 백업(Snapshot)은 영구 백업 가능
<< AWS 주요 발췌 >>
-. Currently, RMAN restore isn't supported for Amazon RDS for Oracle DB instances.
-. Standard Amazon RDS backups don't use RMAN and therefore don't create records in the control file.
-. Disabling automatic backups for a DB instance deletes all existing automated backups for the instance.
-. When automated backups are enabled, your RDS instance and database is taken offline and a backup is immediately created.
-. Retained automated backups don't contain information about parameters or option groups.
-. Unlike automated backups, manual snapshots aren't subject to the backup retention period.
Snapshots don't expire.
-. You can't restore from a DB snapshot to an existing DB instance; a new DB instance is created when you restore.
-. You can restore a DB instance and use a different storage type than the source DB snapshot.
-. After you copy a snapshot, the copy is a manual snapshot.
-. If you want to restore the functionality of the DB instance to that of the DB instance that the snapshot was
created from, you must modify the DB instance to use the security group
and parameter group used by the previous DB instance.
-. RDS uploads transaction logs for DB instances to Amazon S3 every 5 minutes.