1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
2
Check on these main reasons and look at the article included as well.
Bear in mind that binary logs are your first way to recovery and without a correct DR policy it may be really difficult to go on with the process. Anyways here are the other culprits you could hack.
- Check if you've enabled binary logging—it helps track changes to your data.
- Look into your CloudTrail logs for any DELETE statements around the time of the disappearance.
- Keep an eye on CloudWatch metrics for signs of high usage, which could signal trouble
- Consider enabling enhanced monitoring for more detailed insights.
- Check for any long-running transactions using the InnoDB status
- Review your IAM policies to ensure only authorized users are making changes.
- For future prevention, think about enabling binary logging and taking frequent snapshots.
Contenus pertinents
- demandé il y a un an
- demandé il y a 2 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
- Pourquoi ai-je reçu une erreur en lecture seule après la défaillance d'un cluster DB Amazon Aurora ?AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a 2 ans