Greetings everyone, a long time ago I've shared an outstanding tool that I was using at the time called Draw.io, it was my go-to tool for all my drawings, and technical content, plus it has the Veeam, VMware, AWS, and many other most-common stencils. There is nothing wrong with Draw.io and still works strong, and I open it from time to
Veeam: HTML Daily Report for Veeam Backup for Azure is now available – Community Project
Greetings friends, I have spoken about Veeam Backup for Azure multiple times here, I think it is the best Data Protection Solution in the Market for those specific workloads on Azure, here is a list of articles about it: Veeam: Veeam announces enhancements for new versions of Veeam Backup for AWS v4/Azure v3/GCP v2 Veeam: New and improved
Veeam: How to deploy QNAP QuObjects to have an Object Storage on-prem and use it as Capacity Tier
Greetings friends, today I bring you a very interesting post, I have commented in several articles all the power of Veeam Capacity Tier, which allows us to leverage Object Storage providers to store large amounts of backups that usually require long retention, months, semesters, or years. In addition, for some time now, Capacity also allows us to
VeeamON: Quick overview of my top favorite on-demand sessions, plus unofficial Nike Green sneakers
Greetings everyone, VeeamON 2021 has finished, and I have been trying to cover the most important announcements of the event, especially those announcements with Roadmap News, etc. You can find the different articles here: Veeam: Veeam Announces Veeam Backup for Microsoft Office 365 v6 - Self-Service Portal and Native Integration with Azure
Veeam: Veeam Announces Support for Red Hat Enterprise Virtualization (RHEV/KVM)
Greetings folks, during this past VeeamON 2021, Veeam has done it again and announced a new feature that many of us have been waiting for, it is native support for protecting workloads that are on top of Red Hat Enterprise Virtualization. According to the Veeam press release "Veeam is announcing support for its fourth hypervisor in response to