Bring your knowledge and expertise while creating blogs and podcasts
Recently active
Hi Community, If you have just deployed Veeam Backup for Google Cloud (VBGC), the next step is proper configuration to smooth backups and restores. Here’s a simple, step-by-step guide to help you get started quickly: 1️: Add GCP Projects:Go to Configuration → Projects → Add Project.Use Service Account credentials to connect.Make sure the Service Account has the required IAM roles:Compute Admin Storage Admin Cloud SQL Admin Spanner Admin 2️: Set Up Worker Profiles:Navigate to Configuration → Workers → Profiles.By default, you’ll have:Primary Profile (e2-highcpu-8) for regular backups Secondary Profile (e2-highcpu-2) if quotas are tight Archiving Profile (e2-standard-4) for archive jobs 3️: Configure Backup Repositories:Choose Google Cloud Storage buckets or connect external object storage. Use separate buckets for short-term and long-term retention if possible. 4️: Create Backup Policies:Go to Policies → Add Backup Policy.Select projects, regions, and VMs to protect.Define:Backup type (
VMware Cloud Foundation (VCF) 9.0 brings a redesigned architecture that changes how private cloud infrastructure is structured and managed. Whether you're coming from earlier VCF versions or looking at the platform for the first time, this guide breaks down what’s new and how it works in practice. At a high level, VCF 9.0 is a hierarchical system that scales from a single site to globally distributed infrastructure. Here’s how it’s organized and how each layer fits into day-to-day operations. Three-Layer Hierarchy of VCF 9.0VCF 9.0 structures infrastructure into three layers, each serving a clear purpose: Layer 1: Private Cloud (Top-Level)This is the entire footprint of your private cloud environment. It encapsulates everything…your regions, Fleets, and Instances. You can think of it as the top-level container where policy and strategy decisions start.Layer 2: Fleet (Mid-Level)A Fleet is a logical grouping of infrastructure that shares centralized services. Each Fleet includes: VCF Ope
Hi Veeam Community, I have seen many questions (and experienced a few issues myself) when deploying Veeam Backup for Google Cloud (VBGC) in production environments. Most of these could have been avoided with some pre-deployment checks. So, I wanted to share a quick checklist that might help others save time and frustration. 1️: Service Account Preparation Create a dedicated Service Account (SA) in GCP. Assign all required IAM roles/permissions for each project you plan to back up. Test SA access via the VBGC diagnostics tab — all checks should show "Passed" before deployment. 2️: Quota Review Check CPU, disk, and instance quotas for each region where VBGC will deploy worker instances. Adjust quotas in advance if you plan to use higher-spec worker profiles (e.g., upgrading from e2-highcpu-8 to n2-highmem-16). 3️: Network & Access Ensure VBGC and worker instances can access the internet when needed (especially during updates and temporary VM deployment). If using private ne
After receiving an NFR key from Devolutions I headed over to their website and looked around at the documentation. It may be overwhelming to see how much documentation there is, but after browsing some more I realized it is just due to the fact that this software can do so much, and you can configure everything with extreme granularity. There are also many functions the software suite can do.Today we will look at the Remote Desktop Manager and configure cloud based version to save creating any servers and save some time. First, You create your hub, I decided to go with business, but created a personal one after to see the differences. At this point, you will Download and save your emergency kit. Keep this somewhere safe incase you ever loose your account password.Next click on licenses and apply your key.That was pretty much all you have to do to get started. The next step I recommend is adding account recovery, MFA, and OTP to your account, especially if you add any type of credentia
Hello Community ! I am sharing these steps because, when dealing with SharePoint recovery, I encountered several issues that need to be considered, and the online guide is not very clear.First, you need to consider what permissions are required to use the Veeam Explorer for SharePoint tool:https://helpcenter.veeam.com/docs/backup/explorers/vesp_permissions.html?ver=120 First, let's start with the necessary environment:VBR: Veeam Server in workgroupVM_MSSQL: Server MSSQL, on AD domain, with the same version of Microsoft SQL Server installed on which SharePoint is hosted and which will act as “staging server”.Server backup jobs must have Application-Aware correctly configured: Install the Veeam console on the VM_MSSQL server of the same version as the one on the VBR.Check the name of the instance on the DB Server running SharePoint and add a registry key on the VBR server and on the VM_MSSQL server. In our example, we have:SRVSHAREPOINT: SharePoint serverSRVDB: MSSQL server with SharePo
Long-time reader, first-time poster. I thought I’d document my initial experience with Vault from a Veeam Cloud Service Provider (VCSP) perspective, to share the journey with others who may be heading down the same path and to highlight a few gotchas. As with anything new, your mileage may vary and subject to change. We started with a Backup as a Service customer who wanted to use vendor-backed cloud storage. They had spoken to Veeam, were happy with the offering, and it was something we were planning to explore anyway as an alternative to Wasabi. Gotcha #1 – As of writing, VCSPs cannot consume Vault through the VCSP programme and must instead purchase it as a “traditional transaction” through distribution (at least here in New Zealand). What became clearer later in the journey was that there’s a restriction in the VCSP programme requiring the provider to purchase and “own” the storage subscription. This could be an issue depending on the customer type and use case—particularly if they
As you already know, each month, we'll be highlighting a specific Veeam-related registry key to help you better manage and fine-tune your environment.For our post this August, we're diving into a crucial registry setting that can help you avoid potential storage issues: SqlTempLogPath.By default, Veeam chooses the local disk with the most free space to temporarily store SQL log backup files before they're moved to your backup repository. On busy SQL servers, this can quickly consume a lot of disk space. With the SqlTempLogPath registry key, you can manually specify a different location for these temporary files, giving you greater control over your storage.To learn more about how this works and get a step-by-step guide on how to implement it, check out the full blog post here: https://integriservices.blogspot.com/2025/07/regkey-of-month-august.htmlI'd love to hear your thoughts on this key and any other registry settings you'd like us to cover in the future!
Happy Monday, dear Community! I am here with a fresh Veeam Vanguard newsletter containing all the veeamazing content published by our Vanguard program heroes during the last month! @AndrePulia & @BethSouza - Razões e orientações para ser tornar um Veeam Certified Professional - https://community.veeam.com/events/razoes-e-orientacoes-para-ser-tornar-um-veeam-certified-professional-243 @AndreTheGiant - Veeam security features and required licenses - https://vinfrastructure.it/2025/07/veeam-security-features-and-required-licenses/ -Backup scan for Linux VM with Veeam Backup & Replication - https://vinfrastructure.it/2025/07/backup-scan-for-linux-vm-with-veeam-backup-replication/ -Mount servers option in Veeam Backup & Replication 13 - https://vinfrastructure.it/2025/07/mount-servers-option-in-veeam-backup-replication-13/ -Veeam Recon Scanner 2.1 by Coveware - https://vinfrastructure.it/2025/07/veeam-recon-scanner-by-coveware/ @benharmer - VBR V13 Beta 2 – Less bugs, mor
I wanted to post this for everyone who uses VB365 and PGBouncer with Postgres with the recent upgrade 8.1.2.180.When trying to run this upgrade I ran in to an issue with the following error which was caused by connecting to Postgres via the PBBouncer 6432 port. I had to stop services, modify the XML files back to 5432 (default PG port) and then run the upgrade. Once complete I could then revert back to 6432 for PGBouncer and start up the services again.Error seen during upgrade -
There is a new version of the AsBuiltReport.Veeam.VBR report that includes the following enhancements:Blog post:https://techmyth.blog/en/posts/abr-veeam-vbr-0_8_22/Changes:## [0.8.22] - 2025-07-23### Added- Add Cloud Connect infrastructure diagram- Add per Tenant resources diagram### Changed- Updated Get-AbrVbrCloudConnectTenant to include diagram generation- Modified Invoke-AsBuiltReport to handle tenant-specific diagrams- Improved handling of diagram parameters and outputs- Updated changelog and version numbers across scripts- Refactor diagram section in Get-AbrVbrCloudConnectTenant function for improved error handling and clarity### Changed- Bump module to v0.8.22- Bump Veeam.Diagrammer module to v0.6.30- Bump Diagrammer.Core module to v0.2.27- Update workflow to use Windows 2022 for publishing PowerShell moduleSeveral updates have been made to diagram the Cloud Connect infrastructure. I hope you find these improvements helpful! ¡Hasta luego!
Happy Monday everyone! We are reaching the end of the month and that means there will be soon next Veeam Vanguard newsletter out, this time gathering all the Veeam related content published during July. Before that happens I want to share with you May and April Newsletter, as they´re not too old yet and many of you might find content included there still relevant and helpful. So take a seat and check what´s in there for you: Vanguard April Newsletter@alrasheed - The Power of the Veeam Vanguard Community - https://alarasheedblog.wordpress.com/2025/04/01/the-power-of-the-veeam-vanguard-community/ @Chris.Childerhose - PowerShell Tips for Veeam – VB365 v8.1 - https://just-virtualization.tech/2025/04/01/powershell-tips-for-veeam-vb365-v8-1/PowerShell Tips for Veeam – VB365 v8.1 – Move Data Between Repositories - https://just-virtualization.tech/2025/04/10/powershell-tips-for-veeam-vb365-v8-move-data-between-repositories/ @c_glemot - Veeam Vanguard 2025 - 10th time in a row! - https://o
Your backups have been collecting forensic evidence this whole time. Those "humble" audit and sign-in logs from Entra ID. They're actually detailed behavioral fingerprints for every user. When someone deviates from their normal pattern - different country, weird hours, new device... you name it. Instead of letting that data collect digital dust, you can build a surprisingly effective anomaly detection system from what you already have. Here is roughly how this all works. Step 1: Get Your Data ReadyFirst, you'll need to dig into those sign-in and audit logs from your Veeam backups. Microsoft's log format is a bit nested - it's layered like an onion and about as fun to work with. Flatten that mess into something actually usable and drop it into MongoDB (could be anything). Step 2: Teach the System What Normal Looks LikeThis is where machine learning earns its keep. Feed some historical data (I chose 60 days) to the system and let it figure out each user's habits. Does Sarah always log i
As we all know, data backup security is a top priority for every organisation. In my first article I spoke about Security Analyzer feature. In this second part of our series on Veeam’s security features, we’re going to focus on one of the most important new features introduced with Veeam Backup & Replication v12: Four-Eyes Authorization. So, what exactly is Four-Eyes Authorization?The Four-Eyes Authorisation, or the “two-person rule” as it’s also known, is a feature that needs the OK from a second administrator to perform certain sensitive operations in Veeam Backup & Replication. This makes it much harder for any one user to mess up or do something dodgy with important data, because it stops them doing anything important on their own.“The four-eyes principle requires that a critical activity must be approved by at least two people, minimizing errors or security breaches.”Here are the best practices to implement four-eyes authorization and the limitations you should know.First
Last week, I wrote a blog post about “pikchr/piclasso.” When beginning this project, I also considered additional ideas. One of these was how to convert certain scenarios from https://www.veeam.com/calculators/scenario into images. This aspect is significant because visualizing the layout of components can improve understanding and, as a solution architect, it facilitates presenting information to customers. I created https://github.com/tdewin/piclasso/blob/main/mergedemo/vscn-to-piclasso.py, a tool that converts vscn files ("export current scenario") into piclasso diagrams. Safe to say that this is not even a BETA but more some ALPHA code or proof-of-concept. You can copy the output manually or use the "--link" option to generate a direct link. On Mac, combine this with the open command to instantly view your content in the browser. The result:
This is part three of three addressing general topics of environmental architecture for backup systems.In part XVI, we examined considerations for the placement of individual backup components, hardware configuration, and fault tolerance (Point 1 and 2 of the following list of major threats).In part XVII, we examined considerations for locations and site redundancy (Point 3 to 5 of the list of major threats).In this part, we address the aspects of ransomware, malware, theft and threats by insiders. These are points 6 to 8 on the list of major threats to backup environments that we identified in the last part. What are the main threats to backup data? Wrong placement of backup environment components Hardware damage to backup systems Power outages or disasters at one location Power outages or disasters at multiple locations External locations for backup data Ransomware attacks Theft of access data and unauthorized access Intentional or unintentional damage by insidersAs with the topics i
I have been using Synology NAS devices for a few years now and was lucky enough this year to get my hands on a new DS925+. They removed the 10GB option from this one but there is dual 2.5GB ports which you can bond. Find my blog post below and the link as well. Enjoy.Synology DS925+ – Installation & Setup Synology DS925+ – Installation & Setup Over the last couple of years, with the help of Synology, I have been able to secure a DS920+ along with a DX517 expansion & a DS923+ NAS unit, which I have written reviews about. Fast forward to 2025, and I was again in touch with Steph Clayton at Synology, who graciously helped me secure a DS925+ NAS for testing and blogging.The DS925+ is the latest version in the 9xx line of Synology NAS products, featuring several new enhancements, including an updated CPU based on the AMD Ryzen V1500B, a 4-core processor. The unit also supports up to 32GB of RAM, Dual 2.5GB networking, and NVME drives for caching.The following is a list of t
Creating architectural diagrams is challenging for everyone, not just Backup engineers. While you can find Veeam colors and icons at https://www.veeam.com/company/brand-resource-center.html, these resources may change, making it difficult to keep designs current. I found updating most of the Veeam Best Practice guide diagrams—like those at https://bp.veeam.com/vbr/Support/S_Vmware/backup.html—to be especially time-consuming and frustrating. I am continually seeking innovative tools to enhance my workflow. Recently, I discovered pikchr, which offers greater versatility than mermaidjs while still enabling diagrams to be created through code. The layout engine operates from left to right by default, but this setting can be modified as needed. The following example generates two boxes containing the words Proxy and Repository. The word "move" is included to provide spacing between the boxes; without it, they would appear adjacent to each other. The labels “P:” or “R:” at the beginning of e
At VeeamOn 2025, Scality announced a unified software appliance with Artesca Object Storage and Veeam Backup bundled inside as a VM on Kubernetes via KubeVirt. Since this is a software appliance it allows you to use the hardware of your preference but have a simplified deployment and management. The current version is using a Windows Server, either 2022 or 2025, and Veeam 12.3. In the future, the Veeam Software Appliance (v13 on Linux) will also be an option.Recently this has passed Veeam Ready qualification as a repository and for object storage: https://www.veeam.com/solutions/alliance-partner/integrations-qualifications.html?alliancePartner=scalityIn the Service Provider space at Veeam, I have had several partners ask about an appliance to make it easier to deploy Veeam and manage it daily. So, I was intrigued by this announcement and wanted to test it out. (I like to play with the tech as this is the way I learn, hands on more than read).I downloaded the ISO to install and after a
The number of VMware-based public cloud offerings continues to grow. Whether it’s to support cloud migration, reduce data center footprint, or simplify operations, more organizations are looking at running vSphere in the cloud. Some of these platforms have been around for years, while others are newer or just starting to see broader adoption. Even though they all run VMware, not every cloud platform gives you the same visibility or control — which makes a difference when it’s time to plan for backup and recovery. To help clarify what’s possible, I pulled together a matrix comparing the major VMware public cloud platforms — AWS, Azure, Google Cloud, IBM, and Oracle — and how Veeam fits into each one. AWS – VMware Cloud on AWS (VMC)A managed SDDC running on AWS with some restrictions that impact transport methods and access. Veeam support is available but requires specific configuration.KB Reference: Veeam KB2414 AWS Elastic VMware Solution (EVS)This is a standard vSphere environment bui
In an era defined by ever-expanding data footprints and rapidly evolving application landscapes, traditional backup architectures often strain under the demands of modern enterprises. Organizations must not only safeguard data but also build backup infrastructures capable of growing seamlessly alongside their data volumes and adapting to shifting business requirements. A future-proof backup environment relies on scalable designs, cloud-native integrations, and automation to deliver reliable protection, efficient resource utilization, and consistent recovery performance. The Imperative for Scalable Backup SystemsEnterprises today generate data at an unprecedented pace. Every transaction, log, telemetry feed, or multimedia asset contributes to a mounting store of information that must be preserved for operational continuity, compliance mandates, or analytics purposes. A backup solution that cannot expand gracefully will quickly become a bottleneck, forcing disruptive, costly hardware swa
Over the past few weeks, I’ve had numerous conversations with customers about how to protect Microsoft SQL Server with Veeam. Whether it's running on-premises, in Azure VMs, or as a fully managed cloud service, SQL Server plays a mission-critical role in countless organizations — and making sure it’s protected and recoverable is non-negotiable. But here’s the thing: there’s no single “right” way to back up SQL Server with Veeam.No one method is universally better than the others — it all comes down to your infrastructure, operational preferences, and recovery goals.So, to help make sense of the options, I’ve broken down the different ways Veeam supports Microsoft SQL Server backups, organized by where your SQL Server is running.On-Premises Microsoft SQL Server:Agentless Image-Level Backup (VM-Based)This is the simplest and most common approach for virtualized environments (VMware vSphere or Microsoft Hyper-V).Key Features:Agentless backup using Veeam’s hypervisor integration Applicatio
AI has been getting bigger every day, to make things easier, I compiled a list of how we use it and the tech behind it, benefits, explainability and best practices associated with it. If you feel behind in any of these topics or just want to learn more, feel free to check this out!
OverviewI was recently working with a customer on migrating some Rocky Linux VMs running on vSphere hosts to some Hyper-V hosts using Veeam Backup and Replication. After the migration to Hyper VM, the customer received the following error when the VM tried to boot. The issue is that the VM can’t boot in Hyper-V because it is having trouble finding the boot image and mounting the root file system. On further inspection, it was discovered that the Linux VM was missing the required Hyper-V drivers. Windows-based VMs do not run into this issue as they already have the required drivers available at boot. Before Veeam can boot a migrated Rocky Linux VM in Hyper-V, the Rocky OS needs to have the proper Hyper-V drivers installed in the intramfs.img. Once the Hyper-V drivers are added to the initramfs.img the VM can boot and function correctly in the Hyper-V environment. This issue can be fixed after the VM is migrated by booting it to a Live CD and then adding the drivers. Veeam KB 2669—h
On the week of June 23-26, I had a great opportunity to join Emilee Tellez and Jackie Priddy at HPE Discover 2025 in Las Vegas, Nevada. From cutting-edge innovations to powerful conversations, this experience has truly been one for the books. One of the biggest highlights was seeing Veeam showcase our newest collaboration with HPE Morpheus VM Essentials, reinforcing the importance of radical data resilience and cloud automation.It was also inspiring to hear Eric O’Neil, former FBI Ghost, speak on how he helped take down one of America’s most notorious spies, Robert Hanssen. His story on trust, espionage, and cyber risk left a lasting impression and lesson.Being able to join in this experience was amazing and having the chance to connect with some amazing teammates at Veeam was great. Everyone was incredibly generous with their time, advice, and insights. I learned so much from just being around them.Veeam Data Platform & HPE Morpheus VM Essentials SoftwareJohn Jester, the Chief Rev
Dear Community,When working with Veeam Backup for Google Cloud (VBGC) in environments that span multiple GCP projects, it’s critical to understand how Service Accounts work and why they are the backbone of successful backup and recovery operations.This information highlights a real-world scenario where a single service account was configured to manage backups across multiple GCP projects and what permissions are absolutely required to ensure everything runs smoothly. Why Service Accounts Matter in VBGC. The Service Account (SA) is the identity VBGC uses to:Access GCP resources. Perform backups, snapshots, and restores. Manage staging servers. Recover files at the VM or database level. One properly configured Service Account is enough to manage backup and restore operations across multiple GCP projects: The SA has sufficient IAM permissions in each GCP project. All projects are added to the VBGC appliance in the web interface. The appliance can communicate with the associated resources
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.