One of the main focus of this year for me as a cloud architect at Veeam, is to learn as much as possible about public cloud technologies, and how our software solutions can interact with them. I started a few weeks ago to deep dive into our solutions for Amazon Web Services, using N2WS Backup & Recovery. One of the things I’ve learned is how to create a dedicated account to protect other accounts.
A couple of weeks ago I presented to a customer Veeam's integration with AWS services, specifically the Direct Restore to EC2 feature. He was really interested, but he also immediately thought about possible large scenarios of this feature. This solution is not a Disaster Recovery technology, since a machine is not replicated into EC2, ready to be powered on, but it's rather a backup that is uploaded and then imported into EC2. But still, massive migrations or the creation of dev/test environments from a production copy were really nice use cases.
In the previous two posts of this series, I explained how to complete a seeding operation for a backup copy job in Veeam Cloud Connect, both for regular and encrypted backups. But Veeam Cloud Connect can also offer replication solutions to end users, so in this post I will explain you how to seed a replica job towards Cloud Connect.
In my previous post, I explained how to complete a seeding operation for a backup copy job in Veeam Cloud Connect. One of the options that can be leveraged with Cloud Connect however is also encryption: people may trust their service providers, but as they are going to send copies of their production workloads off-site, […]
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.
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.
In 2012 I published a post with a Powershell script to be able to check all the available VM’s in a given vSphere environment, and verify which ones were protected by Veeam Backup & Replication. Time to update the script to make it work with the latest versions of the two software.
Is it better to use real public IP’s or NAT-ed IP’s when publishing Veeam Cloud Connect Replication? Here’s why I think real public IP’s are a better choice.