- 最新
- 最多得票
- 最多評論
Hi,
I found the similar inquiry, in summary,
"Recovery of the DB instance has started. Recovery time will vary with the amount of data to be recovered" usually is seen in case there is a reboot (usually unplanned but not limited to) of the instance and RDS automation automatically identifies and fixes it back for use. Fail-overs are triggered only in case the primary instance has issues. If the reader has an issue it would just reboot and be back online (after recovery) to serve workload again.
please refer more details on the below[1].
https://repost.aws/questions/QUWrOK7aiwSH-iVwgpwq4UFQ/does-recovery-of-db-instance-run-automatically
Also Maintenance Windows[2] will be able to control scheduled events but it won't cover all kinds of events so you need to be alert when some kind event occurs, using CloudWatch monitoring[3].
[2] https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Maintenance.html
[3] https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/AlarmThatSendsEmail.html
相關內容
- 已提問 7 個月前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
Hi, As per the reference document [2] given, We have setup the time in maintenance window which is not a working hours of data processing in RDS,
But in our DB Instance the event - "Recovery of the DB Instance has started" was occur in out side of the maintenance window which was our working hour of data processing.
Also in the reference document [2] there is not mentioned the event for "Recovery of the DB Instance".
So we need to know the reasons for the event occurrence and exact which event was occur?
[2] https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Maintenance.html