Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

release-22.1: backupccl: Backup LATEST file is no longer overwritten #79553

Merged
merged 1 commit into from Apr 7, 2022

Commits on Apr 7, 2022

  1. backupccl: This change teaches backup to no longer overwrite or delet…

    …e the LATEST file,
    
    and instead write a new version side by side with the old ones. Other functions are
    taught to look for these new LATEST files. To make sure that older backup chains
    are not broken by this change,we still maintain an overwritten,
    non versioned LATEST file in the base directory if it is a mixed cluster. This
    logic can be removed in a post 22.1 release when we no longer write to the base directory.
    
    Release Justification: Low risk change to where files are written
    for a highly requested feature.
    
    Release note (enterprise): LATEST files are no longer overwritten and now versioned
    and written in the /metadata/latest directory for non mixed clusters.
    Darryl committed Apr 7, 2022
    Configuration menu
    Copy the full SHA
    9ac51e0 View commit details
    Browse the repository at this point in the history