Backing up data

R-Cloud enables you to back up your Gitlab data securely and efficiently.

Configuring the SaaS application for backup operations

R-Cloud starts protecting your GitLab data after you complete the following tasks:

  1. Create a personal access token for the GitLab application. When selecting the desired scopes, select the following:

    • api

    • read_api

    • read_user

    • read_repository

    • write_repository

    Important  The personal access token must be linked to a group and generated by using either the maintainer role, the owner role, or a custom role. The custom role must be granted the necessary permissions for the supported objects. For details, see GitLab documentation about permissions and roles.

  2. Add the module as a source to R-Cloud. For instructions, see Adding the module to R-Cloud.

    Note  When adding the module as a source, provide the GitLab group ID and the personal (bearer) token generated in the previous step.

  3. Assign a policy to the related SaaS application. For instructions, see Defining your backup strategy.

After adding the module, all the repositories in the specified group, as well as their issues, comments, releases, and pull requests will be automatically detected.

The supported objects are:

  • Repository sources:

    • Refs

    • Branches

    • Commits

    • Tags

    • Objects

    • Log

    • LFS files

  • Commit comments and discussions:

    • Comment/discussion (text, creator, creation date)

    • Discussion notes (text, creator, creation date)

  • Labels:

    • Name

    • Description

    • Color

  • Milestones:

    • Status

    • Name

    • Description

    • Due date

    • Start date

  • Wikis:

    • Wiki pages

    • Commits

    • Logs

  • Snippets:

    • Name

    • Description

    • Files

    • Metadata

    • Comment/discussion (text, creator, creation date)

    • Discussion notes (text, creator, creation date)

  • Issues/Test cases/Requirements/Incidents/Tasks/Merge Requests:

    • Title

    • Description

    • Metadata (creation date, creator, status, assignee, assigned labels, assigned milestones)

    • Comment/discussion (text, creator, creation date)

    • Discussion notes (text, creator, creation date)

  • Releases:

    • Tag name

    • Title

    • Metadata (assigned milestone)

    • Release date

    • Release notes

    • Releases assets (links only)

  • Feature flags:

    • Name

    • Description

    • Type

    • Environment

    • Strategies

  • Environments:

    • Name

    • URL

  • Deployment keys:

    • Key

    • Title

    • Metadata (expires at, can push)

  • Variables:

    • Type

    • Environment

    • Flags

    • Description

    • Key

    • Value

  • Issue boards:

    • Name

    • Label/milestone/assignee associations

Backing up SaaS application data

Limitation

Only backup data can be stored to the automatically created targets (and not copies of backup data or archive data).

To access the SaaS panel, in the navigation pane, click SaaS SaaS.

Procedure

  1. Select the SaaS applications and/or resources that you want to back up.

    Note  If you want to narrow down the list of displayed SaaS applications, use the filtering options as described in Filtering and sorting data.

  2. Click Set Policy Set Policy. The Set Policy dialog box opens.

  3. From the list of available policies, select the preferred policy.

  4. Click Assign to assign the policy to the selected SaaS applications and/or resources.

After you assign a policy to a SaaS application, a backup task starts immediately. Subsequent backups are scheduled according to the values defined in the policy.

If required, you can also perform a manual backup of individual SaaS applications and/or resources at any time. For details, see Performing manual backups.