Seeding Data


While MSP360 (CloudBerry) Backup is great for day-to-day backups, the initial full backup may be too time-consuming depending on the amount of data and available bandwidth. For example, backing up terabytes of data might be a non-starter for users with capped or slow bandwidth. It would be quicker and possibly cheaper to use a faster computer or data transport service like AWS Snowball Edge or Azure Import to perform the initial backup of your data. And when the data is successfully uploaded to the cloud, all subsequent differential backups would take place on the original computer, as they wouldn't be too sizeable.

MSP360 (CloudBerry) Backup is capable of performing such operation; although, some behind-the-scenes actions need to be taken due to the structure of backup data. If done properly, the initial backup will be performed on the fast PC and the slow PC will subsequently pick up the following backups.

The external storage referred to in this article may be a regular SSD or data transport solution like AWS Snowball Edge. Similarly, the fast PC may represent literally another computer with a faster connection or it could be the aforementioned services like AWS Snowball Edge or Azure Import.

In any case, seeding data involves the following steps:

  1. Backing up data to an external storage device.
  2. Transferring data from the external storage device to the required cloud storage with a fast PC (or data transport service).
  3. Synchronizing the repository to match the local and the cloud data.

This section covers the following data seeding solutions: