While CloudBerry backup handles rather large volumes of data effortlessly, some concerns still remain with regard to the feasibility of utilizing the available internet connection for such purposes. Naturally, dozens of terabytes (even less) of data would take forever to upload even with a swift bandwidth, let alone a subpar connection. Besides, many Internet providers impose data caps on their users which could clearly impede any attempt at uploading data of volumes upwards of a certain number of terabytes. Thus, it may seem more appropriate to inspect other solutions to this conundrum.
Thankfully, Amazon provides a very neat and convenient service to solve this problem. It’s called Amazon Snowball. It is essentially a gigantic box that is capable of storing up to 80 TB of data.
It works rather simply; in a nutshell, you request the box from Amazon, upload your data to it, ship the box back to Amazon, and then wait for them to upload it to your bucket at their data storage facility. It is a pretty straightforward process. Surely, there are some technicalities here and there, but overall it’s a piece of cake. Feel free to read this article to learn more about the Snowball.
Now that you get the idea behind Amazon Snowball, let’s talk about how CloudBerry Backup facilitates this process. While ordering and shipping the box back is performed by Amazon, the data transfer from your machine(s) onto the Snowball is conducted with the help of our backup product. Long story short, you set up a backup plan as usual, except that your destination is now the Snowball, not a cloud storage. Hereinafter we explain in detail the process of setting up such a plan and all the associated steps.
It’s critical that you use a suitable machine for data transportation. It should be able to meet high demands in terms of processing, memory, and networking. Read this to learn more about the workstation specifications.
Creating a job
Having gotten a better picture of how the process works, you may commence ordering the Snowball. Head over to Amazon Web Services (be sure to select your region). Here you can create a so-called import or export job.
Next step is to fill in your address and select the preferred shipping speed.
Now you need enter the job details. Namely, the job’s name, the necessary bucket, and the Snowball capacity. Once you’re finished, click Next.
Step 4 is setting the security parameters.
Proceed to tailor your notifications preferences.
Last but not least, is the review process. Carefully examine all the information on this page, and if it is accurate—click Create Job.
Having created the job, expect the box shortly. Once it arrives, you can commence backing up your data to the box.
Working with CloudBerry Backup and the Snowball
Here is a simple breakdown of the whole backup process:
- Plug the Snowball in. Connect the powered-off box to your computer. Turn it on. Optionally, set up a custom IP address.
- Create a backup plan in CloudBerry Backup. The process is virtually indistinguishable from the usual gig. Only this time you use the AWS Snowball to perform the initial backup.
- Download and launch the so-called S3 Adapter to enable CloudBerry Backup to communicate with the box (AWS Snowball has its own file management system).
- Wait for the backup to be completed and then ship the box back to Amazon. Once your data has been successfully transferred from the box into your AWS bucket, launch CloudBerry Backup and let it know that the data is in the cloud, so that it can pick up the backup process during the following backups.
That’s it. The process is remarkably straightforward and takes a few minutes to set up. Now let’s dive in deep into the matter and explore the procedure step-by-step.
Setting up the box
Connect the powered-off box to your computer. There are various ways of doing it, be sure to read this article to learn more about connecting the Snowball to your network. Turn it on, and you’ll see the following information on the box’s E-ink screen:
The Snowball automatically fetches the IP address. Click Network to see it displayed. However, network settings can be manually altered. Refer to the aforementioned article to enquire into it.
Creating a backup plan
Before creating the plan, open your cloud storage settings and ensure that you selected the exact same bucket you had indicated when creating a job over at Amazon.
Now proceed to create a new backup plan. Follow the common steps. Select the I’d like to use AWS Snowball feature to make initial backup checkbox when specifying the plan’s name.
Continue setting up the plan. Soon enough you’ll reach the AWS Snowball step that describes further procedures. Click on the link in step №2 to download Amazon S3 adapter.
Once downloaded, unzip it and launch the command line. Navigate to the folder that contains Amazon S3 adapter and execute the following command:
call snowball-adapter.bat -i <Snowball IP> -m <path to manifest.bin> -u <unlock code>
Ensure that you don't have any other services running on port 8080 (checkable with netstat).
Both the manifest file and the client unlock code can be found in your AWS Console:
If you’ve done everything correctly, you should see a message in the terminal akin to “Server up and running on port 8080”.
Do not close the command line! It should be running all throughout the process. Now go back to CloudBerry Backup and conclude setting up the backup plan. Upon finishing, run it and wait for it to complete.
Now that the data has been successfully transferred to the AWS Snowball, ship the box back to Amazon. When they notify you of your data having been moved to your bucket, go ahead and confirm it in CloudBerry Backup. Click on “Initial backup finished…”.
Select the Import Job Completed checkbox and click OK.
Lo and behold! Your files are now being renamed in the cloud. This process takes place because of certain peculiarities of CloudBerry Backup and the way our software works with file structures.
Afterward, there is nothing else to be done! Voila! Your initial backup has been successfully performed with the help of AWS Snowball. All future backups will be performed as usual from your PC into the cloud by means of CloudBerry Backup.
NB: Do NOT Sync Repository before the files are all renamed in the cloud. This may lead to unintended repercussions.