Are all your backups now listed on TKLBAM too? If so then all good.
In answer to your question, if an incremental backup is missing from the chain then that is very bad! The backup can not be restored unless all of the links in the chain (incremental backups) exist from the incremental backup you are trying to restore, all the way back to the preceeding full backup. That is why it is important that the chain isn't too long.
By default TKLBAM is set to monthly full backups (with no incrementals). I turn daily incrementals on, but set full backups to run every 2 weeks (see here). That way the chain is only ever 13 links long (13 incremental daily backups + 1 full backup = 14 days worth of backups). If you wanted hourly incrementals, personally I'd be looking at full backups every 12 hours. I'm not sure whether I'm being overly paranoid, but bottom line is that the shorter the chain the better IMO. I think it's also good practice to test your backups once every few full backs (so for my setup ideally I'd do it once every month or 2).
I'm not 100% sure what happened to the Hub (re not showing up all backups) but AFAIK the Hub is only displaying info, the important part is that TKLBAM itself is seeing all the incremental backups. Which from my understanding it did.
And yes Duplicity is controled by the local instance of TKLBAM (not the Hub). AFAIK, as long as your local TKLBAM knows what's going on, and the backups exist in your S3 container (assuming you are using the default TKLBAM storage option) then all will be well.
Others are reporting that all backups listed now
Are all your backups now listed on TKLBAM too? If so then all good.
In answer to your question, if an incremental backup is missing from the chain then that is very bad! The backup can not be restored unless all of the links in the chain (incremental backups) exist from the incremental backup you are trying to restore, all the way back to the preceeding full backup. That is why it is important that the chain isn't too long.
By default TKLBAM is set to monthly full backups (with no incrementals). I turn daily incrementals on, but set full backups to run every 2 weeks (see here). That way the chain is only ever 13 links long (13 incremental daily backups + 1 full backup = 14 days worth of backups). If you wanted hourly incrementals, personally I'd be looking at full backups every 12 hours. I'm not sure whether I'm being overly paranoid, but bottom line is that the shorter the chain the better IMO. I think it's also good practice to test your backups once every few full backs (so for my setup ideally I'd do it once every month or 2).
I'm not 100% sure what happened to the Hub (re not showing up all backups) but AFAIK the Hub is only displaying info, the important part is that TKLBAM itself is seeing all the incremental backups. Which from my understanding it did.
And yes Duplicity is controled by the local instance of TKLBAM (not the Hub). AFAIK, as long as your local TKLBAM knows what's going on, and the backups exist in your S3 container (assuming you are using the default TKLBAM storage option) then all will be well.