Since we released Veeam Backup for Google Cloud Platform (can we call it VB4GCP from now on, do you mind?) a few weeks ago, many users have immediately started to use it. The use case of a single user protecting his resources is very easy to understand and configure, but today I’ve been asked by one of our service providers how could we configure the software to protect different customers from the same installation. Let’s test this in the lab!
One of the most common question I receive in regard to Veeam Cloud Connect, is “What’s the size I should configure for my Veeam server”? Usually, we answered this question using our sizing tools and our best practices, but lately I found a different and probably even better answer, thanks to our big data.
Last year, together with the release of the new Veeam Cloud Connect, I wrote and published its Reference Architecture. The paper had a great success with 1500 people downloading it. Because of the new additions in Veeam Backup & Replication v8 Update 2, it was time to upgrade the document.
Since I started to write my first articles about VMware vCloud Hybrid Service, I received some emails from people asking me if those articles where well suited with my daily job. For those who do not know, I work in Switzerland in a vCloud Service Provider, so maybe these two…