Veeam Cloud Connect reference architecture, the book that I wrote two years ago, is now available as an online book that you can read or download as pdf, mobi or epub.
I recently received this request from one of our service providers: “Is there a way to trace the failover actions in Veeam Cloud Connect, so that I can figure out the consumption of the virtual environment?”. As I never tried before to figure out this one myself, I thought it was time to hit the […]
Veeam Availability Console is completely web-based. For this reason, it’s extremely easy to consume it, and the idea behind the product is that the console can be used directly by users. To do so, the Console itself has to be published over Internet, following a few but important steps.
Recently I’ve been asked by a colleague if Veeam Backup & Replication supports VMware NSX. The answer to me was pretty clear, since Veeam works at the vSphere layer and what is sees are “just” portgroups, regardless if they are simple, distributed, or NSX virtual wires. Nonetheless, I decided to do a quick test to prove it.
In the previous post of this series, we registered a remote Veeam Backup & Replication and started to monitor it. VAC can do a lot of things, but when monitoring and the operations that can be done via VAC are not enough, it’s time to learn what other options are available. Remote Access Console: the […]
If you are trying to connect to a remote tenant using Veeam Remote Access Console, and you face the error “”This tenant does not allow managing any of their backup servers remotely”, there are a couple of firewall ports you need to open. Learn here which ones.
In the previous posts of this series, we completed the configuration of Veeam Availability Console, and onboarded our first customer. The customer logged into his own account and configured the different services. Now in this fourth part, we are going to connect a remote Veeam Backup server in order to monitor it.
I’ve seen often Veeam users to configure their repositories using administrative permissions. This is a really bad practice as the most precious part of a Veeam environment, the backup files, are then exposed to security risks, in case anyone can obtain those credentials. And with the raise of cryptolockers and ransomware this behavior has become even more dangerous. For Linux repositories, users can configure their servers to use common users.