I think this might be a bug in writing to the backup metadata stored in backup container? I added the --deep
flag and then it reports it is restorable:
$ /usr/bin/fdbbackup describe [...] -d "<backupURL>" --deep
URL: <backupURL>
Restorable: true
Partitioned logs: false
Snapshot: startVersion=37340640061336 (2021/11/03.00:32:34+0000) endVersion=37341025172871 (2021/11/03.00:38:59+0000) totalBytes=247807760945 restorable=true expiredPct=0.00
SnapshotBytes: 247807760945
MinLogBeginVersion: 37340639699336 (2021/11/03.00:32:34+0000)
ContiguousLogEndVersion: 37341037222797 (2021/11/03.00:39:11+0000)
MaxLogEndVersion: 37341037222797 (2021/11/03.00:39:11+0000)
MinRestorableVersion: 37341025172871 (2021/11/03.00:38:59+0000)
MaxRestorableVersion: 37341037222796 (2021/11/03.00:39:11+0000)
(This is the same backup as above)
Then running the same describe without --deep
now reports restorable, so I’m guessing it was fixed in the stored FDB metadata by the deep scan.