Thanks. I am assuming the images are in the same order as the folders. Let me know if that is not correct.
First thing, the restore problem you were seeing earlier is because the restore folder doesn’t exist. You should create it first for now. The next release of Dgraph should contain a fix to automatically try to create this folder.
Second, the first and second backups look correct but the third one is fairly small. This is correct based on the timestamps of the two backups (19567 vs 19572). However, if you made a lot of changes, the timestamps should have changed by way more than 5.
The problem then is that the backup might not be backing up the most recent version. I think I might have seen something like this before. I’ll look into this. Thankfully, this doesn’t seem to be related to AWS at all so I can do the testing on my own.
Just a couple more requests.
- How long after the last mutation did you run the third backup?
- What happens if you run another backup sometime after the last mutation (let’s say 10 min)? If that ends up backing up the rest of the data, backup should be usable right now as long as you run it periodically and often enough to ensure not a lot of data is missed from the backups due to this issue.
On my end I’ll look into why the backup timestamp seems to be delayed.