Bring your knowledge and expertise while creating blogs and podcasts
Recently active
IntroductionTo enable monitoring of your Veeam Software Appliance (VSA) with VeeamONE, the Veeam Analytics Service needs to be deployed on the VSA.The Veeam Analytics service not only enables communication with Veeam Backup & Replication servers to collect data but also allows to send remediation commands.Since the VSA is secure by design (hardened Linux-based OS, DISA STIG compliance, automated patching…) and that it enforces Zero Trust principles with role-based access control, SAML SSO, and certificate-based pairing, it is important to know what are the available options to connect VeeamONE securely. In this article, we will cover 2 methods of connection and highlight their pros and cons:Via the Veeam Analytics Service Offline BundleORManaged by VeeamONE via the Data Source Wizard Connecting to the VSA with the Offline BundleThe advantage of using the offline bundle is that you don’t need to store VSA credentials anywhere. Simply hand off the bundle to your Veeam Backup and Repl
Hello Community! SynopsisI couldn’t wait to get this out to you all. If you’ve been following along my Veeam Malware Detection journey, specifically with Inline Entropy scans, you know I’ve shared it has some shortcomings; although, it’s still a great tool to implement in your environment in my opinion.The post today coincides with my most recent Malware Forensics post on how to work through events you may receive from Veeam. Click below to read it if you like:Since my Forensics post a few weeks ago, Veeam has provided a few updates to its Malware Detection engine. UpdatesThe first update came with the latest Veeam Backup release, v12.1.2. Much of the Malware updates in this release came mostly from Community feedback on the Forums and pertained mostly to the File System Analysis (FSA) engine. I don’t use that engine in my environment, so not sure how well the update has worked with regard to FSA detection, false positives, and exclusions.The 2nd update is specifically for the Inline E
Mongo DB and VeeamTraditional relational database systems such as Oracle, Microsoft SQL, Postgres are built around the concept of tables of information organized into Rows and Columns. These tables/rows/columns store data in a rigid structure. When a new row is created for a table, it should have all the same fields as other entries in the same table. Some fields in a table can reference information from other tables through foreign keys. There is a Schema to define what fields exist in which table and how tables cross reference each other. Data is entered and retrieved through a Structured Query Language which is similar across each of the different vendors but might have slightly different syntax. Each platform has a unique way to manage scale and improve performance and how storage is managed, as well as implementations of other features like replication and high availability.Relational databases aren’t the only option for storing data. NoSQL databases offer more flexibility in how
Hey everyone,Let’s kick this off by highlighting that as of this moment, Microsoft SQL Server 2025 has not yet been validated for the Veeam Data Platform, as it was only made GA yesterday the 18th November 2025, so the information I’m providing here is in preparation for the inevitable support when it’s passed through Veeam’s QA.Microsoft have now released Microsoft SQL Server 2025 and in reviewing the changes, I stumbled upon some insights that I thought would be worth highlighting to those still using Microsoft SQL Server to power their Veeam Data Platform installations.Starting with Microsoft SQL Server 2025 Standard Edition, Microsoft are making two key changes that will impact scalability; an increased CPU core count, and increased maximum RAM limits. Now they are:CPU Socket Count: This is unchanged and still a maximum of 4x CPU Sockets. If you’re finding idle cores a lot with your SQL Server instance, make sure this isn’t your limit! CPU Core Count: This is increasing 50% from a
With the recent topic of how to change the IP/DNS Name of the vCenter recently posted I wanted to share for those with experience in SQL how you can modify the vCloud URL within Veeam.This requires some SQL knowledge and that you shut down the Veeam services during the process. The main query is as follows:SELECT * FROM Hosts WHERE type=1 OR type=6 OR type=14; Under the "options" column for the relevant row(s) we're going to see the reference(s) to the old cell hostname. Then once you are ready follow these steps:0) Veeam Configuration Backup1) Stop Veeam Services2) Backup VeeamBackup SQL DB3) SELECT * FROM Hosts WHERE type=1 OR type=6 OR type=14;4) Copy the "options" value5) Modify the copied "options" column value to have the new VCD URL6) Note the id column of the related row7) Perform the update query on the objects that need the new URL:UPDATE Hosts SET options='NEW_options_VALUE' WHERE id='ID_FROM_STEP_6';8) Start Services9) Open Console, and "next" through the properties of the
Veeam Data Cloud Vault (VDC Vault) is a secure, fully managed cloud storage solution designed to simplify data protection for hybrid and multi-cloud environments. It offers zero-configuration, management, or integration complexities, making it easy to safeguard Veeam Backup and replication backup archives in a secure off-site location with a consistent subscription price. With Veeam Data Cloud Vault, you can effortlessly achieve the 3-2-1 rule: three copies of data, two different types of media, and one copy offsite. The Veeam Data Cloud Vault ensures data immutability, logical air-gapping from production, and AES 256-bit encryption, providing robust protection against cyber threats. Technical Requirements Security BlueprintThe Veeam Security Blueprint reference architecture for an on-premises backup copy to VDC can be found on the Veeam Community site at https://community.veeam.com/security-blueprints-126.Storage optionsThe following Veeam Backup & Replication backup archives can
On Feb 5, 2026, Microsoft officially announced that EWS in Exchange Online is being deprecated. Starting Oct 1, 2026, Microsoft will begin turning off EWS usage unless it is explicitly extended via a setting. With a deliberate “Not yet!” (aka OrganizationConfig -EwsEnabled $true), EWS is expected to remain usable until Apr 2027—however, this is not a permanent setting, just a temporary extension. So first…. What exactly is EWS? EWS stands for Exchange Web Services and was built almost 20 years ago. For many years—and up to today—it has been used as an API interface. In general, this interface no longer meets today’s requirements for security, scalability, or reliability, which is why Microsoft developed the Microsoft Graph API.By now, the Microsoft Graph interface provides near-complete functionality parity for most EWS scenarios. Microsoft’s own applications have either already migrated away from EWS or are close to finishing. Many third-party vendors have also already transitioned to
Enhancing Your Veeam Security: Key Features to ActivateVeeam Software’s R&D department has been busy the past year. It has introduced three minor feature releases (V12.1, 12.2, and 12.3), including crucial new security features and updates. If you have just installed V12 or are still on V11 and are planning an upgrade to the latest V12 release (V12.3), you may be overwhelmed by figuring out an “order of importance” for activating features.I suggest to customers moving to V12.3, or are using V12.3 but haven’t implemented any security features yet to turn on the new features in this order: Veeam Hardened repository, MFA, 4-Eyes authorization, Entropy and Indicators of Compromise scanning, and Veeam Threat Hunter. First: Veeam Hardened repositoryThe security of your backup infrastructure should start with and center around Immutable storage. For Veeam, this is the Veeam Hardened Repository (VHR). The Veeam Hardened Repository is delivered as a bootable ISO. It allows you to create a
With the release of Veeam Data Platform 12.3 the Nutanix hypervisor is now displayed in the installation splash screen see figure 1 below. In addition some highly requested features have been added to this release see the screenshots below. Figure 1Enabling Nutanix Guest Tools is now an option in the backup job setup screen in the VBN AHV appliance see figure 2. The Nutanix Guest Tools setting will also be available in the VBR console once the job is created in the VBN AHV appliance. It will appear in the “Advanced Settings” Nutanix AHV tab see figure 3 below. Figure 3You will see a new guest processing settings screen on the VBN AHV appliance. It will direct you to set it up in the VBR console for the job see figure 4 below. Figure 4 The application aware processing and guest indexing is now available in “experimental support”. You can still call Veeam support if any issues arise see figure 5. Figure 5Once job changes are made in figure 5. You will see a synchronized job settings on t
When I thought the tape was forgotten ... Veeam brings us these improvements that I think are excellents! Tape 📼 Improvements TAPE CLONING !!! Allows us to Migrate from old LTO to newer tapes generations Additional copy for security reasons You can Copy from one drive to other drive via tape server You can Modify database and link old backups with new tapes You can Preserve link for old tapes File parts are detected and prompt for additional tape Note:Veeam can clone all Veeam tapes (B2T, F2T, NDMP), Veeam Can't do it for 3rd party tapes. What you need to know Requires at least two drives Restore selects automatically the needed tape if several copies exist No scheduler (use PowerShell) One media pool still does only allow one LTO generation What do you think of this improvement?
Applicability and efficiency of each transport mode primarily depends on the type of datastore used by the source host — local or shared, and on the backup proxy type — physical or virtual. The table below shows recommendations for installing the backup proxy, depending on the storage type and desired transport mode.which one do you use?
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
HiIn the 2 days during VEEAMON 2021, there was often the question from new members why to choose Veeam over other competitors…Therefore my own top-15. There will be more reasons, but I think it will cover a lot of the reasons and I don’t think someone has to hesitate anymore ;-) PortabilitySomething I like very hard! All necessary information is built into the backup-file.You are not dependent of your backup-server to restore something. In case of emergency of disaster it’s just sufficient to install VBR Community Edition (free), import your backup-file and restore. You can even extract your backup-file (without VBR) to the .VMDK or .VHDX files.Next to that : the format is interchangeable : you can for example restore a VM (backup taken from vSphere on-premises) to Azure or to HyperV, or restore a backup taken with a Veeam Agent to Amazon EC2 or HyperV, … and so on, the list is very long! Not always possible with other backup vendors in my experience. Universal licensesIf you use univ
When integrating a Synology NAS with Proxmox VE. NFS provides a convenient and flexible storage solution for virtual machines, ISO images, templates, and backups. Unlike local Proxmox storage or block-level storage solutions.Network File System (NFS) shares on a NAS are network-based and accessible to multiple nodes simultaneously, making them ideal for clustered environments or home labs. Kindly take a look at this blog post for more information “Add Synology NFS Storage to Proxmox VE for VMs and Backups”. One important characteristic of NFS on Synology is that it is not pre-allocated. The storage is thin-provisioned, meaning that VM disk files grow dynamically as data is written. This allows efficient use of disk space. But it also requires monitoring free space on the NAS to avoid unexpected storage exhaustion.NFS itself is a protocol that allows a client, such as Proxmox to access files over a network as if they were on a local disk. When using Synology NAS as NFS storage for Proxm
Enabling Multi-Factor Authentication (MFA) or Two-Factor Authentication (2FA) is the best way to protect accounts from password theft or phishing. Therefore it’s recommended to enable such options, when they’re available. Since some time it’s possible to use MFA for Veeam Accounts, which are used to access the my.veeam.com portal or also the Veeam Community 😉Login to your Veeam account at my.veeam.com and click on edit profile in the top right corner.At the bottom of your profile details, you need to click on “Enable MFA”. As a side note, even after enabling MFA this link still states “Enable” instead of “Disable”.On the following page, you need to click on “Set up authenticator application” and follow the instructions. While FreeOTP or Google Authenticator are recommended, you can use any other OTP app; for example I’m using Aegis. Afterwards it’s recommended to create recovery authentication codes, for the case that your MFA app isn't available. Of course you should not store those
Migration from VMware vSphere to HPE HVM with Veeam As organizations modernize their infrastructure strategies and reduce dependence on legacy virtualization platforms, many are evaluating alternatives to VMware vSphere that preserve operational continuity, performance, and data protection. HPE Morpheus Software VM Essentials, combined with Veeam Backup & Replication, delivers a validated and enterprise‑ready path to migrate workloads with confidence, minimal risk, and a clearly defined rollback strategy. This guide describes migration from VMware vSphere to HPE VM Essentials leveraging Veeam Backup & Replication to move workloads to HVM clusters (HPE’s hypervisor). Fundamental to this joint solution is the Veeam Plug‑In for Morpheus VM Essentials, which provides agentless, host‑level backup and recovery operations for HPE HVM. This plug‑in allows Veeam to work directly with Morpheus infrastructure, ensuring that virtual machines can be seamlessly protected with Veeam after mig
Due to recent events, I thought I would share a blog post I wrote a while back on how to add Veeam Recovery ISO to Window’s Boot Menu. This helped us tremendously during the CS outage to quickly gain access to our DC’s. Veeam Agent Recovery Media Boot Integration During the last Veeam Vanguard/Veeam 100 summit in Prague, Czech Republic part of the summit was “Fun field facts” where attendees presented various topics they found useful for sharing. I presented on how to integrate Veeam Agent into Windows. This will be a short follow-up post on how to incorporate the Veeam Agent Recovery Media into Windows Boot Manager.I started my presentation in Prague with “When it rains, it pours…” and, after being in IT for many years now, that is what happens. Just like Murphey’s Law; so imagine this, you have a physical workload backed up with Veeam (great), and the OS crashes. You need to restore to bare metal as fast as possible. But now you need to create the recovery media first, boot up the
When running a Veeam backup, you may encounter the following error:One or more errors occurred. (The remote certificate was rejected by the provided RemoteCertificateValidationCallback.)This issue is typically caused by a trust problem between the Veeam Backup & Replication (VBR) server and a managed server or backup component.ResolutionTo resolve the issue:Open the Veeam Backup & Replication console. Navigate to Inventory. Trust allRetry the backup job.Once the certificate trust is restored, the backup should complete successfully.ConclusionIn most cases, this error indicates that the remote certificate is no longer trusted by the VBR server. Re-establishing the certificate trust relationship resolves the problem quickly.
Unofficial, community-built tool — not an official Veeam product and not supported by Veeam Support. Results are estimates derived from a parsed log and should be validated against the official Veeam calculators, the Veeam Help Center, and Best Practices documentation. For final sizing decisions, loop in a Veeam SE / Solution Architect.When reviewing a Veeam environment— usually because there's a sizing conversation coming, or someone wants a second opinion on whether a setup is sane. And almost every time, the information I actually need is sitting right there in the VMC.log. Proxy count, repository layout, retention, GFS, agent jobs, whether immutability is on, what the NICs are doing. All of it.The problem is it's buried in a few thousand lines of log, and after the third or fourth time of Ctrl-F-ing my way through one of these to pull out proxy task counts and squint at retention policies, I got tired of it.So I built something to do the reading the log file for me.It's called Vee
Nutanix introduced AOS 6.8 and it is causing some API issues with Veeam Backup for Nutanix. This can result in restore failures and other issues. We are recommending Veeam customers not to upgrade until an updated version is available from Nutanix. The timeline we received for the update is later toward the end of the year. Please see the links below for the latest details😀.Veeam Forums link https://forums.veeam.com/nutanix-ahv-f51/aos-6-8-veeam-ahv-support-interoperability-validation-t93415.htmlVeeam Backup for Nutanix User Guide (Supported Versions)https://helpcenter.veeam.com/docs/vbahv/userguide/system_requirements.html?ver=50Thanks,Pete
Agent For MAC Deployment always via catch-all protection groups•.pkg file for installation•Install with double-click or 3rd party software management solution*•Full Disk Access (FDA) must be allowed in both cases Full Disk Access: Manual ConfigurationGo to “Settings –Security & Privacy –Full Disk Access” Check Profile On MacOS 3 Ways To Connect Agent To VBR 1) Command line (same as Veeam Agent for Linux) 2) Import a Catch-Allconfiguration file; can be done via UI: 3) Use mobile device management to distribute a configuration profile Visibility On VBR Side Appears in VBR after import of Catch-All configuration Assign backup policies in VBR console IMPORTANT VAM does NOT back up volumesperform bare metal recoveryperform any sort of application aware backupsave applications settings (unless you specifically select the required files)allow non-admin users to access other users’ datahave local UI to create jobs
General Recommendations Platform Memory and CPU Over-commitmentFirst and foremost, memory over-commitment is not recommended in OpenShift. However, Red Hat recommends overall CPU over-commitment ratio must not exceed 1.8x of the number of physical cores and that memory usage may not exceed 0.9x of the physical memory available in a cluster. This rule is applicable to the ratio of CPU allocation to all of the pods to physical cores available in a cluster.NOTE: CPU over-commitment leads to throttling, so slowness of all workloads on the impacted node. Thereby workloads can be more or less sensitive to that.✅More Information about CPU Ready HereGeneral rules for the vCPU:pCPU ratio ⚙️🧠:✅ 1:1 to 1:3 → No problem 😌⚠️ 1:3 to 1:5 → Performance may start to degrade 🐢📉🚫 1:5 or higher → Likely CPU Ready issues 🔴🧯 Storage and Network LatencyVarious kinds of applications are more or less sensitive to latency on network and/or storage. In the context of an OCP instance the etcd as hosted on
I am often tasked with creating storage heavy systems in terms of throughput and I/O.Some of the proprietary video systems create lots of IO and the users require a lot of space. We all know M.2 NVMe drives are perfect for the task, but what happens when you need larger volumes? Software raid or using Storage Spaces is easy, but the performance penalties are not small. Hardware raid performs much better, but what about when you want to take it to the next level? I purchased a GRAID SupremeRAID SR-1001 and a LQD4500 (Honey Badger) to do some testing. The SR-1001 is a GPU accelerated raid card, and the LQD4500 is 8 M.2 drives on a PCIe card. You can see after installing the LQD4500, device manager shows it has added 8 Samsung disks to the 3 I already had in the system. For the first test, I created a 28TB volume using storage spaces with default settings and ran a default test in CrystalDiskMark. Having an idea of the performance you should be expecting can really help you tune thin
An advantage of software-defined Veeam products is that they can be installed in many different ways and on any hardware your company owns and uses. They can be installed on-premises, or in any hyper-scale public cloud, you choose. To help customers architect, size, and secure the various Veeam products and features, the Veeam Solutions Architect team has created Veeam Security Blueprints (SBP) and they are publicly accessible. Veeam Security Blueprints can be found at https://www.veeam.com/security-blueprints.html Veeam Security Blueprints (SBP) are short (3 – 4 pages) scenario-based reference architectures covering common scenarios seen in the field. Types of scenarios include:On-premises environment using multiple different vendor storage targets (HPE, Cisco, Pure, Exagrid, Cloudian, Lenovo, Zadara, Hitachi Vantara). Veeam cloud backup products (Veeam Backup for Azure, GCP, AWS) VMC on AWS and hybrid environments Veeam Plugins for Enterprise Applications (Oracle and Microsoft SQL)
Hi all!!! I’m here to let you know that the Veeam Cookbook is here and available for all of you in https://veeamcookbook.com/. This cookbook is a collection of recipes to accomplish one task each, the idea is based on a recipe that you read for instructions not for explanations.This book is intended for many people: New to Veeam and just want a simple next, next, next, approach, not to learn about Veeam but how to do something. People who already know Veeam well but sometimes we only do tasks once on an odd occasion, we know the technology just cannot remeber the how! People who just want a quick refresh These recipes for now are based in Veeam Backup & Replication operations Version 11. The cookbook is the creation of the EMEA Veeam Solutions Architects, and we’d really appreciate your feedback for future releases. More to come soon!!!
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.