How to prepare a seed for S3 and Wasabi
1. In the Backup > Settings tab set the client to backup to a local vault only, which can be a USB drive or a UNC path.
2. Start the backup
3. Wait for the backup to finish.
4. On the backup client, go to the Backup > Schedule page and set the "Postpone Backups Until" date to about a month in the future. This is so the backup client does not try to backup while the seed is getting transported.
5. Go into the backup client's install folder, make a copy of 'vault0000.db', and rename the copy to the new name of 'vault0101.db'.
Caution: This step needs to be done prior to re-enabling the backup client. The backup software uses the 'vault0000.db' to keep track of the data in the local vault, while the 'vault0101.db' keeps track of the data in the remote vault. Without this copy/paste, the backup client will not know the data has been seeded to the remote vault.
6. Copy the folder that was chosen in step 1 onto the storage device provided by Amazon or Wasabi. It will have a number of subfolders (including vault, meta, settings, logs).
With the data uploaded to the storage device, follow the device's return policy, and allow time for it to be shipped and imported into your AWS or Wasabi bucket. Once the data is uploaded, you should ensure it is in the proper bucket and folder path.
Within the root storage, the correct place for the backup account folder is in the 'wsbu-brand\brand\acct_name\', which will contain the vault, meta, settings, and log folders. If the import of the data was put in its own bucket, you will need to move the data so the "acct_name" folders line up between the two data locations.
Caution: When you re-enable remote backups on clients, do not enable rigorous sync on the client until their local seed has been successfully copied to their remote vault. Enabling rigorous sync before all the data is in place will cause the client to try to regenerate and resend all the "missing" blocks.
You are done! The next time the computer backs up only the changes will be uploaded to the cloud storage!
Please see the following article for factors that affect performance and suggestions for optimizing: https://support.wholesalebackup.com/hc/en-us/articles/202092304
How to seed to Amazon S3 with Snowball
First, you will need to request a Snowball drive from AWS, read about getting started with AWS snowball here: https://aws.amazon.com/snowball/getting-started/
Alternately, if you have a fast internet connection in your office, you can use an S3 API browsing application to transfer the data from one of your own computers up to S3.
How to seed to Wasabi Storage with Wasabi Ball
First, you will need to request a Wasabi Ball drive from Wasabi, read about getting started with Wasabi Ball here: https://wasabi.com/wasabi-ball/
Alternately, if you have a fast internet connection in your office, you can use an S3 API browsing application to transfer the data from one of your own computers up to Wasabi.