When you create a Cloud Backup job, you can seed the data to the cloud destination if there is too much data to send across the internet in the first full backup. Seeding involves putting the data on a removable drive and sending it to your cloud provider so they can copy the data to your cloud container. Your backup job will then detect the data in the container the first time it runs, and only back up data that has changed.
When to seed
You should consider seeding if the time required to back up all the data on a Cloud Backup's first run would be too long and impact other processes. This will depend on the amount data you have selected and the performance of your connection. For example, if the backup will take more than a day, it may impact your network during business hours and prevent scheduled backups from running, so seeding would be a viable option.
Seeding with BackupAssist
BackupAssist has a Seeding Tool, which prepares the drive that you send to your cloud provider by copying to data to the drive in the correct format. The process from that point on is defined by your cloud provider.
This means there are two processes to follow:
Process 1 - follow the steps in the BackupAssist seeding guide.
Process 2 - follow the steps in your AWS, or Azure cloud provider's guide.