- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
backing-up state means the database is available but it is taking a snapshot. So maybe the promotion is already done and the database is available for use. The replicas normally do not have backups enabled and it is mandatory for primaries to have them, so once a replica gets promoted it starts taking a backup, and this operation can take time as the first backup needs to copy the entire disk snapshot. backing-up instances are usable but not modifiable in AWS console.
After the first snapshot, the rest of them are faster, like in your production database, because consecutive snapshots only copy the disk differences between snapshots.
I've found that sometimes enabling backups and taking a manual snapshot of the replica meant to be promoted before the promotion speeds up any automated backup created later, but YMMV.
Contenuto pertinente
AWS UFFICIALEAggiornata 3 anni fa- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 3 anni fa
Thanks a ton for the context and how you generally approach these things! I'll definitely give that a try on the next one as I have several to do. The job did end up completing, it just took about an hour or hour 20. Otherwise it was a fairly seamless process! I've definitely accepted your answer. Thanks again!