Use VeeamPN to access Cloud Connect tenants

Last week, during the VeeamON 2017 conference, one of the announcements has been a completely new product, called VeeamPN (Veeam Powered Network), a solution to easily create virtual private networks betweens multiple public clouds, remote locations and roaming users. Even if the main use case of the solution is to ease the access to Azure virtual machines, I’ve found another interesting use case that I’m sure the service providers running Veeam Cloud Connect will like.

Send Veeam Agent for Windows backups to both a local repository and to Cloud Connect

Veeam Agent for Windows 2.0 is today available as a public beta, and it’s soon to be officially released. One of the most awaited features is for sure the possibility to send backups over the Internet to Veeam Cloud Connect, and the feedback we’ve seen during the public beta period has been great so far. There’s actually however one limit in v2: users can only choose one destination for their backups. So, if you want to consume Cloud Connect, this is going to be your only traget and you will have no local backups, and viceversa. Two different policies cannot be configured in the interface, but this doesn’t mean it cannot be done!

Seeding Veeam Cloud Connect – Part 1: Backup copy jobs

Veeam Cloud Connect is a great technology that allows end users to add to a local protection also an offsite location where they can store backup copies or replicated virtual machines. As not every customer has a fast internet connection, Veeam Cloud Connect implements multiple data reduction tecniques to improve data transfer, but especially the initial full backup or full replica can be slow and painful for some customers with really small internet connection. That’s why seeding is such an important option in Veeam Cloud Connect.
In this three series blog posts, you will learn how to use Veeam Cloud Connect. In Part 1, how to seed a regular backup copy job.

Load balancing services with AWS Route53 DNS health checks

DNS is a great technology that everyone uses over internet. How would you reach a given website if you weren’t able to solve its name to the IP address? Would you memorize the public IP addresses of any website you want to reach? No, and with IPv6 coming in the future, DNS will become even more important for internet consumption. But DNS has one drawback: its records are usually static, and if a platform is dynamic and spawn/removes instances on the fly, it needs to have a way to modify the DNS records that are published, so that a non-reachable instances is not even listed.