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.
I’m working on some heavy lab tests in these weeks, plus I’m travelling a bit more than usual, so my blogging activity has slowed down a bit. As I’m catching up on the news I read around, I found two different articles that can give to all of us a good perception about two things about the public cloud, or the so called “hyper-scalers”. They have insanely massive resources, but as insane as they are, they are not infinite.
Since Veeam Backup & Replication 9.5 became available and people are using the ReFS blockclone API, one of the most common questions has always been “how much space I’m saving? Is there any way to measure it”. Finally, there’s a way to answer to this question!
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!
Veeam Agents, both for Windows and for Linux, have the possibility to send backups to a Veeam Backup & Replication server. This is a great feature, but sometimes customers don’t even have anymore any virtualized workload to protect, so they find a hard time to justify the deployment of Veeam Backup & Replication to only protect physical workloads. There’s a solution to this however, and it doesn’t cost anything to users.
Last week, another outage of a large cloud provider hit the news, and the many companies using their services were impacted. This time it was Amazon Web Services, as their S3 service in the US-East region has been down for almost 4 hours, impacting so many other cloud services that are relying on this object storage technology. What impacted me, however, had been the reactions of other IT people around and the couch architects all over the world.
One year ago I built a complete and dedicated lab in order to permanently test and demonstrate Veeam Cloud Connect. The lab had been designed to operate as a production environment, and was also used for the Veeam Cloud Connect book I wrote. After a year, my SSL certificate was about to expire, so I […]
In my previous post of this small series, titled Security for your virtual machines: what is KMIP?, I talked about the new generation of the main hypervisors, VMware vSphere 6.5 and Microsoft Hyper-V 2016, and how they both introduced new encryption capabilities for virtual machines. I described the underlying technology used by VMware, KMIP; it’s not time to implement it in my lab and see how it interacts with data protection, specifically backups.