Greetings friends, if we remember the introduction to this series on how to create a Disaster Recovery plan with Veeam in Microsoft Azure, we had the following diagram: In the diagram we can see how between the two locations we are using Veeam PN for connectivity, in this article today we will see the step-by-step steps to deploy and configure
Veeam: Backup and restore workloads to Microsoft Azure – Introduction
Greetings friends, every day it is more common to move workloads to Microsoft Azure, or at least to have planned a certain level of Disaster Recovery to Microsoft Azure in case of a complete shutdown of our main data center, to be able to restore those most urgent applications for users or customers, reducing service downtime. Veeam has a number
Veeam: Veeam magnets, visio shapes with magnets, ready to be used on whiteboards in the Real World
Greetings friends, a few days ago I finally finished a project that I had thought about months ago but I never had time to complete, it is about having the Visio forms of Veeam, or any other manufacturer, printed and magnetic so that we can use them in the increasingly common whiteboards, this can help us to: Create better presentations for
Veeam: AWS workloads now protected thanks to the Veeam’s acquisition of N2W Software (N2WS)
Greetings friends, probably you have heard the news that told us how Veeam had acquired N2WS, a company that is dedicated to the protection of environments in Cloud on Amazon Web Services. https://www.veeam.com/executive-blog/veeam-acquires-n2ws.html Why did Veeam acquire N2WS? N2WS is a leader in Infrastructure as a Service (IaaS) data
VMware: How to solve [InstallationError] There was an error checking file system on altbootbank
Greetings friends, making several upgrades the other day I found the next error that breaks you in the morning if you are in a hurry and you are performing upgrades of ESXi, the error in question happened to me when I tried to update using an ESXi bundle: [InstallationError] There was an error checking file system on altbootbank, please see log