AWS - 回溯 Aurora 数据库
AWS - Backtracking an Aurora DB
根据这个link:
The actual backtrack window is the actual amount of time you can
backtrack your DB cluster, which can be smaller than the target
backtrack window. The actual backtrack window is based on your workload and the storage available for storing information about database changes, called change records.
为了对上面的陈述进行建模，我制作了这张图：
actual backtrack怎么会比target backtrack小呢？我觉得actual backtrack应该大于target backtrack，这样才能有足够的change records回溯？
在我的图形中，如果我想回溯到 24 小时前，它在 actual backtrack window 之外，所以它不包含 change record 怎么办？
这是文档中的拼写错误吗？如果我错了请解释。
谢谢，
目标 是 Aurora 尝试 始终可用的目标。 实际可用的历史记录量必然相同或更少。
You can think of your target backtrack window as the goal for the maximum amount of time you want to be able to backtrack your DB cluster. In most cases, you can backtrack the maximum amount of time that you specified. However, in some cases, the DB cluster can't store enough change records to backtrack the maximum amount of time, and your actual backtrack window is smaller than your target. Typically, the actual backtrack window is smaller than the target when you have extremely heavy workload on your DB cluster. When your actual backtrack window is smaller than your target, we send you a notification.
https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Managing.Backtrack.html
根据这个link:
The actual backtrack window is the actual amount of time you can backtrack your DB cluster, which can be smaller than the target backtrack window. The actual backtrack window is based on your workload and the storage available for storing information about database changes, called change records.
为了对上面的陈述进行建模，我制作了这张图：
actual backtrack怎么会比target backtrack小呢？我觉得actual backtrack应该大于target backtrack，这样才能有足够的change records回溯？
在我的图形中，如果我想回溯到 24 小时前，它在 actual backtrack window 之外，所以它不包含 change record 怎么办？
这是文档中的拼写错误吗？如果我错了请解释。
谢谢，
目标 是 Aurora 尝试 始终可用的目标。 实际可用的历史记录量必然相同或更少。
You can think of your target backtrack window as the goal for the maximum amount of time you want to be able to backtrack your DB cluster. In most cases, you can backtrack the maximum amount of time that you specified. However, in some cases, the DB cluster can't store enough change records to backtrack the maximum amount of time, and your actual backtrack window is smaller than your target. Typically, the actual backtrack window is smaller than the target when you have extremely heavy workload on your DB cluster. When your actual backtrack window is smaller than your target, we send you a notification.
https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Managing.Backtrack.html