GitHub Migration F.A.Q.
Will I need to do anything for the migration?
No, the migration is planned in a way where you can sit back and relax while we do the heavy lifting. Your existing backup files will remain available and accessible under the same login. We will do the migration behind the scenes and once it’s ready, you will have access to the upgraded product upon your next login.
Will I lose any continuity with my backups?
No, the migration will be scheduled to occur after your nightly backups on BackHub. Once migrated, the system will kick off a set of new backups that overlaps with the previous night’s set of backups (so you will have two copies of the same day’s backup, one on each system). At that point, the system will stop performing daily backups on BackHub and it will be picked up on Rewind Backups for GitHub.
What will happen during the migration and can I access my backups?
During the migration, your login credentials will be flipped to the new system as the first backup on the new platform is happening. Since the initial backup will still be in progress, you will not be able to export those files or use them for restores.
If you require access to your previous backups while the migration is happening, please get in touch with our Support Team at help@rewind.com and we will be able to assist you.
How long will the migration and/or the first backup take?
It depends. Migrating the data so that a new backup can kick off on Rewind Backups for GitHub will be quick, but the length of the migration will depend on the size of your storage size or the number of repositories that your account has. The first backup always takes the longest and we anticipate that the majority of accounts will be migrated within hours and certain within a day, before the next nightly backup is scheduled to kick off. If any first backup is taking longer than expected or taking longer than a day, we will reach out and inform you ahead of time.
Should I be worried about the security of my data during the migration?
Not at all! The migration will only move key data that’ll allow us to kick off GitHub backups on the new platform, but none of your actual backup data will be moved. Your older backups will remain in the legacy BackHub system for approximately 30 days (or 365 days depending on your data retention period), at which time it will be removed. No backup data will be transitioned to the new Rewind Backups for GitHub platform. Backing up on the upgraded system includes AES-256 bit encryption for your data both in transit and at rest.
Will I still have access to my older backups and for how long?
Yes. When the migration is complete, a set of new backups will be started on the updated Rewind Backups for GitHub platform. Since these are daily backups, a new version of the backups will be created everyday. For the first 30 days (or 365 days depending on your data retention period), you will continue to have access to your BackHub account to access your previous backups and Download exports or Restore from there should you need to.
After roughly 30 days, you should have a library of 30 days of backups on Rewind Backups for GitHub and your backups on BackHub will be past their retention period (similar to 365-day retention). Once we’re past that point, we will remove access to BackHub.
Who will have access to the new account after the migration?
The current Admin of the BackHub account will continue to have the highest level of access (now called “Owner”) when migrated to the new platform. For the rest of the users, we are maintaining the same levels of access (now called “Admin”) so whoever has access to BackHub will continue to have the same level of access to Rewind Backups for GitHub once migrated.
If you would like to assign a different Owner, there is an option to transfer ownership of the Rewind Backups for GitHub account once it’s been migrated.
Note: Only the Owner has the ability to manage users and we recommend logging in to double check access once the account’s been migrated.
Click here to return to the Migration Hub.