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.

Increase the performance of your Veeam backups in network mode

If you ever tried to do any file operation via the management interface of an ESXi host, like uploading an ISO file or running a backup using Network Mode, you may know the management interface is not running at the full speed of the underlying network interface, and the bandwidth you end up using is only a percentage of the total available. This limit is designed to preserve the availability of the management interface, but still there are situations where this limit is a problem, and you would like to increase it. Hopefully, there’s a solution.