We’re big fans of the Unitrends Enterprise Backup (UEB) virtual appliance, and we’ve had a few people asking whether UEB works in Amazon Web Services (AWS). Up until now, our answer was always…we don’t know? So we thought we’d have a bit of fun and try moving a UEB protecting our vSphere environment into AWS. It’s exactly what Boomerang is perfect for – quickly getting your stuff into AWS without a fuss…
We’ve deployed our UEB in our vSphere environment:
Screen Shot 2015-03-25 at 2.50.36 pm
And we’re protecting the vSphere environment; we’ve taken a few backups to make sure we’ve got data in there.
Screen Shot 2015-03-25 at 3.47.56 pm
To start moving it to AWS, we just need to set the credentials in Boomerang and create a protection group that includes only the UEB virtual machine.
Screen Shot 2015-03-25 at 3.00.58 pm
Once our protection group is created, hit the “Replicate Now” button, and we’re away:
Screen Shot 2015-03-25 at 3.15.15 pm
Each time a replication is made, a snapshot is taken of the VM getting a frozen-point-in-time copy, and you’ll see this happening on the vCenter console.
Screen Shot 2015-03-25 at 3.03.24 pm
The initial replication of the VM is a full copy, making it the longest part of the operation. In this case where we’re just using default options, the provisioned storage is 210GB and this takes about 30 minutes to scan and upload the occupied storage into AWS. Once the initial copy is done, you can then run the replication again and just the changes will be sent, which is a good way to migrate machines with a minimum of downtime.
Screen Shot 2015-03-25 at 4.01.34 pm
Now that the replication is complete we can deploy into AWS, starting with a “Deploy Now.” This triggers an import of the VM, generation of an AMI of the VM, then finally a CloudFormation template that is used to deploy the VM into an AWS instance in the same network topology.
Screen Shot 2015-03-25 at 4.54.16 pm
The instance is now up and running, and I can attach a VPN to the VPC if I want. I’m going to take the easy way, and assign a public Elastic IP to the instance and access directly over the internet. The steps to get there are: Create Elastic IP; assign to Instance; then modify security groups to allow public traffic to the web interface. I’ve just allowed https through at this stage.
Screen Shot 2015-03-25 at 5.22.19 pm
And now the UEB is up and running in AWS, and to access it I just browse to the new address.
Screen Shot 2015-03-25 at 5.24.36 pm
While that was a bit of fun, let’s try getting a little deeper into this and set up the on-premise UEB to replicate into the AWS UEB. In this case I’d recommend that your DNS is well sorted and the access details to each UEB can be set with a fully qualified domain name. The security group in AWS also needs to be modified, as well the on-premise inbound firewall to support the traffic as listed here.
With that done, it’s just a matter of walking through the replication wizard, and assigning the AWS UEB as a Vault (or replication target). It all works amazingly well.
Screen Shot 2015-03-25 at 6.04.47 pm
Here’s how long you can expect this all to take:
  • Initial Configuration in Boomerang – 1 minute (as a caveat, I’m pretty good at this now)
  • Replication time with Boomerang into AWS – 45 mins
  • Clicking “Deploy” – 30 seconds
  • Spin up time in AWS – 30 minutes
  • Tweaking local firewalls configuration and AWS network configurations – 45 mins
  • Total time spent 2.5 hours (actual work time of 46.5 minutes)
Normally this kind of thing would take days of false starts. Think of all the time you can save!