- Newest
- Most votes
- Most comments
Amazon S3 objects cannot be edited. Objects can be read (with GET), and updated versions written (with PUT). The whole object is always written, and there is no tracking of byte-level differences between objects or versions of object keys. Therefore, ongoing backups of a bucket will contain the complete data in all new objects PUT since the last backup. This is similar to your 'file-wise' analogy.
https://docs.aws.amazon.com/aws-backup/latest/devguide/s3-backups.html
For both backup types, the first backup is a full backup, while subsequent backups are incremental at object-level.
Hello.
S3's Continuous Backups are incremental backups, so I think they create backups of parts where changes occur.
For example, if a 1 GB object has a 1 KB change, subsequent backups will create a new 1 GB object in the backup vault.
https://docs.aws.amazon.com/aws-backup/latest/devguide/s3-backups.html
For both backup types, the first backup is a full backup, while subsequent backups are incremental at object-level.
Relevant content
- Accepted Answerasked a year ago
- asked a year ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
@Riku Many thanks for your reply. That means, in my words, that it is either file-wise or byte-wise. Assume the binary of the file is just slightly amended, could we then store just the small differences of the binary?
@rePost-User-3708451 Correct. We store the small difference. It will be assembled if you restore.
@Rodney Lester So that would mean, if our file is of size 1 GB, and we change one day 10 bytes, and another day some furhter 10 bytes, we would not store 3 GB, but only 1 GB + 20 bytes (disregarding some further storage that might be necessary). Is that correct? Furthermore, is there some documentation for it, such that I can have a look at it?
Documentation is here: https://docs.aws.amazon.com/aws-backup/latest/devguide/s3-backups.html