Bulk Restore to GitHub

Bulk Restore streamlines the process of restoring multiple GitHub repositories from backup in just a few clicks.

The Bulk Restore feature in Cloudback allows you to restore multiple repositories at once, making disaster recovery and migration faster and easier. This guide will walk you through the bulk restore process step by step.

Overview

Bulk Restore streamlines the process of restoring multiple GitHub repositories from backup in just a few clicks. The feature uses an easy, step-by-step wizard to guide you through the selection and restoration of backups. If you want to restore a single repository, you can use the Restore to GitHub feature instead.

When to Use Bulk Restore

  • Restoring several repositories after data loss or corruption

  • Migrating repositories to a new account or environment

  • Migrating repositories from several accounts to a single account

  • Testing recovery scenarios in staging or QA environments

How to Perform a Bulk Restore

Step 1: Select Repositories

  1. Go to the Dashboard in Cloudback.

  2. Use the checkboxes to select one or more repositories you want to restore.

  3. Click Trigger restore at the bottom of the screen.

Only repositories with existing backups will be available for restoration. The Trigger restore button shows the number of repositories available for bulk restore.

Trigger restore button

Step 2: Review Source Backups

By default, the latest backup snapshots for each selected repository will be used. You can change this if needed.

  1. In the "Bulk Restore" wizard, review the list of selected repositories and their available backup dates.

  2. Choose the desired backup snapshot for each repository.

  3. Click Next to continue.

Review selected backups

Step 3: Select Target Account

  1. Enter or confirm the target account name where the repositories will be restored.

  2. Click Start Restore to begin the bulk restore process.

The restore process requires read and write access to your GitHub data, but the Cloudback Application app has read-only access, following the principle of least privilege. We have released an additional application Cloudback Restore Application with read and write access to your data. This application should be installed for the restore process to work. You can uninstall the application after the restore is complete.

Select target account

Step 4: Restoration Progress

You will see a progress dashboard showing each repository’s restore status:

  • Succeeded – Restore completed successfully

  • In progress – Restore currently running

  • Queued – Restore is waiting to start

  • Failed – Restore encountered an error

Bulk restore progress

You can safely close the progress window at any time; the restore operations will continue in the background. Each restore is available for review in the Restores tab of the repository details page. For more details, see the Repository Details page.

Troubleshooting

  • Restore failed? Click on the failed repository in the progress list to view error details and recommended actions.

  • Not all repositories listed? Ensure you have the correct account selected and that backups exist for the desired repositories.

  • Need to restore to different accounts or paths? Currently, all selected repositories are restored to a single target account. For restoring to different accounts, you will need to perform separate bulk restores.

  • Want to restore a single repository? Use the Restore to GitHub feature for individual repository restores.

Learn More

Last updated

Was this helpful?