02/06/2017 |

Configuring Cloudberry Backup with OpenIO SDS

iStock_000013893478Small.jpg

I'm no longer a sysadmin (not for a long time), but sometimes I have to prove to myself that I'm still capable of doing something, and I also need to check that what I'm telling others is actually true. (You know, everything about the flexibility and ease of use of a complete SDS cluster, and the fact that it can be deployed in minutes).
 
I recently tried to configure several products at home in order to check compatibility with them and look at various configuration processes.

CloudBerry Backup

CloudBerry Lab has some very nice products, one of which is CloudBerry Backup. It exists in several forms, from a simple and straightforward free version to a complete solution for managed backups designed for service providers.
 
Today I am going to install the product and connect it to an SDS instance.

Prerequisites

First of all, the prerequisites. I'm doing this on a Windows PC, and, just to simplify things, I'll use a Docker container to deploy OpenIO SDS (I also tested it on my Raspberry Pi and it works in the same way).
 
The OpenIO SDS container is available on Docker Hub, and the procedure to have it up and running is very simple.

The first prerequisite is to have Docker on your PC. If you don't have it, you can download and install the package from here. Once the package is installed, Docker launches automatically.
 
For this example, and to keep things simple, I'll use the Swift protocol and TempAuth authentication system with the default credentials that are preset in the standard installation: demo:demo user and PASS_DEMO password.

OpenIO SDS installation

Open a Powershell CLI (you'll find it in the menu that appears by right-clicking the Start menu).
 
At the prompt, type:
 
$docker pull openio/sds
 
Followed by
 
$docker run -ti --tty -p 192.168.1.121:6007:6007 --net=host openio/sds

These commands download the container image, if it is not available on the system, and launch it with specific options. The container is not usually visible to the rest of the world, but Docker provides a NAT service, which is why we use the –p option. It maps TCP port 6007, accessible only on a private network, to the same port in the external world. The IP address is the IP of my default interface (my_ip:int_port:ext_port).
 
At this point, OpenIO SDS is up and running, and the Swift service is available on port 6007 of the local network from your PC. Remember to configure your Windows Firewall to make it accessible from other devices on your network.

Configure the client

You can download Cloudberry Backup directly from CloudBerry Lab's website; here’s the link. The installation process is straightforward, and a wizard walks you through the necessary steps.
 
Once it is installed, we have to configure access to the object store. To do this, you can select "Add New Account" from the first menu on the left.

A new window will appear:

Select the OpenStack Icon and fill in the fields in the dialog box as follows:

Please note that you have to select a container or create a new one; otherwise it won’t work.
Click OK, and voilà! The system is ready to rock and roll!
Click the File menu and you'll be prompted with the Create Backup Plan wizard.

A few more steps and we’re done:

Select the account you created earlier, and then click Next.
Give the plan a name, select what you want to back up, how, when, etc., and, in the last window, check Run Backup Now.

As soon as you click Finish, the backup will start.

Final note

Configuring a client to use OpenIO SDS is very easy, especially with nice tools like CloudBerry Backup.
I'm trying out other configurations, and I'll publish some of them to help end users who are adopting OpenIO SDS.
 
I hope you found this useful. Please let me know if you have other clients/protocols to test. You can also contribute with similar step-by-step guides on our forum too.

Join the OpenIO community!

OpenIO SDS is available for testing in four different flavors: Linux packages, the Docker image, and Raspberry Pi.

Stay in touch with us and our community through Twitter, our Slack community channel, GitHub, blog RSS feed and our web forum, to receive the latest info, support, and to chat with other users.