More than two years ago, when we released Veeam Cloud Connect 9.0, I massively reworked my original paper on the topic, and the final result became a book available as a pdf. The book was also printed and I have some copies at home; not something to win any nobel price, but it's nice to see them there as remind me of the massive work it took. Then, the cloud was calling, and I decided it was time to make it more modern and after some re-editing and learning how markdown and github work, the book became an online resource that people can freely and easily read.
In chapter 3 of this blog series, I showed you how to connect a vCloud Director to Veeam Backup & Replication. Before Veeam Backup & Replication 9.5 Update 4, the main usage of vCloud Director was to make backups of vCloud VMs. But now with Update 4, we can use vCloud Director as a target for Cloud Connect replicas.
In the previous posts we completed the automatic configuration of the Veeam Cloud Connect environment. In this third post of this short series, we will add additional resources in order to offer replication services. In fact, all the Cloud Connect components are now successfully deployed, so Backup services can already be offered, but to offer also replication services we need to connect our environment to the virtualized platform. Historically, Veeam Cloud Connect supported VMware vSphere and Microsoft Hyper-V, but since the soon-to-come 9.5 Update 4 will also add support for VMware vCloud Director, we will see how to add both to the infrastructure.
If you have just deployed vCloud Director over NSX , it may happen that during the creation of a new VCD network, the operations fails with the error “Cannot deploy organization VDC network; Make sure vShield Manager infrastructure is properly configured and there are segment IDs available.” In this case, you need to change the configuration of the NSX transport zones from Multicast to either Hybrid or Unicast.
I got this request from a colleague, who was helping out a service provider with this scenario: vCloud Director is using an external LDAP service, coming from a local Microsoft Active Directory, to authenticate all vCD users. Is Veeam vCloud Director Self-Service portal able to use this authentication and allow those users to use the portal? Let’s find out (hint: yes it works!).
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…