Skip to content

Deprecation of Legacy S3 Layout and old Index Format #4602

@MichaelEischer

Description

@MichaelEischer

Output of restic version

0.16.2

What should restic do differently? Which functionality do you think we should add?

Deprecate the following functionality in 0.17.0. The removal will happen 0.18.0. The deprecated features will be disabled by default, but use feature flags (#4601) to provide an escape hatch to temporarily reenable them.

  • Legacy S3 Layout: since restic 0.7.0 the S3 backend uses the unified layout. The migration code seems to have been broken between restic 0.8.0 and 0.14.0 when using a cache. As we didn't receive a corresponding issue report, there appears to be very little usage of the S3 legacy layout. Supporting both layouts adds significant code complexity, which does not seem to be justified by remaining usage. Old repositories must be migrated prior to deprecation using restic migrate s3_layout to remain accessible.
  • Old Index Format: the old format has only been used before restic 0.2.0, as such likely next to no repositories exist that still use this format. The repository index can be updated to the modern format using restic repair index (also possible using restic versions without support for the old index format).

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions