This article covers how to create and update backup policies in Rewind, which let you apply custom backup frequency and data retention settings to specific groups of GitHub repositories.
Plan requirement: This feature is only available on GitHub Pro and Enterprise plans. If you have any questions please contact your account manager or help@rewind.com.
Before you begin
Before starting, confirm the following:
- Your plan includes support for backup policies. Contact your account manager or help@rewind.com if you're unsure.
- You are an Organization Administrator, Organization Owner, or Integration Administrator in Rewind.
- At least one successful backup of your entire GitHub instance has been completed. This is required before individual repositories can be selected and assigned to a policy, as it allows Rewind to detect all repositories in the instance.
Good to know
Repositories not assigned a policy will automatically use your organization default, or Rewind's default if no organization default has been set. Your organization default is configured during installation and applies to your entire instance. If you want to configure data retention for your entire instance, see Configurable data retention: Feature overview.
Repositories not assigned a policy will automatically use your organization default, or Rewind's default if no organization default has been set. Your organization default is configured during installation and applies to your entire instance. If you want to configure data retention for your entire instance, see Configurable data retention: Feature overview.
Create a backup policy
- After the first backup has completed, click on the GitHub instance you wish to configure, then click Manage backup configuration in the top right.
- You will see your current organization default or Rewind default policy, which applies to your entire instance. Click Create configuration to add a new policy.
- Enter a name that helps you and your team identify this policy and its settings (for example, Business Critical).
- Under Backup policy, select Custom to define a specific backup frequency and data retention for this policy. Select Default to apply your organization default settings instead.
- Click Next, and select the repositories you want to assign this policy to.
- Click Create to finish.
Update a backup policy
- Click on the GitHub instance you wish to update, then click Manage backup configuration in the top right.
- Click the pencil icon next to the policy you want to update.
- Make your changes, then click Save.
Note: Changes to a backup policy apply to future backups only and will not affect previous backups. For example, if you change data retention from 1 year to 3 years, only new backup versions will be retained for 3 years. Previously created versions will continue to follow the original 1-year retention.
Limitations
-
Initial backup must complete before policies can be assigned
Items captured in this initial backup will have a default retention of 1 year. Once backup policies are created, Rewind will run a new backup. All items will receive a new version with the updated policy applied. The original version retains 1-year storage retention, but new backups will follow the new policy going forward. -
Storage and data residency
Configuring different storage or data residency settings at the backup policy level is not currently supported. These settings apply at the instance level only.
Need help?
If you have questions or need assistance, contact help@rewind.com or submit a request.