S3 AWS Backup - Understanding scheduling & incremental & continuous backup

0

Hello Community !

Let's say I have a Continuos Backup for S3. It is scheduled on a daily basis with a retention of 35 days. In this way I would have two strategies. Every day I would be doing a scheduled incremental backup + the continuous backup with the changes made in the bucket until the next day.

In my mind, it should create a recovery point in my vault every day, and each of these recovery points would have a 24 hour restore point. However, even though the backup jobs are completed successfully. There are days when a new recovery point is not created, but I have a recovery point with a recovery window of 3 days for example. So I don't see consistency in this process.

I have another continuous backup for RDS. It is scheduled on a daily basis with a 35 day retention, but in this case I have a single recovery point, with a 35 day restore point window that keeps moving.

Any explanation for this behavior of the S3 backup ? How does the scheduling work ? If I don't specify any schedule, a default one is set.

According to "https://repost.aws/questions/QUgttdfR00Rx-CKkoIkny-vQ/effects-of-backup-frequency-for-continuous-backups"

The schedule defines:

  • Check the backup is running as it should be, and start it if it isn't;
  • Check for retention points that have expired and need to be deleted.

But then I should have only one recovery point in S3 as in RDS.

답변 없음

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인