Overview

Backup Policies let you apply custom backup frequency and data retention settings to specific groups of Confluence spaces. Not all of your data needs the same level of protection. Some spaces may be more sensitive or business-critical than others.

In the Rewind app, each Backup Policy is a backup configuration. You'll find them under Manage backup configuration.

Spaces that haven't been assigned a policy automatically use your organization default, which is the setting for the whole instance. If no organization default was set during installation, they use Rewind's default. Rewind's default is a backup every 24 hours with one year of data retention. If you want to configure the default backup and retention settings for your entire instance, see Configurable data retention: Feature overview.

Before you begin

Before starting, confirm the following:

• Your plan includes support for Backup Policies. This feature is available on the Advanced and Enterprise plans for Rewind Backups for Confluence. 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 full backup of your entire Confluence instance has been completed. Rewind needs this backup to detect all the spaces in your instance before you can select them and assign them to a policy. Until the first full backup has finished, you won't be able to create a policy.

Create a backup policy

1. After the first full backup has completed, click the Confluence instance you want to configure, then click Manage backup configuration in the top right.
2. You'll see your current organization default or Rewind default policy, which applies to your entire instance. Click Create configuration to add a new policy.
3. Enter a name that helps you and your team identify this policy and its settings (for example, Business Critical).
4. Under Backup policy, select Custom to set a specific backup frequency and data retention for this policy. Select Default to apply your organization default settings instead.
5. Click Next, then select the spaces you want to assign to this policy. Each space is shown with its name and space key (for example, ENG).
6. Click Create to finish.

If Rewind is still running a backup when you open the space list, a banner tells you that some spaces may not be listed yet. Wait for the backup to finish, then come back to add them.

Update a backup policy

1. Click the Confluence instance you want to update, then click Manage backup configuration in the top right.
2. Click the pencil icon next to the policy you want to update.
3. Make your changes, such as the backup frequency, the data retention, or which spaces are included. Then click Save.

What a Backup Policy covers

A Backup Policy applies to everything Rewind backs up inside each space you assign to it, including:

• Pages, blog posts and folders, including their labels, properties and restrictions
• Attachments and their labels
• Comments, both footer and inline, including replies and comments on blog posts
• Space settings: space labels, permissions, role assignments, theme, and look and feel
• Space templates

Items that belong to your whole Confluence site follow your organization default instead. This includes global templates and the space roles defined for your site. They aren't inside any one space, so they're backed up on your organization default settings rather than a Backup Policy's settings.

For the full list of what Rewind backs up for Confluence, see What does Rewind backup for Confluence?

Giving someone access to just one Backup Configuration

You can give a person access to the spaces in one or more specific Backup Configurations, without giving them access to the rest of your Confluence backups. You do this with two roles from Rewind Access Fabric:

• Backup Config Admin
  For the Backup Configurations they're assigned to, they can view the backed-up data and restore individual items. They can't edit the configuration, which means they can't change its backup frequency, its data retention, or which spaces it includes, and they can't run a backup. Backups continue on the configuration's schedule. They can't see any other Backup Configuration, and they can't perform organization-wide actions such as managing users, billing, or integrations.
• Backup Config Viewer
  Read-only access to the Backup Configurations they're assigned to. They can view the configuration and its backed-up data. They can't restore data or make any changes.

Organization Owners, Organization Admins, and Integration Admins aren't limited by these roles. They can create and edit Backup Configurations and run backups as usual.

These roles are available for Confluence wherever Backup Policies are set up. Keep in mind:

• A user has one role. You can't give someone Backup Config Admin on one configuration and Backup Config Viewer on another.
• Restores are limited to individual items.
• These roles can't be assigned through single sign-on (SSO).

To assign these roles, and to see how they compare to Rewind's other roles, see Scope user access with Rewind Access Fabric.

Limitations

• Initial backup must complete before policies can be created
  Rewind needs one full backup of your Confluence instance before you can create a Backup Policy. Items backed up before you create a policy keep the retention that was in effect when they were backed up. New backups follow the policy from then on.
• Up to 10 Backup Policies per Confluence instance
  You can create up to 10 Backup Policies for each Confluence instance. Each policy can include as many spaces as you like. If you need more than 10, contact help@rewind.com.
• A space can belong to only one Backup Policy at a time
• Your organization's data retention is the maximum
  A Backup Policy can't keep data longer than the data retention set for your organization.
• Policies apply to whole spaces
  You can't apply a policy to individual pages or other items within a space. A Backup Policy also can't span more than one Confluence site.
• Confluence Cloud only
• Some older backup data may not appear in a Backup Configuration
  When you view a Backup Configuration, or if you have the Backup Config Admin or Backup Config Viewer role, some data from older backups may not be listed. For example, space logos and some items from older backups. If something you expect to see is missing, contact help@rewind.com and we'll help.
• Storage and data residency
  Configuring different storage or data residency settings at the backup policy level isn't currently supported. These settings apply at the instance level only.
• Custom backup hour
  If you have a custom backup hour set on your instance, it isn't compatible with Backup Policies and won't be kept when policies are configured.

Related articles

• Configurable data retention: Feature overview — An overview of how configurable data retention works at the instance level in Rewind.
• Scope user access with Rewind Access Fabric — How to give someone access to specific Backup Configurations with the Backup Config Admin and Backup Config Viewer roles.
• What does Rewind backup for Confluence? — The full list of Confluence items Rewind backs up.
• How to create and update Backup Policies for Jira — The same feature for Jira.

Need help?

If you have questions or need assistance, contact help@rewind.com or submit a request.