You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a table where I have backed up and pushed to s3 using the diff-from flag. As a test I deleted the 'first' few backups and tried to restore from what was left.
Maybe this isn't a valid use case, but either way clickhouse-backup (v0.6.4) should not loop like this. At a minimum it should report an error and exit.
My preferred behaviour is that it would just download the parts it can (reporting that the chain of backups is broken). This would mean that I can keep doing partial backups, no need for full backup at any point. I can then roll the older backups away on s3 when needed.
The text was updated successfully, but these errors were encountered:
I have a table where I have backed up and pushed to s3 using the diff-from flag. As a test I deleted the 'first' few backups and tried to restore from what was left.
The restore gets stuck in an endless loop.
Maybe this isn't a valid use case, but either way clickhouse-backup (v0.6.4) should not loop like this. At a minimum it should report an error and exit.
My preferred behaviour is that it would just download the parts it can (reporting that the chain of backups is broken). This would mean that I can keep doing partial backups, no need for full backup at any point. I can then roll the older backups away on s3 when needed.
The text was updated successfully, but these errors were encountered: