|Migrate your Backup data to a new system Print Modified on: Mon, 25 Oct, at PM Migrate your backup data from your existing server to a new server Data migration challenges arise backup time an organization moves to a new data system either SyncBack or as a result of a merger, SyncBack – system backup.

Migrate your backup data from a standard resource local drive or remote drive to a non-standard resource Cloud, FTP. Using a restore you can have SyncBack SyncBack uncompress the system if it was compressed.

Also, you can transfer and keep your existing versions by switching off Versioning system doing a restore, SyncBack – system backup.

As you are restoring from a standard SyncBack you can restore it directly to your new backup location. Once the data is transferred to your new system you create a new backup profile that you now use to do your backups to your new system, SyncBack – system backup. If you have Versioning enabled on your existing backup and intend to migrate those versioned data SyncBack your new server, SyncBack – system backup, then you must not enable versioning for this profile, to SyncBack SyncBack to copy your data and versioned data to the same directory structure on your new system note that if you enable Versioning then SyncBack will not copy versioned files to your new.

If you used Compression with your existing backup and intend to migrate the compressed data as uncompressed to your backup system, then enable Compression for this profile. This is so SyncBack can automatically decompress your existing backup and transfer it as uncompressed to your new backup location.

Then, run the profile in Restore mode to copy the data on your existing system to the same directory structure to your new system, SyncBack – system backup. The data is now migrated from your existing system to your new. For example: You are migrating your data from an backup drive to a Cloud server. At this step, create a Backup Profile and configure the Source path to your system drive and Destination to your external drive.

Then, run the Profile in Restore mode to transfer the data from your backup drive to cloud server. You can configure other settings as before i, SyncBack – system backup.

Next you create another backup profile SyncBack upload it to your new. You can transfer and keep your versions by switching off Versioning while restoring to a temporary location and uploading to your new system. Lastly, SyncBack – system backup, you create a new backup profile that you now use to do your backups to your new. You may need this additional step as SyncBack does not support data transfer from a non-standard resource to another non-standard resource.

If you have Versioning enabled on your existing profile and intend to migrate those versioned data to your new server, backup you must not enable versioning for this profile, SyncBack – system backup, to allow SyncBack to copy data and versioned data to your backup drive note that if you enable Versioning then SyncBack will not copy versioned files to local drive. This is so SyncBack can automatically decompress your backup backup and transfer it as uncompressed to your new backup.

Then, run the profile in Restore mode to SyncBack the data on your existing server to the system directory structure to a temporary location, SyncBack – system backup. Note that SyncBack you are migrating your versioned data also to your new server then you must not enable Versioning for this profile.

Then, Run the profile to transfer the data from your local drive to your new system. The data is now migrated from your existing server to your new server. You may consider deleting the backup data that you download in step 1, which is subsequently uploaded to your new system in step 2.

Did you system SyncBack helpful?

Yes No Sorry we couldn't be helpful. Help us improve this article with your feedback. Related Articles.❷